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
Apr 10, 2025
Resolved -
This incident has been resolved.
Apr 10, 00:39 UTC
Apr 10, 00:39 UTC
Update -
Pull Requests is operating normally.
Apr 10, 00:36 UTC
Apr 10, 00:36 UTC
Update -
The team has identified a mitigation and is rolling it out while actively monitoring recovery
Apr 10, 00:19 UTC
Apr 10, 00:19 UTC
Update -
Some users are experiencing delays in pull request updates. After pushing new commits, PRs show a "Processing updates" message, and the new commits do not appear in the pull request view.
Apr 9, 23:39 UTC
Apr 9, 23:39 UTC
Update -
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Apr 9, 23:36 UTC
Apr 9, 23:36 UTC
Investigating -
We are currently investigating this issue.
Apr 9, 23:27 UTC
Apr 9, 23:27 UTC
Apr 9, 2025
Resolved -
This incident has been resolved.
Apr 9, 09:31 UTC
Apr 9, 09:31 UTC
Update -
We saw a period of delays on Pull request experiences. The impact is over at the moment, but we are investigating to prevent a repeat.
Apr 9, 09:28 UTC
Apr 9, 09:28 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests
Apr 9, 09:00 UTC
Apr 9, 09:00 UTC
Apr 8, 2025
Resolved -
On 2025-04-08, between 00:42 and 18:05 UTC, as we rolled out an updated version of our GPT 4o model, we observed that vision capabilities for GPT-4o for Copilot Chat in GitHub were intermittently unavailable. During this period, customers may have been unable to upload image attachments to Copilot Chat in GitHub.
In response, we paused the rollout at 18:05 UTC. Recovery began immediately and telemetry indicates that the issue was fully resolved by 18:21 UTC.
Following this incident, we have identified areas of improvements in our model rollout process, including enhanced monitoring and expanded automated and manual testing of our end-to-end capabilities.
Apr 8, 18:21 UTC
In response, we paused the rollout at 18:05 UTC. Recovery began immediately and telemetry indicates that the issue was fully resolved by 18:21 UTC.
Following this incident, we have identified areas of improvements in our model rollout process, including enhanced monitoring and expanded automated and manual testing of our end-to-end capabilities.
Apr 8, 18:21 UTC
Update -
The issue has been resolved now, and we're actively monitoring the service for any further issues.
Apr 8, 18:20 UTC
Apr 8, 18:20 UTC
Update -
Image attachments are not available for some models on Copilot chat on github.com. The issue has been identified and the fix is in progress.
Apr 8, 17:58 UTC
Apr 8, 17:58 UTC
Investigating -
We are currently investigating this issue.
Apr 8, 17:53 UTC
Apr 8, 17:53 UTC
Apr 7, 2025
Resolved -
On April 7, 2025 between 2:15:37 AM UTC and 2:31:14 AM UTC, multiple GitHub services were degraded. Requests to these services returned 5xx errors at a high rate due to an internal database being exhausted by our Codespaces service. The incident mitigated on its own.
We have addressed the problematic queries from the Codespaces service, minimizing the risk of future reoccurrances.
Apr 7, 02:31 UTC
We have addressed the problematic queries from the Codespaces service, minimizing the risk of future reoccurrances.
Apr 7, 02:31 UTC
Update -
Pull Requests is operating normally.
Apr 7, 02:31 UTC
Apr 7, 02:31 UTC
Update -
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Apr 7, 02:24 UTC
Apr 7, 02:24 UTC
Investigating -
We are currently investigating this issue.
Apr 7, 02:19 UTC
Apr 7, 02:19 UTC
Apr 6, 2025
No incidents reported.
Apr 5, 2025
No incidents reported.
Apr 4, 2025
No incidents reported.
Apr 3, 2025
Resolved -
On 2025-04-03, between 6:13:27 PM UTC and 7:12:00 PM UTC the docs.github.com service was degraded and errored. On average, the error rate was 8% and peaked at 20% of requests to the service. This was due to a misconfiguration and elevated requests.
We mitigated the incident by correcting the misconfiguration.
We are working to reduce our time to detection and mitigation of issues like this one in the future.
Apr 3, 19:12 UTC
We mitigated the incident by correcting the misconfiguration.
We are working to reduce our time to detection and mitigation of issues like this one in the future.
Apr 3, 19:12 UTC
Update -
We are investigating and working on applying mitigations to intermittent unavailability of GitHub's Docs.
Apr 3, 18:56 UTC
Apr 3, 18:56 UTC
Investigating -
We are currently investigating this issue.
Apr 3, 18:51 UTC
Apr 3, 18:51 UTC
Completed -
The scheduled maintenance has been completed.
Apr 3, 17:00 UTC
Apr 3, 17:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 2, 17:00 UTC
Apr 2, 17:00 UTC
Scheduled -
Codespaces will be undergoing maintenance in all regions starting from 17:00 UTC on Wednesday, April 2 to 17:00 UTC on Thursday, April 3. Maintenance will begin in Southeast Asia, Central India, Australia Central, and Australia East regions. Once it is complete, maintenance will start in UK South and West Europe, followed by East US, East US2, West US2, and West US3. Each batch of regions will take approximately three to four hours to complete.
During this time period, users may experience connectivity issues with new and existing Codespaces.
If you have uncommitted changes you may need during the maintenance window, you should verify they are committed and pushed before maintenance starts. Codespaces with any uncommitted changes will be accessible as usual once maintenance is complete.
Apr 2, 16:11 UTC
During this time period, users may experience connectivity issues with new and existing Codespaces.
If you have uncommitted changes you may need during the maintenance window, you should verify they are committed and pushed before maintenance starts. Codespaces with any uncommitted changes will be accessible as usual once maintenance is complete.
Apr 2, 16:11 UTC
Apr 2, 2025
Resolved -
Between 2025-03-27 12:00 UTC and 2025-04-03 16:00 UTC, the GitHub Enterprise Cloud Dormant Users report was degraded and falsely indicated that dormant users were active within their business. This was due to increased load on a database from a non-performant query.
We mitigated the incident by increasing the capacity of the database, and installing monitors for this specific report to improve observability for future. As a long-term solution, we are rewriting the Dormant Users report to optimize how it queries for user activity, which will result in significantly faster and accurate report generation.
Apr 2, 20:20 UTC
We mitigated the incident by increasing the capacity of the database, and installing monitors for this specific report to improve observability for future. As a long-term solution, we are rewriting the Dormant Users report to optimize how it queries for user activity, which will result in significantly faster and accurate report generation.
Apr 2, 20:20 UTC
Update -
We are aware that the generation of the Dormant Users Report is delayed for some of our customers, and that the resulting report may be inaccurate. We are actively investigating the root cause and a possible remediation.
Apr 2, 19:09 UTC
Apr 2, 19:09 UTC
Investigating -
We are currently investigating this issue.
Apr 2, 19:08 UTC
Apr 2, 19:08 UTC
Apr 1, 2025
Resolved -
On April 1st, 2025, between 08:17:00 UTC and 09:29:00 UTC the data store powering the Audit Log service experienced elevated errors resulting in an approximate 45 minute delay of Audit Log Events. Our systems maintained data continuity and we experienced no data loss. The delay only affected the Audit Log API and the Audit Log user interface. Any configured Audit Log Streaming endpoints received all relevant Audit Log Events. The data store team deployed mitigating actions which resulted in a full recovery of the data store’s availability.
Apr 1, 09:29 UTC
Apr 1, 09:29 UTC
Update -
The Audit Log is experiencing an increase of failed queries due to availability issues with the associated data store. Audit Log data is experiencing a delay in availability. We have identified the issue and we are deploying mitigating measures.
Apr 1, 09:04 UTC
Apr 1, 09:04 UTC
Investigating -
We are currently investigating this issue.
Apr 1, 08:31 UTC
Apr 1, 08:31 UTC
Mar 31, 2025
Resolved -
Between March 29 7:00 UTC and March 31 17:00 UTC users were unable to unsubscribe from GitHub marketing email subscriptions due to a service outage. Additionally, on March 31, 2025 from 7:00 UTC to 16:40 UTC users were unable to submit eBook and event registration forms on resources.github.com, also due to a service outage.
The incident occurred due to expired credentials used for an internal service. We mitigated it by renewing the credentials and redeploying the affected services. To improve future response times and prevent similar issues, we are enhancing our credential expiry detection, rotation processes, and on-call observability and alerting.
Mar 31, 17:57 UTC
The incident occurred due to expired credentials used for an internal service. We mitigated it by renewing the credentials and redeploying the affected services. To improve future response times and prevent similar issues, we are enhancing our credential expiry detection, rotation processes, and on-call observability and alerting.
Mar 31, 17:57 UTC
Update -
We are currently applying a mitigation to resolve an issue with managing marketing email subscriptions.
Mar 31, 16:46 UTC
Mar 31, 16:46 UTC
Investigating -
We are currently investigating this issue.
Mar 31, 16:27 UTC
Mar 31, 16:27 UTC
Mar 30, 2025
No incidents reported.
Mar 29, 2025
No incidents reported.
Mar 28, 2025
Resolved -
Beginning at 21:24 UTC on March 28 and lasting until 21:50 UTC, some customers of github.com had issues with PR tracking refs not being updated due to processing delays and increased failure rates. We did not status before we completed the rollback, and the incident is currently resolved. We are sorry for the delayed post on githubstatus.com.
Mar 28, 22:50 UTC
Mar 28, 22:50 UTC
Resolved -
This incident was opened by mistake. Public services are currently functional.
Mar 28, 18:14 UTC
Mar 28, 18:14 UTC
Investigating -
We are currently investigating this issue.
Mar 28, 17:53 UTC
Mar 28, 17:53 UTC
Resolved -
Between March 27, 2025, 23:45 UTC and March 28, 2025, 01:40 UTC the Pull Requests service was degraded and failed to update refs for repositories with higher traffic activity. This was due to a large repository migration that resulted in a larger than usual number of enqueued jobs; while simultaneously impacting git fileservers where the problematic repository was hosted. This resulted in an increase in queue depth due to retries on failures to perform those jobs causing delays for non-migration sourced jobs.
We declared an incident once we confirmed that this issue was not isolated to the problematic migration and other repositories were also failing to process ref updates.
We mitigated the issue by stopping the migration and short circuiting the remaining jobs. Additionally, we increased the worker pool of this job to reduce the time required to recover.
As a result of this incident, we are revisiting our repository migration process and are working to isolate potentially problematic migration workloads from non-migration workloads.
Mar 28, 01:40 UTC
We declared an incident once we confirmed that this issue was not isolated to the problematic migration and other repositories were also failing to process ref updates.
We mitigated the issue by stopping the migration and short circuiting the remaining jobs. Additionally, we increased the worker pool of this job to reduce the time required to recover.
As a result of this incident, we are revisiting our repository migration process and are working to isolate potentially problematic migration workloads from non-migration workloads.
Mar 28, 01:40 UTC
Update -
This issue has been mitigated and we are operating normally.
Mar 28, 01:40 UTC
Mar 28, 01:40 UTC
Update -
We are continuing to monitor for recovery.
Mar 28, 00:54 UTC
Mar 28, 00:54 UTC
Update -
We believe we have identified the source of the issue and are monitoring for recovery.
Mar 28, 00:20 UTC
Mar 28, 00:20 UTC
Update -
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Mar 27, 23:52 UTC
Mar 27, 23:52 UTC
Investigating -
We are currently investigating this issue.
Mar 27, 23:49 UTC
Mar 27, 23:49 UTC
Mar 27, 2025
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe