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
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 4, 2025
No incidents reported today.
May 3, 2025
No incidents reported.
May 2, 2025
No incidents reported.
May 1, 2025
Resolved -
This incident has been resolved.
May 1, 23:13 UTC
May 1, 23:13 UTC
Update -
We have identified the underlying cause of attachment upload failures to Issues and mitigated it by rolling back a feature flag. If you are still experiencing failures when uploading attachments to Issues, please reload your page.
May 1, 23:13 UTC
May 1, 23:13 UTC
Update -
We are investigating attachment upload failures on Issues. We will continue to keep users updated on progress towards mitigation.
May 1, 22:29 UTC
May 1, 22:29 UTC
Investigating -
We are investigating reports of degraded availability for Issues
May 1, 22:28 UTC
May 1, 22:28 UTC
Apr 30, 2025
Resolved -
On April 30, 2025, between 8:02 UTC and 9:05 UTC, the Pull Requests service was degraded and failed to update refs for repositories with higher traffic. This was due to a repository migration creating a larger than usual number of enqueued jobs. This resulted in an increase in job failures, delays for non-migration sourced jobs, and delays to tracking refs.
We declared an incident once we confirmed that this issue was not isolated to the migrating repository and other repositories were also failing to process ref updates.
We mitigated the incident by shifting the migration jobs to a different job queue.
To avoid problems like this in the future, we are revisiting our repository migration process and are working to isolate potentially problematic migration workloads from non-migration workloads.
Apr 30, 21:05 UTC
We declared an incident once we confirmed that this issue was not isolated to the migrating repository and other repositories were also failing to process ref updates.
We mitigated the incident by shifting the migration jobs to a different job queue.
To avoid problems like this in the future, we are revisiting our repository migration process and are working to isolate potentially problematic migration workloads from non-migration workloads.
Apr 30, 21:05 UTC
Update -
Some customers of github.com are reporting issues with PR tracking refs not being updated due to processing delays and increased failure rates. We're investigating the source of the issue.
Apr 30, 20:53 UTC
Apr 30, 20:53 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests
Apr 30, 20:51 UTC
Apr 30, 20:51 UTC
Apr 29, 2025
Resolved -
On April 29th, 2025, between 8:40am UTC and 12:50pm UTC the notifications service was degraded and stopped delivering most web and email notifications as well as some mobile push notifications. This was due to a large and faulty schema migration that rendered a set of database primaries unhealthy, affecting the notification delivery pipelines, causing delays in the most of the web and email notification deliveries.
We mitigated the incident by stopping the migration and promoting replicas to replace the unhealthy primaries.
In order to prevent similar incidents in the future, we are addressing the underlying issues in the online schema tooling and improving the way we interact with the database to not be disruptive to production workloads.
Apr 29, 12:52 UTC
We mitigated the incident by stopping the migration and promoting replicas to replace the unhealthy primaries.
In order to prevent similar incidents in the future, we are addressing the underlying issues in the online schema tooling and improving the way we interact with the database to not be disruptive to production workloads.
Apr 29, 12:52 UTC
Update -
The notification delivery backlog has been processed and notifications are now being delivered as expected.
Apr 29, 12:52 UTC
Apr 29, 12:52 UTC
Update -
New notification deliveries are occuring in a timely manner and we have processed a significant portion of the backlog. Users may still notice delayed delivery of some older notifications.
Apr 29, 12:45 UTC
Apr 29, 12:45 UTC
Update -
Web and email notifications continue to be delivered successfully and the service is in a healthy state. We are processing the backlog of notification deliveries which are currently as much as 30-60 minutes delayed.
Apr 29, 11:57 UTC
Apr 29, 11:57 UTC
Update -
We are starting to see signals of recovery with delayed web/email notifications now being dispatched.
The team continue to monitor recovery and ensure return to normal service.
Apr 29, 11:09 UTC
The team continue to monitor recovery and ensure return to normal service.
Apr 29, 11:09 UTC
Update -
We are seeing impact on both web and email notifications with most customers seeing delayed deliveries.
The last incident updated regarding impact on email notifications was incorrect. Email notifications have been experiencing the same delays as web notifications for duration of incident.
We have applied changes to our system and are monitoring to see if these restore normal service. Updates to follow.
Apr 29, 10:37 UTC
The last incident updated regarding impact on email notifications was incorrect. Email notifications have been experiencing the same delays as web notifications for duration of incident.
We have applied changes to our system and are monitoring to see if these restore normal service. Updates to follow.
Apr 29, 10:37 UTC
Update -
Web notifications are experiencing delivery delays for the majority of customers. We are working to mitigate impact and restore delivery times back within normal operating bounds.
Email notifications remain unaffected and are delivering as normal.
We will provide futher updates as we have more information.
Apr 29, 10:07 UTC
Email notifications remain unaffected and are delivering as normal.
We will provide futher updates as we have more information.
Apr 29, 10:07 UTC
Investigating -
We are currently investigating this issue.
Apr 29, 10:05 UTC
Apr 29, 10:05 UTC
Apr 28, 2025
Resolved -
This incident has been resolved.
Apr 28, 11:09 UTC
Apr 28, 11:09 UTC
Update -
We are seeing signs of recovery and continue to monitor latency.
Apr 28, 10:35 UTC
Apr 28, 10:35 UTC
Update -
We continue to investigate impact to Issues and Pull Requests. Customers may see some timeouts as we work towards mitigation.
Apr 28, 09:52 UTC
Apr 28, 09:52 UTC
Update -
We are continuing to investigate impact to Issues and Pull Requests. We will provide more updates as we have them.
Apr 28, 08:58 UTC
Apr 28, 08:58 UTC
Update -
Users may see timeouts when viewing Pull Requests. We are still investigating the issues related to Issues and Pull Requests and will provide further updates as soon as we can
Apr 28, 08:23 UTC
Apr 28, 08:23 UTC
Update -
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Apr 28, 08:21 UTC
Apr 28, 08:21 UTC
Update -
Issues API is currently seeing elevated latency. We are investigating the issue and will provide further updates as soon as we have them.
Apr 28, 08:05 UTC
Apr 28, 08:05 UTC
Investigating -
We are investigating reports of degraded performance for API Requests, Git Operations and Issues
Apr 28, 08:03 UTC
Apr 28, 08:03 UTC
Apr 27, 2025
No incidents reported.
Apr 26, 2025
No incidents reported.
Apr 25, 2025
No incidents reported.
Apr 24, 2025
No incidents reported.
Apr 23, 2025
Resolved -
Starting at 19:13:50 UTC, the service responsible for importing Git repositories began experiencing errors that impacted both GitHub Enterprise Importer migrations and the GitHub Importer which were restored at 22:11:00 UTC. At the time, 837 migrations across 57 organizations were affected. Impacted migrations would have shown the error message "Git source migration failed. Error message: An error occurred. Please contact support for further assistance." in the migration logs and required a retry.
The root cause of the issue was a recent configuration change that caused our workers, responsible for syncing the Git repository, to lose the necessary access required for the migration. We were able to retrieve the needed access for the workers , and all dependent services resumed normal operation.
We’ve identified and implemented additional safeguards to help prevent similar disruptions in the future.
Apr 23, 22:20 UTC
The root cause of the issue was a recent configuration change that caused our workers, responsible for syncing the Git repository, to lose the necessary access required for the migration. We were able to retrieve the needed access for the workers , and all dependent services resumed normal operation.
We’ve identified and implemented additional safeguards to help prevent similar disruptions in the future.
Apr 23, 22:20 UTC
Update -
We are investigating issues with GitHub Enterprise Importer. We will continue to keep users updated on progress towards mitigation.
Apr 23, 21:44 UTC
Apr 23, 21:44 UTC
Investigating -
We are currently investigating this issue.
Apr 23, 21:38 UTC
Apr 23, 21:38 UTC
Resolved -
On April 23, 2025, between 07:00 UTC and 07:20 UTC, multiple GitHub services experienced degradation caused by resource contention on database hosts. The resulting error rates, which ranged from 2–5% of total requests, led to intermittent service disruption for users. The issue was triggered by heavy workloads on the database leading to connection saturation.
The incident mitigated when the database throttling activated which allowed the system to rebalance the connections. This restored the traffic flow to the database and restored service functionality.
To prevent similar issues in the future, we are reviewing the capacity of the database, improving monitoring and alerting systems, and implementing safeguards to reduce time to detection and mitigation.
Apr 23, 08:00 UTC
The incident mitigated when the database throttling activated which allowed the system to rebalance the connections. This restored the traffic flow to the database and restored service functionality.
To prevent similar issues in the future, we are reviewing the capacity of the database, improving monitoring and alerting systems, and implementing safeguards to reduce time to detection and mitigation.
Apr 23, 08:00 UTC
Update -
A brief problem with one of our database clusters caused intermittent errors around 07:05 UTC for a few minutes. Our systems have recovered and we continue to monitor.
Apr 23, 07:47 UTC
Apr 23, 07:47 UTC
Update -
Issues is operating normally.
Apr 23, 07:43 UTC
Apr 23, 07:43 UTC
Update -
Actions is operating normally.
Apr 23, 07:42 UTC
Apr 23, 07:42 UTC
Update -
Pages is operating normally.
Apr 23, 07:42 UTC
Apr 23, 07:42 UTC
Update -
API Requests is operating normally.
Apr 23, 07:42 UTC
Apr 23, 07:42 UTC
Update -
Codespaces is operating normally.
Apr 23, 07:41 UTC
Apr 23, 07:41 UTC
Update -
Codespaces is experiencing degraded performance. We are continuing to investigate.
Apr 23, 07:23 UTC
Apr 23, 07:23 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
Apr 23, 07:22 UTC
Apr 23, 07:22 UTC
Investigating -
We are investigating reports of degraded performance for API Requests, Issues and Pages
Apr 23, 07:17 UTC
Apr 23, 07:17 UTC
Apr 22, 2025
Completed -
The scheduled maintenance has been completed.
Apr 22, 16:30 UTC
Apr 22, 16:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 21, 16:30 UTC
Apr 21, 16:30 UTC
Scheduled -
Codespaces will be undergoing global maintenance from 16:30 UTC on Monday, April 21 to 16:30 UTC on Tuesday, April 22. 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.
Apr 17, 15:30 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.
Apr 17, 15:30 UTC
Apr 21, 2025
Apr 20, 2025
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe