Check if GitHub is down, recent outages, user-reported issues, and outages map.
GitHub is working normally
Report your issue to help others see what's happening with GitHub.
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. Sign up for free to see more GitHub status data.
IsDown has tracked 730 incidents since started monitoring GitHub status in April 2020. We collect data from 4522+ services, and normalize the data to give you a clear picture of the impact of the outage.
| Date | Status | Incident | Duration |
|---|---|---|---|
|
Oct 09, 2025
10:45 AM EDT
|
Major | Incident with Webhooks | about 2 hours |
|
Oct 09, 2025
09:52 AM EDT
|
Minor | Multiple GitHub API endpoints are experiencing errors | 7 minutes |
|
Oct 07, 2025
03:48 PM EDT
|
Minor | Disruption with some GitHub services | about 4 hours |
|
Oct 07, 2025
01:03 PM EDT
|
Never Acknowledged | Possible Outage Indicated by User Reports | about 1 hour |
|
Oct 02, 2025
10:41 PM EDT
|
Minor | Incident with Copilot | about 1 hour |
|
Oct 01, 2025
12:43 PM EDT
|
Minor | Degraded Gemini 2.5 Pro experience in Copilot | 1 day |
|
Oct 01, 2025
03:59 AM EDT
|
Minor | Degraded Performance for GitHub Actions MacOS Runners | about 9 hours |
|
Sep 29, 2025
02:39 PM EDT
|
Minor | Disruption with Gemini 2.5 Pro and Gemini 2.0 Flash in Copilot | 35 minutes |
|
Sep 29, 2025
12:45 PM EDT
|
Major | Disruption with some GitHub services | about 1 hour |
|
Sep 25, 2025
01:00 PM EDT
|
Minor | Disruption with some GitHub services | 37 minutes |
Repository access denied
Repository access denied
Repository access denied
Actions not running
Repository access denied
Very slow connecting to github codespaces in West Europen region. Code modules will not run when eventually connected.
Push/pull failures
Copilot response failure
Codespace is stuck at ShuttingDown for the past hour, and every attempt to export fails. PS C:\Users\michaeljo> gh codespace list organic-goggles-q79x465vrxvgc47v5 organic goggles office-fuel/1JSBridgeRepo codespace_midgard_fullclone ShuttingDown
Reason: Server error: 500
no conversations load and you can not select a model to use
not able to login in vscode
Sorry, your request failed. Please try again. Request id: c06351fd-c2ba-4c10-8995-6917cbfe016f Reason: Server error: 500 Sorry, your request failed. Please try again. Request id: 41735d3d-bc63-444e-bb66-27242261af74 Reason: token expired or invalid: 403
GitHub API rate limit exceeded. Please wait and try again.
unable to access github copilot in visual studio 22
Github Copilot extension for VSCode stopped working. Every time I send a new chat request it tells me that there's an error with the request due to invalid token.
Sorry, your request failed. Please try again. Request id: a32d868c-7f5b-45e5-9ab1-6f12c216b2b0 Reason: token expired or invalid: 403
Sorry, your request failed. Please try again. Request id: 2529862d-d24e-4783-9386-80eaff9cbead Reason: token expired or invalid: 403
Sorry, your request failed. Please try again. Request id: Reason: token expired or invalid: 403
Sorry, your request failed. Please try again. Reason: token expired or invalid: 403
Sorry, your request failed. Please try again. Reason: Token expired or invalid: 403
Sorry, your request failed. Please try again. Request id: e7078385-9d81-4451-9e63-f74da4761561 Reason: token expired or invalid: 403
Sorry, your request failed. Please try again. Request id: [redacted] Reason: token expired or invalid: 403
Getting 403 error in github copiliot
Errors due to token issues
I get this across all models Sorry, your request failed. Please try again. Request id: ### Reason: token expired or invalid: 403
Sorry, your request failed. Please try again. Request id: Reason: token expired or invalid: 403
Getting a generic error in a Jetbrains IDE
token expired or invalid: 403
GitHub API rate limit exceeded. Please wait and try again.
Sorry, your request failed. Please try again. Request id: xxx Reason: token expired or invalid: 403
Sorry, your request failed. Please try again. Request id: xxxxx Reason: token expired or invalid: 403
CoPilot is not responding. (Conversation sidebar is flashing gray)
Copilot functionaliy does not work in VSCode
Copilot chat in intellij is blank screen
Tasks couldn’t be loaded Try again or, if the problem persists, contact support. GitHub status
Request Failed: 400 {"error":{"message":"tools.0.custom.input_schema: JSON schema is invalid. It must match JSON Schema draft 2020-12 (https://json-schema.org/draft/2020-12). Learn more about tool use at https://docs.anthropic.com/en/docs/tool-use.","code":"invalid_request_body"}}
Can't submit CR feedback in GitHub PR as well as submit it to the file. "Error I'm sorry but there was an error. Please try again."
An error occurred while processing your request, please try again later
It is timing out and telling me to try again and hanging in vs code
Agent mode does not work, getting "an error has occurered"
API rate limit exceeded for user ID 678094 (but not even using it)
GitHub Copilot It is not working
"Sorry, no response was returned."
Can't login to the site or use Copilot in VS Code.
service not working with VSCode
https://github.com/settings/copilot/features site and copilot extension for VS Code is down.
The Copilot page is returning an error, and Visual Studio Code displays the following message: “Please contact your enterprise admin to enable your managed account for Copilot Business.”
It's not working in VS Code. Copilot settings page in GitHub redirects to error page.
Not launching in VSCode and Support page is down
Copilto down, says to contact support.
says contact support. Cannot access my copilot page
No Copilot subscription found. WTF?
logged off copilot, can't log back in
Cant access the tool neither the copilot page on github.com
500 error on any copilot query
GitHub Copilot does not work. Says I need to contact support.
Copilot failed to get a response. Please try again.
cannot log into copilot inside visual studio 2022
not responding, says 'contact support'
| Component | Status |
|---|---|
| Git Operations | OK |
| API Requests | OK |
| Webhooks | OK |
| Issues | OK |
| Pull Requests | OK |
| Actions | OK |
| Packages | OK |
| GitHub Pages | OK |
| Codespaces | OK |
| Visit www.githubstatus.com for more information | OK |
| Copilot | OK |
IsDown actively monitors the health of GitHub and several major components.
Services commonly monitored together with GitHub and alternatives
AWS
Google Cloud
Google Workspace
Cloudflare
Microsoft Azure
Slack
Datadog US1
Zoom
Figma
Microsoft 365
Adobe
HubSpot
Aircall
Stripe
Airtable
GitHub Enterprise Cloud - EU
GitHub Enterprise Cloud Australia
GitHub is a web-based version control and collaboration platform for software developers, offering tools like issue tracking, pull requests, and actions for CI/CD.
Monitoring GitHub since April 2020
Tracking 11 GitHub services and regions
148 incidents in 2025
Number of Incidents
21 issues
Last incident
1 days ago
Be the first to know when GitHub goes down
Monitor All your Vendors in One Place
4522+ third-party services available to monitor
Know Before They Know
Alerts 30+ minutes before official updates
Stop the Ticket Flood
Cut "is it down?" tickets by 80%
IsDown aggregates various status pages from services into a very clear dashboard. Worth every penny.
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 October 09, 2025 with the title "Incident with Webhooks"
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 GitHub 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 instead of just relying on reports from users. The integration allows us to provide more details about GitHub's Outages, 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.
14-day free trial · No credit card required · No code required
