Live GitHub status. See if GitHub is down, view recent outages, and get real-time alerts when problems start.
GitHub is having a major outage
We are currently investigating this issue.
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.
IsDown has tracked 663 incidents since started monitoring GitHub status in April 2020. We collect data from 4200+ services, and normalize the data to give you a clear picture of the impact of the outage.
1 day ago · lasted about 1 hour
We are investigating reports of degraded performance for Actions
1 day ago · lasted 24 minutes
We are currently investigating this issue.
We've tracked and collected 663 incidents since started monitoring GitHub status
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
Sauli
Can't run a workflow manually from website
naveni
cant login into github copilot
linus
stopping right when started
Talha
For last few hours, copilot within vscode won't work. Logs me out.
Akash
github copilot not working and terminating my vs code window
Andi
Github is down, it signed me out and will not let me sign in
Krzysztof
Unable to log in to extension. Models not available
Rajveer
It doesnt return any response
Andrés
Not able to open chat on VSCode
mounir
cant sign in via vs code extension
Rimes
Server outage, here is the error message. Sorry, your request failed. Please try again. Request id: .......................................................................... Reason: Server error: 500
Loganathan
Not able to sign in to Githup copilot in VS code.
Timmer
LLMS unavilable. Cannot login to Copilot
Amal
github copilot down: Reason: Server error: 500
Toon
Language model unavailable
Devyansh
I am not able to use github copilot
Szymon
Copilot on Visual Studio don't work
Chris
GitHub Copilot Agent isn't picking up issues it is assigned to.
Axel
VS Code cannot connect ot Github Copilot - tells me to check my firewall, but even deactivating the firewall gives the same error
Kevin
Can't log in, Copilot initialized failed.
kim
copilot login not working
Nejc
Copilot failed to get ready. Please review the guidance in the Chat view.
James
Can’t send any and sign in
Firman
site GHE to authentication cannot be reached
Gert
failed to connect with copilote via vscode and also on the github site itself, not possible to give any prompts
glenn
crashes and logs me out. Wont allow re-login. displays the 'sign in to use coplit' but won't when a button is clicked—terrible timing in the middle of work.
adrian
Copilot failed to get ready. Please review the guidance in the Chat view.
Leon
Doesnt reply, then crashes and logs me out, won't open the login window when link is clicked
Jorge
Copilot is not returning any responses after sending a prompt. "Sorry, no response was returned."
ste
VS Code extension does not return results (Sorry, no response was returned.)
Ahmad
I keep getting. "sorry no response was returned" error
Alvaro
From PHPStorm plugin, copilot response "Oops, no choices received from the server. Please try again", and from web chat, response "I'm sorry but there was an error. Please try again."
Alexander
Github Copilot keeps pulling network errors.
Hugo
vscode dont work with Github Copilot Error Code: net::ERR_HTTP2_PROTOCOL_ERROR. See issues here, a lot of people have the same problem. Tried with two internet connections... https://github.com/microsoft/vscode-copilot-release/issues?q=is%3Aissue%20state%3Aopen%20Error%20Code%3A%20ne...
Abe
It's saying that is modifying files but it is not doing anything at all.
Union
getting 408 and 429 errors
Mathias
copilot chat isn't working anymor i can only go by the Ctrl+I chat
gery
Integrate Cooilot has a problem completing request.
Guilherme
Requests failed on vscode
Mahesh
Sorry, your request failed. Please try again. Request id: 667f9fbe-8ac4-4d69-bf98-4108c4e5022b Reason: Please check your firewall rules and network connection then try again. Error Code: net::ERR_HTTP2_PROTOCOL_ERROR.
Rafael
Code completion server connection timeout
Lucas
can´t connect my vscode extension
Timothy
Sorry, your request failed. Please try again. ... Reason: Server error: 500
Geoff
Copilot took too long to get ready. Please try again.
Artur
Sorry, your request failed. Please try again. Request id: Reason: Server error: 500
York
Github Copilot not responding
Robert
Copilot is painfully slow regardless of the model I use in VS Code. I have the $10/month paid subscription
Rafael
copilot cannot retorn resposnse: Sorry, no response was returned.
Max
The main page is broken and the actual code space won't even load. I tried restarting my device, tweaked the internet settings, and a lot of other things but it still wouldn't load.
John
Cannot connect to copilot. IDE says "You are currently offline. Please connect to the internet to use copilot" even though I do have internet connection.
Gary
Unable to connect to codespaces
Nuno
Merging pull requests is in a loading state and doesn't validate
John
I see this constantly: "Reason: Request Failed: 400 Bad Request"
Michael
The codespaces are not loading
cindy
Codespaces is not connecting
Matei
Page not loading Console: Uncaught SyntaxError: expected expression, got '<'
Henry
I'm locked in a "Setting up your codespace" screen
Peter
Github action stuck queued for runner for 20 minutes
Revanth
Copilot page now found issue
David
I can't connect to some of my codespaces.
Scheduled for May 28, 2025 at 04:30 PM UTC · until 04:30 PM UTC
Codespaces will be undergoing global maintenance from 16:30 UTC on Wednesday, May 28 to 16:30 UTC on Thursday, May 29. Maintenance will begin in our Europe, Asia, and Australia regions. Once it is complete, maintenance will start in our US regions...
IsDown actively monitors the health of GitHub and several major components.
Be the first to know when GitHub and other third-party services go down
Services commonly monitored together with GitHub
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.
Yes, GitHub might be slow has there's an ongoing outage. You can check the details on the top of the page.
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 May 28, 2025 with the title "Disruption with some GitHub services"
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
