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
May 20, 2025
No incidents reported today.
May 19, 2025
No incidents reported.
May 18, 2025
No incidents reported.
May 17, 2025
Resolved -
Between May 16, 2025, 1:21 PM UTC and May 17, 2025, 2:26 AM UTC, the GitHub Enterprise Importer service was degraded and experienced slow processing of customer migrations. Customers may have seen extended wait times for migrations to start or complete.
This incident was initially observed as a slowdown in migration processing. During our investigation, we identified that a recent change aimed at improving API query performance caused an increase in load signals, which triggered migration throttling. As a result, the performance of migrations was negatively impacted, and overall migration duration increased. In parallel, we identified a race condition that caused a specific migration to be repeatedly re-queued, further straining system resources and contributing to a backlog of migration jobs, resulting in accumulated delays. No data was lost, and all migrations were ultimately processed successfully.
We have reverted the feature flag associated with a query change and are working to improve system safeguards to help prevent similar race condition issues from occurring in the future.
May 17, 02:27 UTC
This incident was initially observed as a slowdown in migration processing. During our investigation, we identified that a recent change aimed at improving API query performance caused an increase in load signals, which triggered migration throttling. As a result, the performance of migrations was negatively impacted, and overall migration duration increased. In parallel, we identified a race condition that caused a specific migration to be repeatedly re-queued, further straining system resources and contributing to a backlog of migration jobs, resulting in accumulated delays. No data was lost, and all migrations were ultimately processed successfully.
We have reverted the feature flag associated with a query change and are working to improve system safeguards to help prevent similar race condition issues from occurring in the future.
May 17, 02:27 UTC
Update -
We continue to see signs of recovery for GitHub Enterprise Importer migrations. Queue depth is decreasing and migration duration is trending toward normal levels. We will continue to monitor improvements.
May 17, 02:26 UTC
May 17, 02:26 UTC
Update -
We have identified the source of increased load and have started mitigation. Customers using the GitHub Enterprise Importer may still see extended wait times until recovery completes.
May 16, 22:33 UTC
May 16, 22:33 UTC
Update -
Investigations on the incident impacting GitHub Enterprise Importer continue. An additional contributing cause has been identified, and we are working to ship additional mitigating measures.
May 16, 20:36 UTC
May 16, 20:36 UTC
Update -
We have taken several steps to mitigate the incident impacting GitHub Enterprise Importer (GEI). We are seeing early indications of system recovery. However, customers may continue to experience longer migrations and extended queue times. The team is continuing to work on further mitigating efforts to speed up recovery.
May 16, 18:19 UTC
May 16, 18:19 UTC
Update -
We are continuing to investigate issues with the GitHub Enterprise Importer. Customers may experience slower migration processes and extended wait times.
May 16, 15:32 UTC
May 16, 15:32 UTC
Update -
We are investigating issues with the GitHub Enterprise Importer. Customers may experience slower migration processes and extended wait times.
May 16, 14:06 UTC
May 16, 14:06 UTC
Investigating -
We are currently investigating this issue.
May 16, 13:46 UTC
May 16, 13:46 UTC
May 16, 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.
May 16, 15:24 UTC
May 16, 15:24 UTC
Update -
We are investigating issues with the audit log. Users querying Git audit log data may observe increased latencies and occasional timeouts.
May 16, 10:22 UTC
May 16, 10:22 UTC
Investigating -
We are currently investigating this issue.
May 16, 09:22 UTC
May 16, 09:22 UTC
May 15, 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.
May 15, 22:58 UTC
May 15, 22:58 UTC
Update -
The issues with our upstream model provider have been resolved, and Gemini 2.5 Pro is available again in Copilot Chat, VS Code, and other Copilot products.
We will continue monitoring to ensure stability, but mitigation is complete.
May 15, 22:57 UTC
We will continue monitoring to ensure stability, but mitigation is complete.
May 15, 22:57 UTC
Update -
We have started to gradually re-enable the Gemini 2.5 Pro model in Copilot Chat, VS Code, and other Copilot products.
May 15, 22:20 UTC
May 15, 22:20 UTC
Update -
We have disabled the Gemini 2.5 Pro model in Copilot Chat, VS Code and other Copilot products due to an issue with an upstream model provider.
Users may still see these models as available for a brief period but we recommend switching to a different model. Other models are not impacted and are available.
Once our model provider has resolved the issues impacting Gemini 2.5 Pro, we will re-enable it.
May 15, 13:16 UTC
Users may still see these models as available for a brief period but we recommend switching to a different model. Other models are not impacted and are available.
Once our model provider has resolved the issues impacting Gemini 2.5 Pro, we will re-enable it.
May 15, 13:16 UTC
Investigating -
We are currently investigating this issue.
May 15, 12:41 UTC
May 15, 12:41 UTC
Completed -
The scheduled maintenance has been completed.
May 15, 16:30 UTC
May 15, 16:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 16:30 UTC
May 14, 16:30 UTC
Scheduled -
Codespaces will be undergoing global maintenance from 16:30 UTC on Wednesday, May 14 to 16:30 UTC on Thursday, May 15. Maintenance will begin in our Europe, Asia, and Australia regions. Once it is complete, maintenance will start in our US regions. Each batch of regions will take approximately three to four hours to complete.
During this time period, users may experience intermittent connectivity issues when creating new Codespaces or accessing existing ones.
To avoid disruptions, ensure that any uncommitted changes are committed and pushed before the maintenance starts. Codespaces with uncommitted changes will remain accessible as usual after the maintenance is complete.
May 13, 19:52 UTC
During this time period, users may experience intermittent connectivity issues when creating new Codespaces or accessing existing ones.
To avoid disruptions, ensure that any uncommitted changes are committed and pushed before the maintenance starts. Codespaces with uncommitted changes will remain accessible as usual after the maintenance is complete.
May 13, 19:52 UTC
Resolved -
On May 15, 2025, between 00:08 AM UTC and 10:21 AM UTC, customers were unable to create fine-grained Personal Access Tokens (PATs) on github.com. This incident was triggered by a recent code change to our front end that unintentionally affected the way certain pages loaded and prevented the PAT creation process from completing.
We mitigated the incident by reverting the problematic change. To reduce the likelihood of similar issues in the future, we are improving our monitoring for page load anomalies and PAT creation failures and improving our safe deployment practices.
May 15, 10:38 UTC
We mitigated the incident by reverting the problematic change. To reduce the likelihood of similar issues in the future, we are improving our monitoring for page load anomalies and PAT creation failures and improving our safe deployment practices.
May 15, 10:38 UTC
Update -
The issue preventing users from creating Personal Access Tokens (PATs) has been resolved. The root cause was identified and a change was reverted to restore functionality. PAT generation is now working as expected.
May 15, 10:38 UTC
May 15, 10:38 UTC
Update -
We have identified the cause, and have a working fix. We will continue to update users.
May 15, 09:56 UTC
May 15, 09:56 UTC
Update -
We are exploring the best path forward, but no new update at this stage.
May 15, 09:20 UTC
May 15, 09:20 UTC
Update -
While we have found a possible cause, we have no update on mitigation steps at this stage. We will continue to keep users updated.
May 15, 08:35 UTC
May 15, 08:35 UTC
Update -
We are investigating fine grained PAT creation failures. We will continue to keep users updated on progress towards mitigation. Existing FGP's are unaffected.
May 15, 07:44 UTC
May 15, 07:44 UTC
Investigating -
We are currently investigating this issue.
May 15, 07:00 UTC
May 15, 07:00 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.
May 15, 01:02 UTC
May 15, 01:02 UTC
Update -
We have received confirmation from our upstream provider that the issue has been resolved. We are seeing significant recovery. The Gemini 2.5 Pro model is now fully available in Copilot Chat, VS Code, and other Copilot products.
May 15, 01:02 UTC
May 15, 01:02 UTC
Update -
We continue experiencing degraded availability for the Gemini 2.5 Pro model in Copilot Chat, VS Code and other Copilot products. We are working closely with our upstream provider to resolve this issue.
May 14, 21:18 UTC
May 14, 21:18 UTC
Update -
We continue experiencing degraded availability for the Gemini 2.5 Pro model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.
May 14, 16:46 UTC
May 14, 16:46 UTC
Update -
We are experiencing degraded availability for the Gemini 2.5 Pro model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.
Other models are available and working as expected.
May 14, 16:01 UTC
Other models are available and working as expected.
May 14, 16:01 UTC
Update -
We keep investigating issues with Gemini 2.5 Pro model which is in Public Preview. Users may see intermittent errors with this model.
May 14, 15:14 UTC
May 14, 15:14 UTC
Investigating -
We are currently investigating this issue.
May 14, 14:39 UTC
May 14, 14:39 UTC
May 14, 2025
May 13, 2025
No incidents reported.
May 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.
May 12, 15:06 UTC
May 12, 15:06 UTC
Investigating -
We are currently investigating this issue.
May 12, 14:53 UTC
May 12, 14:53 UTC
May 11, 2025
No incidents reported.
May 10, 2025
No incidents reported.
May 9, 2025
No incidents reported.
May 8, 2025
Completed -
The scheduled maintenance has been completed.
May 8, 16:30 UTC
May 8, 16:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 7, 16:30 UTC
May 7, 16:30 UTC
Scheduled -
Codespaces will be undergoing global maintenance from 16:30 UTC on Wednesday, May 7 to 16:30 UTC on Thursday, May 8. Maintenance will begin in our Europe, Asia, and Australia regions. Once it is complete, maintenance will start in our US regions. Each batch of regions will take approximately three to four hours to complete.
During this time period, users may experience intermittent connectivity issues when creating new Codespaces or accessing existing ones.
To avoid disruptions, ensure that any uncommitted changes are committed and pushed before the maintenance starts. Codespaces with uncommitted changes will remain accessible as usual after the maintenance is complete.
May 6, 19:29 UTC
During this time period, users may experience intermittent connectivity issues when creating new Codespaces or accessing existing ones.
To avoid disruptions, ensure that any uncommitted changes are committed and pushed before the maintenance starts. Codespaces with uncommitted changes will remain accessible as usual after the maintenance is complete.
May 6, 19:29 UTC
Resolved -
On May 8, 2025, between 14:40 UTC and 16:27 UTC the Git Operations service was degraded causing some pushes and merges to fail. On average, the error rate was 1.4% with a peak error rate of 2.24%. This was due to a configuration change which unexpectedly led a critical service to shut down on a subset of hosts that store repository data.
We mitigated the incident by re-deploying the affected service to restore its functionality.
In order to prevent similar incidents from happening again, we identified the cause that triggered this behavior and mitigated it for future deployments. Additionally, to reduce time to detection we will improve monitoring of the impacted service.
May 8, 16:27 UTC
We mitigated the incident by re-deploying the affected service to restore its functionality.
In order to prevent similar incidents from happening again, we identified the cause that triggered this behavior and mitigated it for future deployments. Additionally, to reduce time to detection we will improve monitoring of the impacted service.
May 8, 16:27 UTC
Update -
Pull Requests is operating normally.
May 8, 16:18 UTC
May 8, 16:18 UTC
Update -
Actions is operating normally.
May 8, 16:12 UTC
May 8, 16:12 UTC
Update -
We have identified the issue and applied mitigations, and are monitoring for recovery.
May 8, 16:03 UTC
May 8, 16:03 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
May 8, 15:23 UTC
May 8, 15:23 UTC
Investigating -
We are investigating reports of degraded performance for Git Operations and Pull Requests
May 8, 15:20 UTC
May 8, 15:20 UTC
May 7, 2025
May 6, 2025
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe