Get email notifications whenever GitHub creates, updates or resolves an incident.
Get text message notifications whenever GitHub creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
All Systems Operational
About This Site
For the status of GitHub Enterprise Cloud - EU, please visit: eu.githubstatus.com
For the status of GitHub Enterprise Cloud - Australia, please visit: au.githubstatus.com
For the status of GitHub Enterprise Cloud - US, please visit: us.githubstatus.com
Git Operations
?
Operational
Webhooks
?
Operational
Visit www.githubstatus.com for more information
Operational
API Requests
?
Operational
Issues
?
Operational
Pull Requests
?
Operational
Actions
?
Operational
Packages
?
Operational
Pages
?
Operational
Codespaces
?
Operational
Copilot
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Nov 14, 2025
No incidents reported today.
Nov 13, 2025
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Nov 13, 15:13 UTC
Nov 13, 15:13 UTC
Update -
Git Operations is experiencing degraded performance. We are continuing to investigate.
Nov 13, 15:03 UTC
Nov 13, 15:03 UTC
Investigating -
We are currently investigating this issue.
Nov 13, 15:00 UTC
Nov 13, 15:00 UTC
Nov 12, 2025
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Nov 12, 23:04 UTC
Nov 12, 23:04 UTC
Update -
We are continuing to investigate connectivity issues with codespaces
Nov 12, 22:51 UTC
Nov 12, 22:51 UTC
Update -
We are investing reports of codespaces no longer appearing in the UI or API. Users may experience connectivity issues to the impacted codespaces.
Nov 12, 22:26 UTC
Nov 12, 22:26 UTC
Investigating -
We are currently investigating this issue.
Nov 12, 22:26 UTC
Nov 12, 22:26 UTC
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Nov 12, 17:39 UTC
Nov 12, 17:39 UTC
Update -
We are continuing to monitor our mitigations to delays in notification deliveries. Some users may still experience delays of over 10 minutes.
Nov 12, 17:15 UTC
Nov 12, 17:15 UTC
Update -
We are continuing to work on mitigating delays in notification deliveries. Some users may still experience delays of over 10 minutes.
Nov 12, 15:35 UTC
Nov 12, 15:35 UTC
Update -
We are continuing to work on mitigating delays in notification deliveries. Some users may experience delays of over 10 minutes.
Nov 12, 14:58 UTC
Nov 12, 14:58 UTC
Update -
We are investigating delays of up to 10 minutes in notification deliveries. Our team has identified the likely cause and is actively working to mitigate the issue.
Nov 12, 14:25 UTC
Nov 12, 14:25 UTC
Investigating -
We are currently investigating this issue.
Nov 12, 14:23 UTC
Nov 12, 14:23 UTC
Nov 11, 2025
Resolved -
On November 11, 2025, between 16:28 UTC and 20:54 UTC, GitHub Actions larger hosted runners experienced degraded performance, with 0.4% of overall workflow runs and 8.8% of larger hosted runner jobs failing to start within 5 minutes. The majority of impact was mitigated by 18:44, with a small tail of organizations taking longer to recover.
The impact was caused by the same database infrastructure issue that caused similar larger hosted runner performance degradation on October 23rd, 2025. In this case, it was triggered by a brief infrastructure event in this incident rather than a database change.
Through this incident, we identified and implemented a better solution for both prevention and faster mitigation. In addition to this, a durable solution for the underlying database issue is rolling out soon.
Nov 11, 20:54 UTC
The impact was caused by the same database infrastructure issue that caused similar larger hosted runner performance degradation on October 23rd, 2025. In this case, it was triggered by a brief infrastructure event in this incident rather than a database change.
Through this incident, we identified and implemented a better solution for both prevention and faster mitigation. In addition to this, a durable solution for the underlying database issue is rolling out soon.
Nov 11, 20:54 UTC
Update -
Mitigation is complete and all new jobs targeting Larger Hosted Runners should not experience delays.
Nov 11, 20:53 UTC
Nov 11, 20:53 UTC
Update -
The team is continuing to apply the mitigation for Large Hosted Runners. We will provide updates as we progress.
Nov 11, 19:40 UTC
Nov 11, 19:40 UTC
Update -
The team continues to investigate delays with Large Hosted Runners. We will continue providing updates on the progress towards mitigation.
Nov 11, 18:37 UTC
Nov 11, 18:37 UTC
Investigating -
We are currently investigating this issue.
Nov 11, 18:02 UTC
Nov 11, 18:02 UTC
Nov 10, 2025
No incidents reported.
Nov 9, 2025
No incidents reported.
Nov 8, 2025
No incidents reported.
Nov 7, 2025
No incidents reported.
Nov 6, 2025
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Nov 6, 00:06 UTC
Nov 6, 00:06 UTC
Update -
We have recovered from our earlier performance issues. Copilot code completions should be functioning normally at this time.
Nov 6, 00:06 UTC
Nov 6, 00:06 UTC
Update -
Copilot Code Completions are partially unavailable. Our engineering team is engaged and investigating.
Nov 5, 23:41 UTC
Nov 5, 23:41 UTC
Investigating -
We are investigating reports of degraded performance for Copilot
Nov 5, 23:41 UTC
Nov 5, 23:41 UTC
Nov 5, 2025
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Nov 5, 23:26 UTC
Nov 5, 23:26 UTC
Update -
We have identified and resolved the underlying issues with Code Completions. Customers should see full recovery.
Nov 5, 23:26 UTC
Nov 5, 23:26 UTC
Update -
We are investigating increased error rates affecting Copilot Code Completions. Some users may experience delays or partial unavailability. Our engineering team is monitoring the situation and working to identify the cause.
Nov 5, 22:57 UTC
Nov 5, 22:57 UTC
Investigating -
We are investigating reports of degraded performance for Copilot
Nov 5, 22:56 UTC
Nov 5, 22:56 UTC
Nov 4, 2025
Resolved -
On November 4, 2025, GitHub Enterprise Importer experienced a period of degraded migration performance and elevated error rates between 18:04 UTC and 23:36 UTC. During this interval customers queueing and running migrations experienced prolonged queue times and slower processing.
The degradation was ultimately connected to higher than normal system load, once load was reduced error rates returned to normal. The investigation is ongoing to pinpoint the precise root cause and prevent future recurrence.
Long-term work is planned to strengthen system resilience under high load and promote better visibility into migration status for customers.
Nov 4, 22:00 UTC
The degradation was ultimately connected to higher than normal system load, once load was reduced error rates returned to normal. The investigation is ongoing to pinpoint the precise root cause and prevent future recurrence.
Long-term work is planned to strengthen system resilience under high load and promote better visibility into migration status for customers.
Nov 4, 22:00 UTC
Nov 3, 2025
Resolved -
On November 3, 2025, between 14:10 UTC and 19:20 UTC, GitHub Packages experienced degraded performance, resulting in failures for 0.5% of Nuget package download requests. The incident resulted from an unexpected change in usage patterns affecting rate limiting infrastructure in the Packages service.
We mitigated the issue by scaling up services and refining our rate limiting implementation to ensure more consistent and reliable service for all users. To prevent similar problems, we are enhancing our resilience to shifts in usage patterns, improving capacity planning, and implementing better monitoring to accelerate detection and mitigation in the future.
Nov 3, 19:20 UTC
We mitigated the issue by scaling up services and refining our rate limiting implementation to ensure more consistent and reliable service for all users. To prevent similar problems, we are enhancing our resilience to shifts in usage patterns, improving capacity planning, and implementing better monitoring to accelerate detection and mitigation in the future.
Nov 3, 19:20 UTC
Update -
We have applied the mitigation and are starting to see signs of recovery. We will continue to monitor the health of the system.
Nov 3, 17:27 UTC
Nov 3, 17:27 UTC
Update -
We are continuing to work on mitigation.
Nov 3, 17:10 UTC
Nov 3, 17:10 UTC
Update -
Progress on mitigation continues but no recovery seen yet to error rates. We will continue to provide updates as we have them.
Nov 3, 15:58 UTC
Nov 3, 15:58 UTC
Update -
We are continuing to see high error rates for package downloads. Our team is working on ways to mitigate this urgently
Next update in 20 minutes
Nov 3, 15:33 UTC
Next update in 20 minutes
Nov 3, 15:33 UTC
Update -
Our investigations are continuing and we are working to mitigate impact. Thank you for your patience as we work on this.
Nov 3, 15:18 UTC
Nov 3, 15:18 UTC
Update -
We are seeing increased failure rates of up to 15% for GitHub Packages downloads with users experiencing 5xx errors.
We are investigating and working towards mitigation. We will continue to provide updates as they are available.
Nov 3, 14:35 UTC
We are investigating and working towards mitigation. We will continue to provide updates as they are available.
Nov 3, 14:35 UTC
Investigating -
We are investigating reports of degraded performance for Packages
Nov 3, 14:33 UTC
Nov 3, 14:33 UTC
Nov 2, 2025
No incidents reported.
Nov 1, 2025
Resolved -
On November 1, 2025, between 2:30 UTC and 6:14 UTC, Actions workflows could not be triggered manually from the UI. This impacted all customers queueing workflows from the UI for most of the impact window. The issue was caused by a faulty code change in the UI, which was promptly reverted once the impact was identified. Detection was delayed due to an alerting gap for UI breaks in this area when all underlying APIs are still healthy. We are implementing enhanced alerting and additional automated tests to prevent similar regressions and reduce detection time in the future.
Nov 1, 06:14 UTC
Nov 1, 06:14 UTC
Update -
Actions is operating normally.
Nov 1, 06:14 UTC
Nov 1, 06:14 UTC
Update -
We have mitigated the issue for manually dispatching workflows via the UI
Nov 1, 06:14 UTC
Nov 1, 06:14 UTC
Update -
We have identified the cause of the issue and are working towards a mitigation
Nov 1, 05:35 UTC
Nov 1, 05:35 UTC
Update -
We are investigating issues manually dispatching workflows via the GitHub UI for Actions. The Workflow Dispatch API is unaffected.
Nov 1, 05:05 UTC
Nov 1, 05:05 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Nov 1, 04:43 UTC
Nov 1, 04:43 UTC
Oct 31, 2025
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe