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
Aug 14, 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.
Aug 14, 06:23 UTC
Aug 14, 06:23 UTC
Update -
We are investigating reports of issues with service(s): Actions. We will continue to keep users updated on progress towards mitigation.
Aug 14, 05:42 UTC
Aug 14, 05:42 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Aug 14, 05:03 UTC
Aug 14, 05:03 UTC
Aug 13, 2025
No incidents reported.
Aug 12, 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.
Aug 12, 17:56 UTC
Aug 12, 17:56 UTC
Update -
Service availability has been mostly restored, but some users will continue to see increased request latency and stale search results. We are still working towards full recovery.
Aug 12, 17:07 UTC
Aug 12, 17:07 UTC
Update -
Service availability has been mostly restored, but increased load/query latency and stale search results persist. We continue to work towards full mitigation.
Aug 12, 16:33 UTC
Aug 12, 16:33 UTC
Update -
We are seeing partial recovery in service availability, but still see inconsistent experiences and stale search data across services. Investigation and mitigations are underway.
Aug 12, 15:48 UTC
Aug 12, 15:48 UTC
Update -
We are experiencing increased latency in our API layers and inconsistently degraded experiences when loading or querying issues, pull requests, labels, packages, releases, workflow runs, projects, and repositories, among others. Investigation is underway.
Aug 12, 15:20 UTC
Aug 12, 15:20 UTC
Update -
We are investigating reports of degraded performance in services backed by search. The team continues to investigate why requests are failing to reach our search clusters.
Aug 12, 14:53 UTC
Aug 12, 14:53 UTC
Update -
Packages is experiencing degraded performance. We are continuing to investigate.
Aug 12, 14:30 UTC
Aug 12, 14:30 UTC
Investigating -
We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests
Aug 12, 14:12 UTC
Aug 12, 14:12 UTC
Aug 11, 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.
Aug 11, 18:57 UTC
Aug 11, 18:57 UTC
Update -
Logged out users may see intermittent errors when loading github.com webpages. Investigation is ongoing.
Aug 11, 18:53 UTC
Aug 11, 18:53 UTC
Investigating -
We are currently investigating this issue.
Aug 11, 18:51 UTC
Aug 11, 18:51 UTC
Aug 10, 2025
No incidents reported.
Aug 9, 2025
No incidents reported.
Aug 8, 2025
No incidents reported.
Aug 7, 2025
No incidents reported.
Aug 6, 2025
No incidents reported.
Aug 5, 2025
Resolved -
At 15:33 UTC on August 5, 2025, we initiated a production database migration to drop a column from a table backing pull request functionality. While the column was no longer in direct use, our ORM continued to reference the dropped column in a subset of pull request queries. As a result, there were elevated error rates across pushes, webhooks, notifications, and pull requests with impact peaking at approximately 4% of all web and REST API traffic.
We mitigated the issue by deploying a change that instructed the ORM to ignore the removed column. Most affected services recovered by 16:13 UTC. However, that fix was applied only to our largest production environment. An update to some of our custom and canary environments did not pick up the fix and this triggered a secondary incident affecting ~0.1% of pull request traffic, which was fully resolved by 19:45 UTC.
While migrations have protections such as progressive roll-out first targeting validation environments and acknowledge gates, this incident identified an application monitoring gap that would have prevented continued rollout when impact was observed. We will add additional automation and safeguards to prevent future incidents without requiring human intervention. We are also already working on a way to streamline some types of changes across environments, which would have prevented the second incident from occurring.
Aug 5, 19:46 UTC
We mitigated the issue by deploying a change that instructed the ORM to ignore the removed column. Most affected services recovered by 16:13 UTC. However, that fix was applied only to our largest production environment. An update to some of our custom and canary environments did not pick up the fix and this triggered a secondary incident affecting ~0.1% of pull request traffic, which was fully resolved by 19:45 UTC.
While migrations have protections such as progressive roll-out first targeting validation environments and acknowledge gates, this incident identified an application monitoring gap that would have prevented continued rollout when impact was observed. We will add additional automation and safeguards to prevent future incidents without requiring human intervention. We are also already working on a way to streamline some types of changes across environments, which would have prevented the second incident from occurring.
Aug 5, 19:46 UTC
Update -
Pull Requests is operating normally.
Aug 5, 19:46 UTC
Aug 5, 19:46 UTC
Update -
We continue to investigate issues with PRs. Impact remains limited to less than 2% of users.
Aug 5, 19:20 UTC
Aug 5, 19:20 UTC
Update -
We continue to investigate issues with PRs impacting less than 2% of customers.
Aug 5, 18:49 UTC
Aug 5, 18:49 UTC
Update -
We continue to investigate issues with PRs impacting less than 2% of customers.
Aug 5, 18:23 UTC
Aug 5, 18:23 UTC
Update -
We're seeing issues related to PR are investigating. Less than 2% of users are impacted.
Aug 5, 18:07 UTC
Aug 5, 18:07 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests
Aug 5, 17:53 UTC
Aug 5, 17:53 UTC
Resolved -
At 15:33 UTC on August 5, 2025, we initiated a production database migration to drop a column from a table backing pull request functionality. While the column was no longer in direct use, our ORM continued to reference the dropped column in a subset of pull request queries. As a result, there were elevated error rates across pushes, webhooks, notifications, and pull requests with impact peaking at approximately 4% of all web and REST API traffic.
We mitigated the issue by deploying a change that instructed the ORM to ignore the removed column. Most affected services recovered by 16:13 UTC. However, that fix was applied only to our largest production environment. An update to some of our custom and canary environments did not pick up the fix and this triggered a secondary incident affecting ~0.1% of pull request traffic, which was fully resolved by 19:45 UTC.
While migrations have protections such as progressive roll-out first targeting validation environments and acknowledge gates, this incident identified an application monitoring gap that would have prevented continued rollout when impact was observed. We will add additional automation and safeguards to prevent future incidents without requiring human intervention. We are also already working on a way to streamline some types of changes across environments, which would have prevented the second incident from occurring.
Aug 5, 16:14 UTC
We mitigated the issue by deploying a change that instructed the ORM to ignore the removed column. Most affected services recovered by 16:13 UTC. However, that fix was applied only to our largest production environment. An update to some of our custom and canary environments did not pick up the fix and this triggered a secondary incident affecting ~0.1% of pull request traffic, which was fully resolved by 19:45 UTC.
While migrations have protections such as progressive roll-out first targeting validation environments and acknowledge gates, this incident identified an application monitoring gap that would have prevented continued rollout when impact was observed. We will add additional automation and safeguards to prevent future incidents without requiring human intervention. We are also already working on a way to streamline some types of changes across environments, which would have prevented the second incident from occurring.
Aug 5, 16:14 UTC
Update -
Actions is operating normally.
Aug 5, 16:14 UTC
Aug 5, 16:14 UTC
Update -
Pull Requests is operating normally.
Aug 5, 16:14 UTC
Aug 5, 16:14 UTC
Update -
Issues is operating normally.
Aug 5, 16:14 UTC
Aug 5, 16:14 UTC
Update -
Webhooks is operating normally.
Aug 5, 16:14 UTC
Aug 5, 16:14 UTC
Update -
Git Operations is operating normally.
Aug 5, 16:13 UTC
Aug 5, 16:13 UTC
Update -
We have fully mitigated this issue and all services are operating normally.
Aug 5, 16:13 UTC
Aug 5, 16:13 UTC
Update -
Webhooks is experiencing degraded performance. We are continuing to investigate.
Aug 5, 16:08 UTC
Aug 5, 16:08 UTC
Update -
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Aug 5, 16:06 UTC
Aug 5, 16:06 UTC
Update -
We have identified a change that was made in the Pull Request area for GitHub. Users may be unable to use certain pull request and issues features and may see some webhooks impacted. We have identified the issue, taken mitigation and are starting to see recovery but will continue to monitor and post updates as we have them.
Aug 5, 16:05 UTC
Aug 5, 16:05 UTC
Update -
Webhooks is experiencing degraded availability. We are continuing to investigate.
Aug 5, 15:56 UTC
Aug 5, 15:56 UTC
Update -
Git Operations is experiencing degraded performance. We are continuing to investigate.
Aug 5, 15:55 UTC
Aug 5, 15:55 UTC
Update -
Pull Requests is experiencing degraded availability. We are continuing to investigate.
Aug 5, 15:54 UTC
Aug 5, 15:54 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
Aug 5, 15:51 UTC
Aug 5, 15:51 UTC
Update -
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Aug 5, 15:51 UTC
Aug 5, 15:51 UTC
Investigating -
We are investigating reports of degraded performance for Issues and Webhooks
Aug 5, 15:42 UTC
Aug 5, 15:42 UTC
Aug 4, 2025
No incidents reported.
Aug 3, 2025
No incidents reported.
Aug 2, 2025
No incidents reported.
Aug 1, 2025
Resolved -
Between 06:04 UTC to 10:55 UTC on August 1, 2025, 100% of users attempting to sign up with an email and password experienced errors. Social signup was not affected. Once the problem became clear, the offending code was identified and a change was deployed to resolve the issue. We are adding additional monitoring to our sign-up process to improve our time to detection.
Aug 1, 10:55 UTC
Aug 1, 10:55 UTC
Update -
We are working on a mitigation to an issue preventing some users from signing up with email and password. Social signup methods remain available.
Aug 1, 10:26 UTC
Aug 1, 10:26 UTC
Update -
We have identified an issue preventing some new users from signing up. We are working to mitigate.
Aug 1, 09:39 UTC
Aug 1, 09:39 UTC
Investigating -
We are currently investigating this issue.
Aug 1, 09:20 UTC
Aug 1, 09:20 UTC
Jul 31, 2025
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe