GitHub Outage History
GitHub is up right nowPingoru has recorded 201 incidents for GitHub: 201 in the last 12 months and 63 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 27 | 135 of 720 (19%) |
| May 2026 | 22 | 34 of 744 (5%) |
| June 2026 | 24 | 54 of 720 (8%) |
| July 2026 | 27 | 43 of 744 (6%) |
| August 2026 | 27 | 75 of 744 (10%) |
| September 2026 | 14 | 46 of 720 (6%) |
| October 2026 | 25 | 54 of 744 (7%) |
| November 2026 | 0 | 0 of 13 (0%) |
Incidents, newest first
Critical June 17, 2026 Incident with Copilot Availability 53m Copilot
Started Jun 17, 2026, 03:50 AM UTC· resolved Jun 17, 2026, 04:44 AM UTC
- investigating Jun 17, 2026, 03:50 AM UTC
We are investigating reports of degraded availability for Copilot
- investigating Jun 17, 2026, 03:52 AM UTC
We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.
- investigating Jun 17, 2026, 04:26 AM UTC
We've applied a mitigation to unblock Copilot functionality. Users may start to see signs of recovery. Relaunching your client should accelerate signs of recovery. We will continue to monitor the situation.
- monitoring Jun 17, 2026, 04:44 AM UTC
Copilot is operating normally.
- resolved Jun 17, 2026, 04:44 AM UTC
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.
Major June 16, 2026 Disruption with some GitHub services 29m Copilot AI Model Providers
Started Jun 16, 2026, 05:45 PM UTC· resolved Jun 16, 2026, 06:15 PM UTC
- investigating Jun 16, 2026, 05:45 PM UTC
We are investigating reports of degraded availability for Copilot AI Model Providers
- investigating Jun 16, 2026, 05:47 PM UTC
We are experiencing degraded availability for the Opus 4.8 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
- monitoring Jun 16, 2026, 06:00 PM UTC
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 16, 2026, 06:14 PM UTC
The issues with our upstream model provider have been resolved, and Opus 4.8 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.
- resolved Jun 16, 2026, 06:15 PM UTC
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.
Minor June 15, 2026 Multiple services have elevated errors and endpoint failures when checking feature flags 38m
Started Jun 15, 2026, 06:32 PM UTC· resolved Jun 15, 2026, 07:10 PM UTC
- investigating Jun 15, 2026, 06:32 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- monitoring Jun 15, 2026, 07:02 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 15, 2026, 07:10 PM UTC
We identified an issue with feature flag checks that caused elevated errors and endpoint failures across multiple GitHub Copilot services. Customers may have experienced failed requests or degraded functionality. A fix has been deployed and error rates are steadily decreasing. All affected services are now mitigated and we are monitoring recovery.
- resolved Jun 15, 2026, 07:10 PM UTC
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.
Minor June 15, 2026 Increased latency with webhooks 2h Webhooks
Started Jun 15, 2026, 03:37 PM UTC· resolved Jun 15, 2026, 05:37 PM UTC
- investigating Jun 15, 2026, 03:37 PM UTC
We are investigating reports of degraded performance for Webhooks
- investigating Jun 15, 2026, 04:39 PM UTC
Webhooks delivery latency has returned to normal levels. The backlog that built up during the incident has been cleared at approximately 4:29 UTC. We consider this incident resolved.
- monitoring Jun 15, 2026, 04:39 PM UTC
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
- resolved Jun 15, 2026, 05:37 PM UTC
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.
Minor June 11, 2026 Incident with Webhooks 2h 37m Webhooks
Started Jun 11, 2026, 07:42 PM UTC· resolved Jun 11, 2026, 10:19 PM UTC
- investigating Jun 11, 2026, 07:42 PM UTC
We are investigating reports of degraded performance for Webhooks
- investigating Jun 11, 2026, 07:42 PM UTC
We are currently experiencing delays in Web Hook delivery and are actively investigating the root cause.
- investigating Jun 11, 2026, 07:58 PM UTC
We have applied a mitigation and are monitoring for recovery.
- monitoring Jun 11, 2026, 08:00 PM UTC
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
- resolved Jun 11, 2026, 10:19 PM UTC
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.
Critical June 10, 2026 Authentication issues related to API requests 1h 18m API Requests, Issues
Started Jun 10, 2026, 03:20 PM UTC· resolved Jun 10, 2026, 04:39 PM UTC
- investigating Jun 10, 2026, 03:20 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 10, 2026, 03:23 PM UTC
API Requests is experiencing degraded availability. We are continuing to investigate.
- investigating Jun 10, 2026, 03:27 PM UTC
Issues is experiencing degraded performance. We are continuing to investigate.
- investigating Jun 10, 2026, 03:27 PM UTC
We are investigating issues related to sporadic authentication failures impacting approximately 15% of API traffic. We will continue to investigate and provide updates.
- investigating Jun 10, 2026, 03:46 PM UTC
We continue to investigate issues related to sporadic authentication failures, impacting approximately 15% of API traffic. Further updates will be provided as we work to mitigate.
- investigating Jun 10, 2026, 03:46 PM UTC
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
- investigating Jun 10, 2026, 04:21 PM UTC
We continue to investigate issues related to sporadic authentication failures, impacting approximately 15% of API traffic. Erroneous 401 responses are causing app integrations to trigger authentication flows. We have identified a problematic component in our infrastructure and are working to mitigate.
- investigating Jun 10, 2026, 04:36 PM UTC
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 10, 2026, 04:37 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- resolved Jun 10, 2026, 04:39 PM UTC
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.
Notice June 8, 2026 Degraded availability for GitHub.com, GraphQL API, and Webhooks UI/API –
Started Jun 08, 2026, 03:00 PM UTC· resolved Jun 08, 2026, 03:00 PM UTC
- resolved Jun 09, 2026, 03:48 PM UTC
On June 8, 2026, between 14:49 and 14:54 UTC, a subset of requests to GitHub.com, the REST API, GraphQL API, and Webhooks UI/API experienced elevated error rates due to a transient infrastructure capacity issue that self-resolved within approximately 5 minutes. Users experienced HTTP 500 errors and timeouts when accessing GitHub.com, the REST API, GraphQL API, and Webhooks UI/API for approximately 5 minutes, with the REST API taking up to 12 minutes to fully recover.
Minor June 8, 2026 Disruption with Claude Opus 4.7 57m Copilot AI Model Providers
Started Jun 08, 2026, 09:05 AM UTC· resolved Jun 08, 2026, 10:03 AM UTC
- investigating Jun 08, 2026, 09:05 AM UTC
We are investigating reports of degraded performance for Copilot AI Model Providers
- investigating Jun 08, 2026, 09:08 AM UTC
We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
- investigating Jun 08, 2026, 09:49 AM UTC
We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue, and starting to see recovery.
- resolved Jun 08, 2026, 10:03 AM UTC
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.
Critical June 8, 2026 Pull Requests and Issues unavailable for signed-out users 1h 24m Issues, Pull Requests, Actions
Started Jun 08, 2026, 07:11 AM UTC· resolved Jun 08, 2026, 08:36 AM UTC
- investigating Jun 08, 2026, 07:11 AM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 08, 2026, 07:14 AM UTC
Issues is experiencing degraded availability. We are continuing to investigate.
- investigating Jun 08, 2026, 07:31 AM UTC
Issues is experiencing degraded performance. We are continuing to investigate.
- investigating Jun 08, 2026, 07:32 AM UTC
Pull Requests is experiencing degraded performance. We are continuing to investigate.
- investigating Jun 08, 2026, 08:13 AM UTC
Following investigation, we are seeing that impact is limited to unauthenticated users when accessing Pull Requests or Issues. Our team continues to work towards mitigation with more updates to follow as we have them.
- investigating Jun 08, 2026, 08:27 AM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- monitoring Jun 08, 2026, 08:35 AM UTC
The degradation affecting Actions, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
- resolved Jun 08, 2026, 08:36 AM UTC
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.
Minor June 6, 2026 Disruption with some GitHub services in the EU region 14m Packages
Started Jun 06, 2026, 04:53 PM UTC· resolved Jun 06, 2026, 05:07 PM UTC
- investigating Jun 06, 2026, 04:53 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 06, 2026, 04:56 PM UTC
Packages is experiencing degraded performance. We are continuing to investigate.
- resolved Jun 06, 2026, 05:07 PM UTC
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.
Minor June 6, 2026 EU Network Maintenance 3h 17m
Started Jun 06, 2026, 03:31 PM UTC· resolved Jun 06, 2026, 06:49 PM UTC
- investigating Jun 06, 2026, 03:31 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 06, 2026, 03:31 PM UTC
We are conducting routine maintenance on our network infrastructure in the EU. This will not impact production traffic, but may result in slightly increased latency for the remainder of our work. We expect this to last until 15:00 UTC.
- monitoring Jun 06, 2026, 03:36 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 06, 2026, 06:48 PM UTC
All work has been completed and we are hands off.
- resolved Jun 06, 2026, 06:49 PM UTC
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.
Minor June 5, 2026 Auth issue resulting in API impacts, including some Slack and Teams channel subscriptions 5h
Started Jun 05, 2026, 05:20 PM UTC· resolved Jun 05, 2026, 10:21 PM UTC
- investigating Jun 05, 2026, 05:20 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 05, 2026, 05:25 PM UTC
Customers may see unexpected repo unsubscription events in their Slack or Teams channels.
- investigating Jun 05, 2026, 06:04 PM UTC
During 14:49 UTC to 16:45 UTC, customers may have experienced authorization failures for legitimate requests. This was caused by a recently enabled feature flag, which has now been turned off as a mitigation. Customers should now see normal authorization behavior. This is also the cause of the chat integration issue, and we are exploring options to restore it. In the meantime, customers can manually re-subscribe their repo.
- monitoring Jun 05, 2026, 06:05 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 05, 2026, 06:43 PM UTC
We are still exploring options to restore the deleted subscriptions, and we will provide another update soon. In the meantime, customers can manually re-subscribe their Slack and Teams channels to repositories.
- monitoring Jun 05, 2026, 08:34 PM UTC
Additional detail on the scope of impact during the 14:49 UTC to 16:45 UTC window: a small but elevated percentage of authenticated requests to GitHub.com received incorrect authorization failures. We saw a 1 to 2% increase in 4xx responses for a small number of endpoints (/repos/{owner}/{repo}/pulls/{pull_number}, /repos/{owner}/{repo}, /repos/{owner}/{repo}/contents/{path}). The vast majority of requests completed normally; customers who saw errors during the window can retry now and should see them succeed.
- monitoring Jun 05, 2026, 10:21 PM UTC
Affected Slack and Teams subscriptions have been restored. Please contact support if you encounter any additional issues.
- resolved Jun 05, 2026, 10:21 PM UTC
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.
Critical June 4, 2026 Live updates degraded 11m
Started Jun 04, 2026, 08:20 PM UTC· resolved Jun 04, 2026, 08:32 PM UTC
- investigating Jun 04, 2026, 08:20 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- resolved Jun 04, 2026, 08:32 PM UTC
Everything is operating normally.
Critical June 4, 2026 Copilot Code Review Failing 1h 56m
Started Jun 04, 2026, 06:02 PM UTC· resolved Jun 04, 2026, 07:59 PM UTC
- investigating Jun 04, 2026, 06:02 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 04, 2026, 06:03 PM UTC
We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review. A mitigation is in progress.
- investigating Jun 04, 2026, 06:22 PM UTC
We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review. A mitigation is in progress, we expect mitigation in approximately 30m. GitHub Enterprise Cloud with Data Residency is not impacted.
- investigating Jun 04, 2026, 06:52 PM UTC
The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.
- investigating Jun 04, 2026, 07:07 PM UTC
The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.
- monitoring Jun 04, 2026, 07:07 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 04, 2026, 07:41 PM UTC
The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. We are continuing to monitor for full resolution. Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.
- monitoring Jun 04, 2026, 07:59 PM UTC
This issue is now fully resolved and Copilot Code Review is working as expected.
- resolved Jun 04, 2026, 07:59 PM UTC
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.
Minor June 3, 2026 Disruption with some GitHub services 8h 29m
Started Jun 03, 2026, 07:42 PM UTC· resolved Jun 04, 2026, 04:11 AM UTC
- investigating Jun 03, 2026, 07:42 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 03, 2026, 07:43 PM UTC
We're seeing delays in Dependabot scheduled version update runs. Our team is actively working on a fix and will share updates as the situation develops.
- investigating Jun 03, 2026, 08:18 PM UTC
Customers may see delays of up to two days in Dependabot version updates. Dependabot Security updates are not delayed. The team is investigating mitigations for the backlog. Next update in 1 hour.
- investigating Jun 03, 2026, 09:10 PM UTC
We are preparing a mitigation for the delayed Dependabot scheduled version updates. Next update in 2 hours.
- investigating Jun 03, 2026, 11:38 PM UTC
We have applied mitigations and are continuing to see improvements in the Dependabot scheduled version updates. Next update in 12 hours.
- monitoring Jun 04, 2026, 02:35 AM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 04, 2026, 02:37 AM UTC
Job lag has recovered from a peak of 1.71 days to 9h 9m at 19:29 UTC and continues to decrease. Backlog is draining at a healthy rate with no signs of reversal. New jobs are processing on schedule. Remaining lag will continue to drain over the next few hours as queued work completes; this is expected post-incident catch-up, not active impact. We will continue monitoring and re-engage if lag trend reverses.
- monitoring Jun 04, 2026, 04:11 AM UTC
Job lag has recovered to within normal operating thresholds. We are declaring this incident closed and will follow up with a summary soon.
- resolved Jun 04, 2026, 04:11 AM UTC
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.
Minor June 3, 2026 Disruption with some GitHub services 3h 33m
Started Jun 03, 2026, 03:13 AM UTC· resolved Jun 03, 2026, 06:46 AM UTC
- investigating Jun 03, 2026, 03:13 AM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 03, 2026, 03:45 AM UTC
We are investigating reports of issues with service(s): Spark. We will continue to keep users updated on progress towards mitigation.
- investigating Jun 03, 2026, 06:02 AM UTC
We are investigating reports of issues with service(s): Spark. We will continue to keep users updated on progress towards mitigation.
- monitoring Jun 03, 2026, 06:45 AM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- resolved Jun 03, 2026, 06:46 AM UTC
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.
Minor June 1, 2026 Delays with Code Scanning and Billing 9h
Started Jun 01, 2026, 03:17 PM UTC· resolved Jun 02, 2026, 12:17 AM UTC
- investigating Jun 01, 2026, 03:17 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 01, 2026, 03:17 PM UTC
We are investigating reports of delayed code scanning runs and delayed billing updates. We will continue to keep users updated on progress towards mitigation.
- investigating Jun 01, 2026, 03:43 PM UTC
We are investigating reports of delayed code scanning runs, billing updates, email and mobile push notifications. We are investigating delays in our job processing architecture. We will continue to keep users updated on progress towards mitigation.
- investigating Jun 01, 2026, 04:42 PM UTC
We are investigating reports of delayed billing updates, on GitHub.com. We are continuing to investigate delays in our job processing architecture. We are attempting to mitigate at the infrastructure level. Code scanning runs and notifications have recovered. We will continue to keep users updated on progress towards mitigation. GitHub Enterprise Cloud with Data Residency is not impacted.
- investigating Jun 01, 2026, 05:28 PM UTC
We are continuing to investigate delayed billing updates, on GitHub.com. We have applied multiple mitigations and are seeing some signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub Enterprise Cloud with Data Residency is not impacted.
- investigating Jun 01, 2026, 06:48 PM UTC
We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations and are seeing some more signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub Enterprise Cloud with Data Residency is not impacted.
- investigating Jun 01, 2026, 07:27 PM UTC
We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations are continuing to see signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub Enterprise Cloud with Data Residency is not impacted. Next update in 2 hours.
- investigating Jun 01, 2026, 09:59 PM UTC
We have identified the root cause and applied mitigations to address delays in billing updates and are continuing to see improvement in the processing rate. We will continue to monitor the progress and will provide an update in few hours. GitHub Enterprise Cloud with Data Residency is not impacted.
- resolved Jun 02, 2026, 12:17 AM UTC
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.
Notice May 28, 2026 Elevated error rates across multiple services –
Started May 28, 2026, 07:07 PM UTC· resolved May 28, 2026, 07:07 PM UTC
- resolved May 28, 2026, 11:10 PM UTC
On May 28, 2026, between 19:07 UTC and 19:16 UTC, multiple GitHub services experienced elevated error rates. This was due to a change that was partially deployed to an authentication service, causing errors for dependent services including the web experience, REST API, Git operations, and GitHub Actions. At peak impact, 10% of GitHub Actions runs failed to queue or encountered errors while downloading actions. We mitigated the incident by rolling back the change. We are expanding test coverage and improving our deployment validation process to prevent recurrence of this issue in the future.
Critical May 28, 2026 Disruption with OpenAI Models 1h 40m Copilot
Started May 28, 2026, 07:01 PM UTC· resolved May 28, 2026, 08:41 PM UTC
- investigating May 28, 2026, 07:01 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating May 28, 2026, 07:20 PM UTC
Copilot is experiencing degraded performance. We are continuing to investigate.
- investigating May 28, 2026, 07:40 PM UTC
We are investigating errors with Copilot requests using OpenAI models
- investigating May 28, 2026, 08:06 PM UTC
Open AI models are currently unavailable. We are shifting requests to other models to reduce impact.
- resolved May 28, 2026, 08:41 PM UTC
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.
Minor May 28, 2026 Webhook APIs and UI Degraded 18m Webhooks
Started May 28, 2026, 01:13 AM UTC· resolved May 28, 2026, 01:32 AM UTC
- investigating May 28, 2026, 01:13 AM UTC
We are investigating reports of degraded performance for Webhooks
- monitoring May 28, 2026, 01:27 AM UTC
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
- resolved May 28, 2026, 01:32 AM UTC
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.
Minor May 27, 2026 Incident with Pull Requests, Issues, Git Operations and API Requests 1h 6m Git Operations, API Requests, Issues, Pull Requests
Started May 27, 2026, 12:10 PM UTC· resolved May 27, 2026, 01:16 PM UTC
- investigating May 27, 2026, 12:10 PM UTC
We are investigating reports of degraded performance for API Requests, Git Operations, Issues and Pull Requests
- investigating May 27, 2026, 12:54 PM UTC
We're continuing to investigate degraded performance of Git operations, Issues and Pull requests.
- resolved May 27, 2026, 01:16 PM UTC
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.
Minor May 26, 2026 Disruption with some GitHub services 51m Copilot
Started May 26, 2026, 03:44 PM UTC· resolved May 26, 2026, 04:35 PM UTC
- investigating May 26, 2026, 03:44 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating May 26, 2026, 03:48 PM UTC
Copilot is experiencing degraded performance. We are continuing to investigate.
- monitoring May 26, 2026, 04:24 PM UTC
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
- resolved May 26, 2026, 04:35 PM UTC
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.
Critical May 26, 2026 Incident with Actions and Pages 2h 21m Actions, Pages
Started May 26, 2026, 10:57 AM UTC· resolved May 26, 2026, 01:18 PM UTC
- investigating May 26, 2026, 10:57 AM UTC
We are investigating reports of degraded performance for Actions and Pages
- investigating May 26, 2026, 11:19 AM UTC
Actions is experiencing degraded availability. We are continuing to investigate.
- investigating May 26, 2026, 11:53 AM UTC
We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.
- investigating May 26, 2026, 12:17 PM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating May 26, 2026, 12:37 PM UTC
We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation
- monitoring May 26, 2026, 01:00 PM UTC
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
- monitoring May 26, 2026, 01:01 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- resolved May 26, 2026, 01:18 PM UTC
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.
Major May 25, 2026 Elevated rate of Git push errors –
Started May 25, 2026, 09:02 AM UTC· resolved May 25, 2026, 09:02 AM UTC
- resolved Jun 08, 2026, 01:56 PM UTC
On May 25, 2026, between 09:02 UTC and 09:11 UTC, Git push operations over HTTPS and SSH experienced elevated failures. During this window, an average of 31% and a peak of 43% of push requests failed. The incident was caused by a recently enabled code path that issued an unexpectedly expensive database query against a primary database. The resulting load exhausted the database's connection pool, which caused the push failures above. The acute impact resolved automatically as in-flight work completed. We mitigated the incident by disabling the feature flag controlling the new code path. We are working to route the affected read to a replica to reduce the likelihood of issues like this in the future.
Minor May 23, 2026 Intermittent errors with app installation token authentication –
Started May 23, 2026, 07:32 PM UTC· resolved May 23, 2026, 07:32 PM UTC
- investigating May 23, 2026, 04:00 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating May 23, 2026, 04:01 PM UTC
We are seeing an increased rate of authentication failures for app installation tokens, affecting approximately 1% of tokens. We are continuing to investigate.
- investigating May 23, 2026, 04:35 PM UTC
We are continuing to investigate an elevated error rate of authentication failures for app installation tokens. Next update in one hour.
- investigating May 23, 2026, 05:41 PM UTC
We are seeing signs of mitigation and are continuing to monitor for complete mitigation. Next update in one hour.
- investigating May 23, 2026, 06:42 PM UTC
We see significant signs of mitigation and are monitoring for full mitigation.
- investigating May 23, 2026, 07:06 PM UTC
We have identified and are applying additional mitigation and will continue to monitor for complete mitigation.
- investigating May 23, 2026, 07:32 PM UTC
This is fully mitigated, we will continue to monitor to ensure it does not reoccur.
- resolved May 23, 2026, 07:32 PM UTC
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.