Is GitHub down? Check the current status
GitHub is operational
Updated
GitHub is operational
Updated
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
IsDown pulls data from GitHub's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.
This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.
Michael
about 19 hours agoCodespaces The codespaces are not loading
cindy
about 21 hours agoCodespaces Codespaces is not connecting
Matei
about 23 hours agoCodespaces Page not loading Console: Uncaught SyntaxError: expected expression, got '<'
Henry
2 days agoCodespaces I'm locked in a "Setting up your codespace" screen
Peter
4 days agoActions Github action stuck queued for runner for 20 minutes
Revanth
6 days agoCopilot Copilot page now found issue
David
9 days agoCodespaces I can't connect to some of my codespaces.
sila
10 days agoCodespaces codespace is not connecting
Cacho
16 days agoCopilot 400 errors trying to get prompt responses in VSCode Copilot
Matt
16 days agoCopilot Responses very slow from all models
Isabella
17 days agoCopilot Getting an error message when trying to open
Jamie
21 days agoActions GitActions syn/push is stalling / looking for runner
Mike
23 days agoCodespaces Codespaces give an error when trying to load
Dziugas
24 days agoCopilot GitHub Copilot Language model unavailable
Amanda
25 days agoCodespaces I can't get my codespace to load, it's stuck on the setting up remote connection loading bar (internet is working for all other sites)
Guille
28 days agoCopilot Not hable to use Github Copilot Chat on Github web site. Conversation failed to load Reload the page to try again.
pino
28 days agoCopilot it's not loading properly, giving me a dull error
Yonan
28 days agoCopilot It says conversation not found. Please reload. When I am on the landing page.
Kresimir
29 days agoCopilot Getting the following error message: Conversation failed to load Reload the page to try again.
Ujjwal
30 days agoCopilot it is not processing any content via codespace access or via github
CurrentUser
about 1 month agoCodespaces Connection errors, multiple times, many days a week. Almost always at around this hours. They should fix this
Chandrasekaran
about 1 month agoCopilot GitHub Copilot not working within Visual Studio Code. Get this error in the output: 2025-03-18 11:56:37.755 [info] Logged in as jjchandru 2025-03-18 11:56:58.848 [error] GitHub Copilot could not connect to server. Extension activation failed: "net::ERR_CONNECTION_TIMED_OUT" 2025-03-18 11:56:58...
A
about 1 month agoCopilot 502, 400, request failed errors on copilot in vscode insiders
omid
about 1 month agoCopilot vscode copilot Err: Failed to sign in to GHE.com. Would you like to try again? You must be signed in to use Copilot.
phil
about 1 month agoCopilot [Conversations Warning] [CopilotClient] Issue with setting up the connection to 'https://api.githubcopilot.com/chat/completions', if you are using a proxy, check if HTTPS_PROXY is set correctly. https://learn.microsoft.com/en-us/dotnet/fundamentals/networking/http/httpclient#http-proxy [Conversa...
Alejandro
about 1 month agoActions self-hosted runner not taking jobs even when restarted
Mohamad
about 1 month agoActions The Workflow keeps running and unable to be cancelled
Jessica
about 1 month agoCopilot It is not responding to any requests for instance definitions and meanings
Andrew
about 1 month agoCodespaces My GitHub codespace gets stuck while building on both my local Visual Studio Code and when I open it in the browser. On VS Code, the bottom right corner toast message says "Setting up remote connections: Building codespace...". The bar is half finished, but it has stopped and hasn't gone any furt...
Isak
about 1 month agoActions Blank screen, does not start, says started 4m ago but I cannot see anything?
Csaba
about 2 months agoCopilot same here. keeps generating and nothing happened.
Lukasz
about 2 months agoCopilot I cannot ask questions in the Web chat.
Bob
about 2 months agoCopilot This gives: RPC server exception: System.Exception: Error occurred while invoking intent 'None'. Bad Request
Ender
about 2 months agoCopilot Every chat I send into GitHub Copilot returns a "Sorry, your request failed. Please try again. Request id: Reason: Server error: 500 Internal Server Error"
Loret
2 months agoCopilot I enter my questions with no response.
Zack
2 months agoCodespaces Spontaneous prompts codespace restart, remote connection stalls on set up.
Ivar
2 months agoCopilot Not loading or suggesting
Mathew
2 months agoCodespaces Codespaces is stopping after a few minutes running and needs to be restarted to work. Multiple users at company experiencing issue.
kelvin
2 months agoCopilot not responding to auto complete
Lorran
2 months agoCopilot It keeps generating, generating, and never ends, never delivers any answers.
David
2 months agoCopilot Sorry, your request failed. Please try again. Request id: 5c93e76d-3b43-495d-8942-a32ef1b5c66a Reason: Request Failed: 400 Bad Request
jason
2 months agowhen i click download zip file it gives me error 404 and i can not download any file
tobias
2 months agoCopilot not getting access, either on vscode or in github
Joshua
2 months agoActions Large runners not being assigned
tristan
2 months agoCodespaces 502 Bad Gateway on my codespace link
jason
3 months agoCopilot when i use github copilot locally, it works well. But when i start the vpn to access remote company environment, the github copilot reports "sorry, please tray again latter"
jason
3 months agoCopilot github copilot always reports "Sorry, your request failed. Please try again."
Leslie
3 months agoCopilot Copilot is down. All functionalities including Chat, auto-complete and Git changes summary aren't working. They simple don't process
Simon
3 months ago504 The server didn't respond in time.
Anubhav
3 months agocant open any repo on github
alex
3 months agoWe couldn't respond to your request in time. Sorry about that. Please try refreshing and contact us if the problem persists.
mich
3 months agoCopilot "Sorry, your request failed. Please try again. "
Abdulla
3 months agoGithub pages not loading properly
Neil
3 months agoCopilot Copilot not returning responses
Jaden
3 months agoCopilot Both copilot embedded in Github browser and embedded in VScode are saying unavailable whenever a prompt is entered
Dang
3 months agoCopilot Claude 3.5 Sonnet The return was not
Wuffel
3 months agoCopilot Copilot is not answering at all in PyCharm. So response. Nothing.
Samuel
3 months agoCopilot no completions are proposed, and "open completions pane" shows zero completions. github copilot chat works fine.
Slav
3 months agoCopilot GitHub Copilot VSCode Extension can't connect to authentication provider and gives the following message in output logs: "Error getting a session: Timed out waiting for authentication provider to register"
Umair
3 months agoCopilot I am unable to access github copilot on web
IsDown has tracked 642 incidents since started monitoring GitHub status in April 2020.
2 days ago · lasted about 2 hours
We are investigating reports of degraded performance for Pull Requests More details
3 days ago · lasted 2 days
We are currently investigating this issue. More details
3 days ago · lasted 42 minutes
We are currently investigating this issue. More details
We've tracked and collected 642 incidents since started monitoring GitHub status
Number of Incidents
18 issues
Last incident
2 days ago
AWS
Google Cloud
Google Workspace
Azure
Cloudflare
Slack
Zoom
Datadog US1
Figma
Adobe
HubSpot
Microsoft 365
Aircall
Stripe
Airtable
Why teams choose IsDown:
14-day free trial • No credit card required
Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.
When GitHub is down, start by checking the official status page and IsDown's monitoring. If PRs, repository access, or deployment processes are affected, try using alternative workflows. If it's a network or connectivity issue, verify whether it's on GitHub's end or a local problem by testing a different network or clearing the DNS cache.
Keeping track of GitHub status updates helps in understanding the outage. In cases of widespread disruptions, teams can mitigate the impact by delaying non-critical tasks or working offline until service is restored.
IsDown provides real-time alerts when GitHub experiences disruptions. Users can set up notifications via Slack, PagerDuty, or email to stay informed. Whether it's a network problem, database failure, or deployment delay, IsDown keeps users updated. Tracking GitHub status checks ensures teams are aware of potential service interruptions before they escalate.
Yes, when GitHub experiences an outage, it can significantly disrupt software development workflows. Developers may be unable to push code, merge pull requests (PRs), or access repositories. This can delay releases, hinder collaboration, and affect automation pipelines, particularly in DevOps and CI/CD environments where GitHub is integrated with build and deployment processes.
GitHub outages can be caused by infrastructure failures, database issues, network congestion, or planned/unplanned system maintenance. Problems with query performance, API rate limits, or repository indexing may slow down searches and repository access. To determine whether an issue is widespread or isolated, developers should check GitHub's official status page and third-party monitoring platforms like IsDown for real-time outage reports.
To reduce the impact of GitHub downtime, teams should implement contingency workflows. This may include maintaining local repositories for offline work, setting up alternative version control systems (e.g., GitLab, Bitbucket), or using mirrored repositories. For CI/CD pipelines, integrating multiple service providers can ensure redundancy. Regularly monitoring GitHub status updates allows teams to react proactively and adjust workflows as needed.
Currently there's no report of GitHub being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the GitHub official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
GitHub last outage was on April 16, 2025 with the title "Incident with Pull Requests"
Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor GitHub and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.
IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
IsDown offers an easy way to monitor GitHub with maximum flexibility
IsDown monitors GitHub for major outages. A major outage is when GitHub experiences a critical issue that severely affects one or more services/regions. When GitHub marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.
IsDown monitors GitHub status page for minor outages. A minor outage is when GitHub experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.
IsDown collects all information from the outages published in GitHub status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
GitHub publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.
IsDown monitors GitHub and all their 11 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
GitHub and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.
“Very happy with isDown. Setting up and managing the monitoring is straightforward. The customer support team has been excellent, always quick to answer questions and provide assistance.
I definitely recommend IsDown.”
The data and notifications you need, in the tools you already use.
14-day free trial · No credit card required · No code required
