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
Jun 6, 2025
No incidents reported today.
Jun 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.
Jun 5, 19:29 UTC
Jun 5, 19:29 UTC
Update -
We have applied a mitigation and we are beginning to see recovery. We are continuing to monitor for recovery.
Jun 5, 19:02 UTC
Jun 5, 19:02 UTC
Update -
Actions is experiencing degraded availability. We are continuing to investigate.
Jun 5, 18:35 UTC
Jun 5, 18:35 UTC
Update -
Users of Actions will see delays in jobs starting or job failures. Users of Pages will see slow or failed deployments
Jun 5, 18:30 UTC
Jun 5, 18:30 UTC
Update -
Pages is experiencing degraded performance. We are continuing to investigate.
Jun 5, 18:01 UTC
Jun 5, 18:01 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Jun 5, 18:00 UTC
Jun 5, 18:00 UTC
Jun 4, 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.
Jun 4, 15:55 UTC
Jun 4, 15:55 UTC
Update -
We have applied mitigations and are monitoring for recovery.
Jun 4, 15:39 UTC
Jun 4, 15:39 UTC
Update -
We are currently investigating delays with Actions triggering for some users.
Jun 4, 15:19 UTC
Jun 4, 15:19 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Jun 4, 15:15 UTC
Jun 4, 15:15 UTC
Jun 3, 2025
No incidents reported.
Jun 2, 2025
No incidents reported.
Jun 1, 2025
No incidents reported.
May 31, 2025
Completed -
The scheduled maintenance has been completed.
May 31, 04:30 UTC
May 31, 04:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 29, 21:30 UTC
May 29, 21:30 UTC
Scheduled -
Codespaces will be undergoing global maintenance from May 29, 2025 21:30 UTC to May 31, 2025 4:30 UTC. 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 29, 21:01 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 29, 21:01 UTC
May 30, 2025
Resolved -
On May 30, 2025, between 08:10 UTC and 16:00 UTC, the Microsoft Teams GitHub integration service experienced a complete service outage.
During this period, the service was unable to deliver notifications or process user requests, resulting in a 100% error rate for all integration functionality except link previews.
This outage was due to an authentication issue with our downstream provider. We mitigated the incident by working with our provider to restore service functionality and are working to migrate to more durable authentication methods to reduce the risk of similar issues in the future.
May 30, 15:57 UTC
During this period, the service was unable to deliver notifications or process user requests, resulting in a 100% error rate for all integration functionality except link previews.
This outage was due to an authentication issue with our downstream provider. We mitigated the incident by working with our provider to restore service functionality and are working to migrate to more durable authentication methods to reduce the risk of similar issues in the future.
May 30, 15:57 UTC
Update -
Our team is continuing to work to mitigate the source of the disruption affecting a small set of customers using the GitHub Microsoft Teams integration.
May 30, 14:47 UTC
May 30, 14:47 UTC
Update -
We are experiencing a disruption with our Microsoft Teams integration. Investigations are underway and we will provide further updates as we progress.
May 30, 12:29 UTC
May 30, 12:29 UTC
Investigating -
We are currently investigating this issue.
May 30, 11:20 UTC
May 30, 11:20 UTC
May 29, 2025
Completed -
The scheduled maintenance has been completed.
May 29, 16:30 UTC
May 29, 16:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 16:30 UTC
May 28, 16:30 UTC
Scheduled -
Codespaces will be undergoing global maintenance from 16:30 UTC on Wednesday, May 28 to 16:30 UTC on Thursday, May 29. 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 22, 15:26 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 22, 15:26 UTC
May 28, 2025
Resolved -
On May 28, 2025, from approximately 09:45 UTC to 14:45 UTC, GitHub Actions experienced delayed job starts for workflows in public repos using Ubuntu-24 standard hosted runners. This was caused by a misconfiguration in backend caching behavior after a failover, which led to duplicate job assignments and reduced available capacity. Approximately 19.7% of Ubuntu-24 hosted runner jobs on public repos were delayed. Other hosted runners, self-hosted runners, and private repo workflows were unaffected.
By 12:45 UTC, we mitigated the issue by redeploying backend components to reset state and scaling up available resources to more quickly work through the backlog of queued jobs. We are working to improve our deployment and failover resiliency and validation to reduce the likelihood of similar issues in the future.
May 28, 14:43 UTC
By 12:45 UTC, we mitigated the issue by redeploying backend components to reset state and scaling up available resources to more quickly work through the backlog of queued jobs. We are working to improve our deployment and failover resiliency and validation to reduce the likelihood of similar issues in the future.
May 28, 14:43 UTC
Update -
We are continuing to monitor the affected Actions runners to ensure a smooth recovery.
May 28, 14:35 UTC
May 28, 14:35 UTC
Update -
We are observing indications of recovery with the affected Actions runners.
The team will continue monitoring systems to ensure a return to normal service.
May 28, 13:42 UTC
The team will continue monitoring systems to ensure a return to normal service.
May 28, 13:42 UTC
Update -
We're continuing to investigate delays in Actions runners for hosted Ubuntu 24.
We will provide further updates as more information becomes available.
May 28, 12:41 UTC
We will provide further updates as more information becomes available.
May 28, 12:41 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
May 28, 11:49 UTC
May 28, 11:49 UTC
Update -
Actions is experiencing high wait times for obtaining standard hosted runners for ubuntu 24. Other hosted labels and self-hosted runners are not impacted.
May 28, 11:42 UTC
May 28, 11:42 UTC
Investigating -
We are currently investigating this issue.
May 28, 11:11 UTC
May 28, 11:11 UTC
May 27, 2025
Resolved -
On May 27, 2025, between 09:31 UTC and 13:31 UTC, some Actions jobs experienced failures uploading to and downloading from the Actions Cache service. During the incident, 6% of all workflow runs couldn’t upload or download cache entries from the service, resulting in a non-blocking warning message in the logs and performance degradation. The disruption was caused by an infrastructure update related to the retirement of a legacy service, which unintentionally impacted Cache service availability. We resolved the incident by reverting the change and have since implemented a permanent fix to prevent recurrence.
We are improving our configuration change processes by introducing additional end-to-end tests to cover the identified gaps, and implementing deployment pipeline improvements to reduce mitigation time for similar issues in the future.
May 27, 13:31 UTC
We are improving our configuration change processes by introducing additional end-to-end tests to cover the identified gaps, and implementing deployment pipeline improvements to reduce mitigation time for similar issues in the future.
May 27, 13:31 UTC
Update -
Mitigation is applied and we’re seeing signs of recovery. We’re monitoring the situation until the mitigation is applied to all affected repositories.
May 27, 13:03 UTC
May 27, 13:03 UTC
Update -
We are experiencing degradation with the GitHub Actions cache service and are working on applying the appropriate mitigations.
May 27, 12:27 UTC
May 27, 12:27 UTC
Investigating -
We are investigating reports of degraded performance for Actions
May 27, 12:26 UTC
May 27, 12: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.
May 27, 12:41 UTC
May 27, 12:41 UTC
Investigating -
We are currently investigating this issue.
May 27, 12:20 UTC
May 27, 12:20 UTC
Resolved -
Between 10:00 and 20:00 UTC on May 27, a change to our git proxy service resulted in some git client implementations not being able to consistently push to GitHub. Reverting the change resulted in an immediate resolution of the problem for all customers. The inflated time to detect this failure was due to the relatively few impacted clients. We are re-evaluating the proposed change to understand how we can
prevent and detect such failures in the future.
May 27, 10:00 UTC
prevent and detect such failures in the future.
May 27, 10:00 UTC
May 26, 2025
Resolved -
On May 26, 2025, between 06:20 UTC and 09:45 UTC GitHub experienced broad failures across a variety of services (API, Issues, Git, etc). These were degraded at times, but peaked at 100% failure rates for some operations during this time.
On May 23, a new feature was added to Copilot APIs and monitored during rollout but it was not tested at peak load. At 6:20 UTC on May 26, load increased on the code path in question and started to degrade a Copilot API because the caching for this endpoint and circuit breakers for high load were misconfigured.
In addition, the traffic limiting meant to protect wider swaths of the GitHub API from queuing was not yet covering this endpoint, meaning it was able to overwhelm the capacity to serve traffic and cause request queuing.
We were able to mitigate the incident by turning off the endpoint until the behavior could be reverted.
We are already working on a quality of service strategy for API endpoints like this that will limit the impact of a broad incident and are rolling it out. We are also addressing the specific caching and circuit breaker misconfigurations for this endpoint, which would have reduced the time to mitigate this particular incident and the blast radius.
May 26, 10:17 UTC
On May 23, a new feature was added to Copilot APIs and monitored during rollout but it was not tested at peak load. At 6:20 UTC on May 26, load increased on the code path in question and started to degrade a Copilot API because the caching for this endpoint and circuit breakers for high load were misconfigured.
In addition, the traffic limiting meant to protect wider swaths of the GitHub API from queuing was not yet covering this endpoint, meaning it was able to overwhelm the capacity to serve traffic and cause request queuing.
We were able to mitigate the incident by turning off the endpoint until the behavior could be reverted.
We are already working on a quality of service strategy for API endpoints like this that will limit the impact of a broad incident and are rolling it out. We are also addressing the specific caching and circuit breaker misconfigurations for this endpoint, which would have reduced the time to mitigate this particular incident and the blast radius.
May 26, 10:17 UTC
Update -
We continue to see signs of recovery.
May 26, 10:09 UTC
May 26, 10:09 UTC
Update -
Issues is operating normally.
May 26, 09:51 UTC
May 26, 09:51 UTC
Update -
Git Operations is operating normally.
May 26, 09:46 UTC
May 26, 09:46 UTC
Update -
API Requests is operating normally.
May 26, 09:44 UTC
May 26, 09:44 UTC
Update -
Copilot is operating normally.
May 26, 09:43 UTC
May 26, 09:43 UTC
Update -
Packages is operating normally.
May 26, 09:43 UTC
May 26, 09:43 UTC
Update -
Actions is operating normally.
May 26, 09:42 UTC
May 26, 09:42 UTC
Update -
Packages is experiencing degraded performance. We are continuing to investigate.
May 26, 08:39 UTC
May 26, 08:39 UTC
Update -
Copilot is experiencing degraded performance. We are continuing to investigate.
May 26, 08:26 UTC
May 26, 08:26 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
May 26, 08:25 UTC
May 26, 08:25 UTC
Update -
We are continuing to investigate degraded performance.
May 26, 07:53 UTC
May 26, 07:53 UTC
Update -
Issues is experiencing degraded performance. We are continuing to investigate.
May 26, 07:35 UTC
May 26, 07:35 UTC
Investigating -
We are investigating reports of degraded performance for API Requests and Git Operations
May 26, 07:21 UTC
May 26, 07:21 UTC
May 25, 2025
No incidents reported.
May 24, 2025
No incidents reported.
May 23, 2025
Resolved -
On May 23, 2025, between 17:40 UTC and 18:30 UTC public API and UI requests to read and write Git repository content were degraded and triggered user-facing 500 responses. On average, the error rate was 61% and peaked at 88% of requests to the service. This was due to the introduction of an uncaught fatal error in an internal service. A manual rollback was required which increased the time to remediate the incident.
We are working to automatically detect and revert a change based on alerting to reduce our time to detection and mitigation. In addition, we are adding relevant test coverage to prevent errors of this type getting to production.
May 23, 18:33 UTC
We are working to automatically detect and revert a change based on alerting to reduce our time to detection and mitigation. In addition, we are adding relevant test coverage to prevent errors of this type getting to production.
May 23, 18:33 UTC
Update -
API Requests is operating normally.
May 23, 18:33 UTC
May 23, 18:33 UTC
Update -
API Requests is experiencing degraded performance. We are continuing to investigate.
May 23, 18:26 UTC
May 23, 18:26 UTC
Investigating -
We are currently investigating this issue.
May 23, 18:21 UTC
May 23, 18:21 UTC
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe