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
Git Operations
?
Operational
API Requests
?
Operational
Webhooks
?
Operational
Visit www.githubstatus.com for more information
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
Jul 6, 2023
No incidents reported today.
Jul 5, 2023
Resolved -
This incident has been resolved.
Jul 5, 11:37 UTC
Jul 5, 11:37 UTC
Update -
Pull Requests is continuing to operate normally following earlier issues.
We are synchronising impacted pull requests in the background. If there are any further issues we will status again.
Jul 5, 11:35 UTC
We are synchronising impacted pull requests in the background. If there are any further issues we will status again.
Jul 5, 11:35 UTC
Update -
Reprocessing of unprocessed pushes from earlier continues. We will continue to provide progress updates.
Reminder that all new pushes are working as usual.
Jul 5, 11:22 UTC
Reminder that all new pushes are working as usual.
Jul 5, 11:22 UTC
Update -
We have identified impacted pushes to repositories and are reprocessing these. We will provide updates as we progress.
As previously stated, all new pushes will be processed as usual.
Jul 5, 10:30 UTC
As previously stated, all new pushes will be processed as usual.
Jul 5, 10:30 UTC
Update -
We are working to identify all impacted pushes. Once identified, we will reprocess these. We will provide updates as we progress.
As previously stated, all new pushes will be processed as usual.
Jul 5, 09:55 UTC
As previously stated, all new pushes will be processed as usual.
Jul 5, 09:55 UTC
Update -
We have identified an issue that caused pull requests to not reflect additional git pushes over the last several hours. New pushes will now be processed as normal.
Jul 5, 07:09 UTC
Jul 5, 07:09 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests.
Jul 5, 05:54 UTC
Jul 5, 05:54 UTC
Jul 4, 2023
No incidents reported.
Jul 3, 2023
Resolved -
This incident has been resolved.
Jul 3, 13:47 UTC
Jul 3, 13:47 UTC
Update -
We are aware of an increase in 5xx errors for Pull Requests. Our team has been working on mitigation for the past 40 minutes and expects to see full recovery in the next 20 minutes.
Jul 3, 13:22 UTC
Jul 3, 13:22 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests.
Jul 3, 13:18 UTC
Jul 3, 13:18 UTC
Jul 2, 2023
No incidents reported.
Jul 1, 2023
No incidents reported.
Jun 30, 2023
No incidents reported.
Jun 29, 2023
Resolved -
From 17:39-18:12 UTC GitHub was down in parts of North America, particularly the US East coast, and South America.
GitHub takes measures to ensure that we have redundancy in our system for various disaster scenarios. We have been working on building redundancy to an earlier single point of failure in our network architecture at a second Internet edge facility. This second Internet edge facility was completed in January and has been actively routing production traffic since then. Today we were performing a live failover test to validate that we could in fact use this second Internet edge facility if the primary were to fail. Unfortunately, during this failover we inadvertently caused a production outage.
During the test we exposed that the secondary site had a network pathing configuration issue that prevented it from properly functioning as the primary facility. This caused issues with Internet connectivity to GitHub, ultimately resulting in an outage. We were immediately notified of the issue in our monitoring and alerting. Within two minutes of being alerted we reverted the change and brought the primary facility back online. Once online it took time for traffic to be rebalanced and for our border routers to reconverge restoring public connectivity to affected GitHub systems.
This failover test helped expose the configuration issue, and we are addressing the gaps in both configuration and our failover testing which will help make GitHub more resilient. We recognize the severity of this outage and apologize for the impact it has to our customers.
Jun 29, 18:36 UTC
GitHub takes measures to ensure that we have redundancy in our system for various disaster scenarios. We have been working on building redundancy to an earlier single point of failure in our network architecture at a second Internet edge facility. This second Internet edge facility was completed in January and has been actively routing production traffic since then. Today we were performing a live failover test to validate that we could in fact use this second Internet edge facility if the primary were to fail. Unfortunately, during this failover we inadvertently caused a production outage.
During the test we exposed that the secondary site had a network pathing configuration issue that prevented it from properly functioning as the primary facility. This caused issues with Internet connectivity to GitHub, ultimately resulting in an outage. We were immediately notified of the issue in our monitoring and alerting. Within two minutes of being alerted we reverted the change and brought the primary facility back online. Once online it took time for traffic to be rebalanced and for our border routers to reconverge restoring public connectivity to affected GitHub systems.
This failover test helped expose the configuration issue, and we are addressing the gaps in both configuration and our failover testing which will help make GitHub more resilient. We recognize the severity of this outage and apologize for the impact it has to our customers.
Jun 29, 18:36 UTC
Update -
We have recovered and are operating normally
Jun 29, 18:35 UTC
Jun 29, 18:35 UTC
Update -
The root cause has been mitigated and most services have fully recovered. We are still monitoring for full recovery.
Jun 29, 18:33 UTC
Jun 29, 18:33 UTC
Update -
We are continuing to investigate this issue.
Jun 29, 18:22 UTC
Jun 29, 18:22 UTC
Update -
We are continuing to see recovery and are continuing to monitor as recovery continues.
Jun 29, 18:20 UTC
Jun 29, 18:20 UTC
Update -
We are starting to see recovery and are continuing to monitor as we mitigate.
Jun 29, 18:12 UTC
Jun 29, 18:12 UTC
Update -
We have identified the root cause of the outage and are working toward mitigation
Jun 29, 18:02 UTC
Jun 29, 18:02 UTC
Investigating -
We are currently experiencing an outage of GitHub products and are investigating.
Jun 29, 17:52 UTC
Jun 29, 17:52 UTC
Resolved -
This incident has been resolved.
Jun 29, 17:19 UTC
Jun 29, 17:19 UTC
Update -
The third party provider GitHub uses is continuing to work through the issue that is causing delays for some customers with Actions Larger Runners and has started applying mitigations.
Jun 29, 16:30 UTC
Jun 29, 16:30 UTC
Update -
The third party provider GitHub uses is continuing to work through the issue that is causing delays for some customers with Actions Larger Runners and is seeking to provide a mitigation soon.
Jun 29, 15:45 UTC
Jun 29, 15:45 UTC
Update -
A third party provider GitHub uses has identified an issue and is working on recovery over the next hour. Standard Hosted Runners and Self Hosted Runners should not be impacted.
Jun 29, 15:05 UTC
Jun 29, 15:05 UTC
Update -
GitHub Actions customers using Windows and Linux Larger Runners may be experiencing longer than normal queue times.
Jun 29, 15:02 UTC
Jun 29, 15:02 UTC
Investigating -
We are investigating reports of degraded performance for Actions.
Jun 29, 14:51 UTC
Jun 29, 14:51 UTC
Resolved -
This incident has been resolved.
Jun 29, 06:43 UTC
Jun 29, 06:43 UTC
Update -
With the fix deployed, we are now seeing recovery across impacted scenarios.
Jun 29, 06:41 UTC
Jun 29, 06:41 UTC
Update -
We are continuing to rollout the fix for failing Actions jobs using the deployment environments feature. We are expecting the remaining rollout to take another hour
Jun 29, 06:05 UTC
Jun 29, 06:05 UTC
Update -
We are continuing to monitor the rollout of the fix for failing Actions jobs using the deployment environments feature. We are expecting the rollout to take up to another hour
Jun 29, 05:24 UTC
Jun 29, 05:24 UTC
Update -
We are continuing to monitor the rollout of the fix for failing Actions jobs using the deployment environments feature. We are expecting the rollout to take up to another 1 to 1.5 hours.
Jun 29, 04:54 UTC
Jun 29, 04:54 UTC
Update -
We are continuing to monitor the rollout of the fix for failing Actions jobs using the deployment environments feature. We are expecting the rollout to take up to 1.5 to 2 hours.
Jun 29, 04:19 UTC
Jun 29, 04:19 UTC
Update -
We are monitoring the rollout of a fix for failing Actions jobs using the deployment environments feature. We are expecting the rollout to take a couple more hours.
Jun 29, 03:32 UTC
Jun 29, 03:32 UTC
Update -
We are monitoring the rollout of a fix for failing Actions jobs using environments. The impact on GitHub Pages publishing continues.
Jun 29, 03:12 UTC
Jun 29, 03:12 UTC
Update -
The fix for failing Actions jobs using environments is rolling out. We are expecting the rollout to take several hours to complete. The impact on GitHub Pages continues.
Jun 29, 02:50 UTC
Jun 29, 02:50 UTC
Update -
The fix for failing Actions jobs using environments is rolling out. We are expecting the rollout to take several hours to complete.
Jun 29, 02:02 UTC
Jun 29, 02:02 UTC
Update -
We are deploying a fix for failing Actions jobs using environments. The issue is also impacting GitHub Pages - deployments are pending in an approval stage.
Jun 29, 01:26 UTC
Jun 29, 01:26 UTC
Update -
We continue working on a fix for failing Actions jobs using environments.
Jun 29, 00:37 UTC
Jun 29, 00:37 UTC
Update -
We now understand the root cause of failing Actions jobs using environments. We are working on a fix.
Jun 29, 00:11 UTC
Jun 29, 00:11 UTC
Update -
We are seeing failures in Actions jobs using environments. Downstream impact on the deployments of GitHub Pages. We are investigating more details.
Jun 28, 23:39 UTC
Jun 28, 23:39 UTC
Update -
API Requests is operating normally.
Jun 28, 23:35 UTC
Jun 28, 23:35 UTC
Update -
Pages is experiencing degraded performance. We are continuing to investigate.
Jun 28, 23:15 UTC
Jun 28, 23:15 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
Jun 28, 23:11 UTC
Jun 28, 23:11 UTC
Update -
Actions is operating normally.
Jun 28, 23:01 UTC
Jun 28, 23:01 UTC
Investigating -
We are investigating reports of degraded performance for Actions and API Requests.
Jun 28, 22:59 UTC
Jun 28, 22:59 UTC
Jun 28, 2023
Resolved -
This incident has been resolved.
Jun 28, 11:37 UTC
Jun 28, 11:37 UTC
Update -
We are investigating reports of issues with service(s): Issues, Pull Requests, Actions, Releases. We will continue to keep users updated on progress towards mitigation.
Jun 28, 11:24 UTC
Jun 28, 11:24 UTC
Investigating -
We are investigating reports of degraded performance for Issues and Pull Requests.
Jun 28, 11:21 UTC
Jun 28, 11:21 UTC
Jun 27, 2023
No incidents reported.
Jun 26, 2023
No incidents reported.
Jun 25, 2023
Resolved -
This incident has been resolved.
Jun 25, 07:01 UTC
Jun 25, 07:01 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
Jun 25, 06:41 UTC
Jun 25, 06:41 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests.
Jun 25, 06:40 UTC
Jun 25, 06:40 UTC
Jun 24, 2023
No incidents reported.
Jun 23, 2023
No incidents reported.
Jun 22, 2023
No incidents reported.
