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
Feb 1, 2024
Resolved -
This incident has been resolved.
Feb 1, 04:41 UTC
Feb 1, 04:41 UTC
Update -
This issue has been resolved. A reload of your browser window/tab may be required if you continue to experience issues with the collapsable navigation sidebars not loading.
Feb 1, 04:41 UTC
Feb 1, 04:41 UTC
Update -
We are in the process of deploying a remediation, and expect to see restoration of impacted functionality within the next hour.
Feb 1, 04:21 UTC
Feb 1, 04:21 UTC
Update -
We have identified an issue that is preventing some navigation components from loading while browsing GitHub.com, and are testing a remediation prior to deployment.
Feb 1, 03:55 UTC
Feb 1, 03:55 UTC
Update -
We are currently investigating reports of some components of the GitHub.com website not loading for some users.
Feb 1, 03:14 UTC
Feb 1, 03:14 UTC
Investigating -
We are currently investigating this issue.
Feb 1, 03:13 UTC
Feb 1, 03:13 UTC
Jan 31, 2024
Resolved -
This incident has been resolved.
Jan 31, 14:57 UTC
Jan 31, 14:57 UTC
Update -
We have resolved the issue and confirmed all regions are now operating as expected.
Jan 31, 14:56 UTC
Jan 31, 14:56 UTC
Update -
The fix for ip allow lists is currently rolling out; and we are awaiting confirmation from specific geographic regions.
Jan 31, 14:49 UTC
Jan 31, 14:49 UTC
Update -
We are rolling out a fix to resolve the issues with IP allow lists. This should be resolved shortly.
Jan 31, 14:33 UTC
Jan 31, 14:33 UTC
Update -
Some customers are experiencing issues with IP allow lists.
Jan 31, 14:14 UTC
Jan 31, 14:14 UTC
Investigating -
We are currently investigating this issue.
Jan 31, 14:14 UTC
Jan 31, 14:14 UTC
Jan 30, 2024
No incidents reported.
Jan 29, 2024
No incidents reported.
Jan 28, 2024
Resolved -
On January 28, 2024, between 01:00 UTC and 14:00 UTC the Avatars service was degraded and could not return all avatar images requested by users, instead it would return a default, fallback avatar image. This incident impacted, at peak time 6% of the requests for viewing Avatars. Requests that were impacted did not prevent the users from continuing to use any GitHub services. This was due to an issue with the Avatars service connecting to a database host.
We mitigated the incident by restarting the malfunctioning hosts that were not able to return the user avatar images.
We are working to improve alerting and monitoring of our services to reduce our time to detection and mitigation.
Jan 28, 14:42 UTC
We mitigated the incident by restarting the malfunctioning hosts that were not able to return the user avatar images.
We are working to improve alerting and monitoring of our services to reduce our time to detection and mitigation.
Jan 28, 14:42 UTC
Update -
We have mitigated all customer impact. We are no longer serving fallback avatar icons when loading web pages for some customers. We continue to monitor the results.
Jan 28, 14:27 UTC
Jan 28, 14:27 UTC
Update -
A fix has been implemented for customers seeing the default avatar (octocat) when loading web pages and we are monitoring the results.
Jan 28, 13:57 UTC
Jan 28, 13:57 UTC
Update -
Some requests for getting the Avatars are returning the fallback response instead of the asked avatar since they are having issues connecting to the Mysql host
Jan 28, 13:20 UTC
Jan 28, 13:20 UTC
Investigating -
We are currently investigating this issue.
Jan 28, 13:20 UTC
Jan 28, 13:20 UTC
Jan 27, 2024
No incidents reported.
Jan 26, 2024
No incidents reported.
Jan 25, 2024
No incidents reported.
Jan 24, 2024
No incidents reported.
Jan 23, 2024
Resolved -
On January 23, 2024 at 14:36 UTC, our internal metrics began showing an increase in exceptions originating from our live update service. Live updates to Issues, PRs, Actions, and Projects were failing, but refreshing the page successfully updated page content. We resolved the issue by rolling back a problematic dependency update and reenabled live updates at 18:53 UTC.
We are working to improve alerting and monitoring of our live update service to reduce our time to detection and mitigation.
Jan 23, 18:53 UTC
We are working to improve alerting and monitoring of our live update service to reduce our time to detection and mitigation.
Jan 23, 18:53 UTC
Update -
Live updates have been restored and the system is operating normally.
Jan 23, 18:53 UTC
Jan 23, 18:53 UTC
Update -
We have identified and are beginning to roll out a potential fix for issues with live updates to our Web UI that power automatic page updates such as the merge box on Pull Requests and updates to Projects.
Users will see actions spinning on the PR merge box for example. As a work around, please refresh the page to get the page updated while we work to fix the issue. We will provide further updates as we continue resolving the issue.
Jan 23, 18:14 UTC
Users will see actions spinning on the PR merge box for example. As a work around, please refresh the page to get the page updated while we work to fix the issue. We will provide further updates as we continue resolving the issue.
Jan 23, 18:14 UTC
Update -
We are continuing to investigate issues with live updates to our Web UI that power automatic page updates such as the merge box on Pull Requests and updates to Projects.
Users will see actions spinning on the PR merge box for example. As a work around, please refresh the page to get the page updated while we work to fix the issue. We will provide further updates as we continue resolving the issue.
Jan 23, 17:17 UTC
Users will see actions spinning on the PR merge box for example. As a work around, please refresh the page to get the page updated while we work to fix the issue. We will provide further updates as we continue resolving the issue.
Jan 23, 17:17 UTC
Update -
We are continuing to investigate intermittent issues with live updates to our Web UI that power automatic page updates such as the merge box on Pull Requests and updates to Projects. Users will see actions spinning on the PR merge box for example. As a work around, please refresh the page to get the page updated while we work to fix the issue. We will provide further updates as we continue resolving the issue.
Jan 23, 16:37 UTC
Jan 23, 16:37 UTC
Update -
We are investigating intermittent issues with live updates to our Web UI that power automatic page updates such as the merge box on Pull Requests. Users will intermittently see actions spinning on the PR merge box for example. As a work around, please refresh the page to get the page updated while we work to fix the issue. We will provide further updates as we continue resolving the issue.
Jan 23, 15:59 UTC
Jan 23, 15:59 UTC
Investigating -
We are currently investigating this issue.
Jan 23, 15:50 UTC
Jan 23, 15:50 UTC
Jan 22, 2024
No incidents reported.
Jan 21, 2024
Resolved -
On 2024-01-21 at 3:38 UTC, we experienced an incident that affected customers using Codespaces. Customers encountered issues creating and resuming Codespaces in multiple regions due to operational issues with compute and storage resources.
Around 25% of customers were impacted, primarily in East US and West Europe. We re-routed traffic for Codespace creations to less impacted regions, but existing Codespaces in these regions may have been unable to resume during the incident.
By 7:30 UTC, we had recovered connectivity to all regions except West Europe, which had an extended recovery time due to increased load in that particular region. The incident was resolved on 2024-01-21 at 9:34 UTC once Codespace creations and resumes were working normally in all regions.
Jan 21, 09:34 UTC
Around 25% of customers were impacted, primarily in East US and West Europe. We re-routed traffic for Codespace creations to less impacted regions, but existing Codespaces in these regions may have been unable to resume during the incident.
By 7:30 UTC, we had recovered connectivity to all regions except West Europe, which had an extended recovery time due to increased load in that particular region. The incident was resolved on 2024-01-21 at 9:34 UTC once Codespace creations and resumes were working normally in all regions.
Jan 21, 09:34 UTC
Update -
We continue to work on mitigating the issues with Codespace resumes in West Europe.
Jan 21, 09:32 UTC
Jan 21, 09:32 UTC
Update -
We continue to work on mitigating the issues with Codespace resumes in West Europe.
Jan 21, 08:58 UTC
Jan 21, 08:58 UTC
Update -
We continue to work on mitigating the issues with Codespace resumes in West Europe.
Jan 21, 08:27 UTC
Jan 21, 08:27 UTC
Update -
Codespace creation has fully recovered in all regions. We are still mitigating issues with Codespace resumes in West Europe.
Jan 21, 07:55 UTC
Jan 21, 07:55 UTC
Update -
We continue to see recovery in most regions. We are still working on mitigating the issue impacting customers in West Europe.
Jan 21, 07:24 UTC
Jan 21, 07:24 UTC
Update -
We are continuing to monitor recovery in the affected regions.
Jan 21, 06:50 UTC
Jan 21, 06:50 UTC
Update -
We are seeing signs of recovery in the affected regions.
Jan 21, 06:15 UTC
Jan 21, 06:15 UTC
Update -
Codespaces is experiencing degraded performance. We are continuing to investigate.
Jan 21, 06:15 UTC
Jan 21, 06:15 UTC
Update -
We continue to work on mitigating the underlying the issue impacting Codespaces customers.
Jan 21, 06:00 UTC
Jan 21, 06:00 UTC
Update -
We continue to work on mitigating the underlying the issue impacting Codespaces customers.
Jan 21, 05:24 UTC
Jan 21, 05:24 UTC
Update -
Around 15% of Codespaces customers are unable to create or resume their codespaces. We are continuing efforts to mitigate the issue.
Jan 21, 04:50 UTC
Jan 21, 04:50 UTC
Update -
Codespaces is experiencing degraded availability. We are continuing to investigate.
Jan 21, 04:21 UTC
Jan 21, 04:21 UTC
Update -
We have identified the issue impacting Codespaces customers in multiple regions and are working on mitigation.
Jan 21, 04:15 UTC
Jan 21, 04:15 UTC
Update -
We are experiencing elevated error rates in multiple regions and are currently investigating.
Jan 21, 03:38 UTC
Jan 21, 03:38 UTC
Investigating -
We are investigating reports of degraded performance for Codespaces
Jan 21, 03:38 UTC
Jan 21, 03:38 UTC
Resolved -
On 2024-01-21 from 02:05 UTC to 06:19 UTC, GitHub Hosted Runners experienced increased error rates from our main cloud service provider. The errors were initially limited to a single region and we were able to route around the issue by transparently failing over to other regions. However, errors gradually expanded across all regions we deploy to and led to our available compute capacity being exhausted.
During the incident, up to 35% of Actions jobs using Larger Runners and 2% of Actions jobs using GitHub Hosted Runners overall may have experienced intermittent delays in starting. Once the issue was resolved by our cloud service provider, our systems made a full recovery without intervention.
We’re working closely with our service provider to understand the cause of the outage and mitigations we can put in place. We’re also working to increase our resilience to outages of this nature by expanding the regions we deploy to beyond the existing set, especially for Larger Runners.
Jan 21, 06:19 UTC
During the incident, up to 35% of Actions jobs using Larger Runners and 2% of Actions jobs using GitHub Hosted Runners overall may have experienced intermittent delays in starting. Once the issue was resolved by our cloud service provider, our systems made a full recovery without intervention.
We’re working closely with our service provider to understand the cause of the outage and mitigations we can put in place. We’re also working to increase our resilience to outages of this nature by expanding the regions we deploy to beyond the existing set, especially for Larger Runners.
Jan 21, 06:19 UTC
Update -
We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.
Jan 21, 05:54 UTC
Jan 21, 05:54 UTC
Update -
We have mitigated the issues impacting Actions Larger Runners. We are still experiencing delays starting normal jobs, and are continuing to investigate.
Jan 21, 05:26 UTC
Jan 21, 05:26 UTC
Update -
The team has identified the cause of the issues with Actions Larger Runners and has begun mitigation.
Jan 21, 04:53 UTC
Jan 21, 04:53 UTC
Update -
The team continues to investigate issues with some Actions jobs being queued for a long time and a percentage of jobs failing. We will continue providing updates on the progress towards mitigation.
Jan 21, 04:16 UTC
Jan 21, 04:16 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Jan 21, 03:45 UTC
Jan 21, 03:45 UTC
Jan 20, 2024
No incidents reported.
Jan 19, 2024
No incidents reported.
Jan 18, 2024
No incidents reported.
