GitHub Outage History

GitHub is up right now

Pingoru has recorded 201 incidents for GitHub: 201 in the last 12 months and 63 in the last 90 days.

Source: githubstatus.com · Aggregated across GitHub products

201incidents recorded
201last 12 months
63last 90 days
3 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking GitHub in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202627135 of 720 (19%)
May 20262234 of 744 (5%)
June 20262454 of 720 (8%)
July 20262743 of 744 (6%)
August 20262775 of 744 (10%)
September 20261446 of 720 (6%)
October 20262554 of 744 (7%)
November 202600 of 12 (0%)

Incidents, newest first

Major July 24, 2026 Disruption with some GitHub services 1h 19m API Requests, Issues, Pull Requests, Actions and 2 more

Started Jul 24, 2026, 04:17 PM UTC· resolved Jul 24, 2026, 05:36 PM UTC

  1. investigating Jul 24, 2026, 04:17 PM UTC

    We are investigating reports of degraded performance for API Requests and Issues

  2. investigating Jul 24, 2026, 04:19 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  3. investigating Jul 24, 2026, 04:20 PM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  4. investigating Jul 24, 2026, 04:22 PM UTC

    We are investigating timeouts to some GitHub services

  5. investigating Jul 24, 2026, 04:26 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  6. investigating Jul 24, 2026, 04:27 PM UTC

    Pages is experiencing degraded performance. We are continuing to investigate.

  7. investigating Jul 24, 2026, 04:28 PM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  8. investigating Jul 24, 2026, 04:40 PM UTC

    We have applied a mitigation and are monitoring for recovery

  9. investigating Jul 24, 2026, 04:41 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  10. investigating Jul 24, 2026, 05:16 PM UTC

    The degradation affecting API Requests, Actions, Copilot, Issues, Pages and Pull Requests has been mitigated. We are monitoring to ensure stability.

  11. investigating Jul 24, 2026, 05:24 PM UTC

    We are seeing recovery across all services

  12. resolved Jul 24, 2026, 05:36 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.

Read the full incident report →

Notice July 24, 2026 Incident With Blocked GitHub.com Traffic –

Started Jul 24, 2026, 11:00 AM UTC· resolved Jul 24, 2026, 11:00 AM UTC

  1. resolved Jul 24, 2026, 03:56 PM UTC

    Between July 23, 2026 at 18:45 UTC and July 24, 2026 at 11:19 UTC, an abuse mitigation update caused some legitimate customers whose traffic was routed through our Central Europe and South America edge locations to be incorrectly blocked from GitHub.com. We estimate that approximately 0.25% of GitHub.com requests were affected during this period. This was caused by an abuse mitigation configuration that incorrectly classified legitimate traffic. We mitigated the incident by reverting the update. We are adding validation and safeguards to prevent similar incorrect blocking in the future.

Read the full incident report →

Major July 23, 2026 Latency issues across a number of services 1h 45m Webhooks, Issues, Pull Requests, Actions

Started Jul 23, 2026, 07:53 AM UTC· resolved Jul 23, 2026, 09:39 AM UTC

  1. investigating Jul 23, 2026, 07:53 AM UTC

    We are investigating reports of degraded availability for Actions, Issues and Webhooks

  2. investigating Jul 23, 2026, 08:25 AM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  3. investigating Jul 23, 2026, 08:34 AM UTC

    We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.

  4. investigating Jul 23, 2026, 09:18 AM UTC

    The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

  5. investigating Jul 23, 2026, 09:19 AM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  6. investigating Jul 23, 2026, 09:22 AM UTC

    We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.

  7. investigating Jul 23, 2026, 09:27 AM UTC

    The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

  8. investigating Jul 23, 2026, 09:35 AM UTC

    Webhooks is operating normally.

  9. monitoring Jul 23, 2026, 09:39 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  10. resolved Jul 23, 2026, 09:39 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.

Read the full incident report →

Minor July 22, 2026 Disruption with actions hosted runners 1h 25m Actions

Started Jul 22, 2026, 08:43 PM UTC· resolved Jul 22, 2026, 10:09 PM UTC

  1. investigating Jul 22, 2026, 08:43 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Jul 22, 2026, 08:47 PM UTC

    Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.

  3. investigating Jul 22, 2026, 10:01 PM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  4. monitoring Jul 22, 2026, 10:01 PM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  5. resolved Jul 22, 2026, 10:09 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.

Read the full incident report →

Critical July 21, 2026 Some SSH connections using deploy keys are failing 1h 25m

Started Jul 21, 2026, 10:31 AM UTC· resolved Jul 21, 2026, 11:57 AM UTC

  1. investigating Jul 21, 2026, 10:31 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jul 21, 2026, 11:04 AM UTC

    We are investigating reports of intermittent SSH authentication failures affecting connections that use deploy keys. Customers may experience failed SSH connections when interacting with repositories via deploy keys. Our engineering team is actively investigating the root cause and working toward resolution.

  3. investigating Jul 21, 2026, 11:46 AM UTC

    We have identified a recent code change as a potential cause of the SSH authentication failures affecting deploy key connections. Our engineering team is rolling back this change. Customers using deploy keys for SSH access to repositories may continue to experience intermittent connection failures until the fix is deployed.

  4. resolved Jul 21, 2026, 11:57 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.

Read the full incident report →

Minor July 20, 2026 Disruption with GPT 5.3 Codex 2h 33m Copilot AI Model Providers

Started Jul 20, 2026, 04:03 PM UTC· resolved Jul 20, 2026, 06:37 PM UTC

  1. investigating Jul 20, 2026, 04:03 PM UTC

    We are investigating reports of degraded performance for Copilot AI Model Providers

  2. investigating Jul 20, 2026, 04:04 PM UTC

    We are investigating GPT Codex 5.3 performance.

  3. investigating Jul 20, 2026, 04:39 PM UTC

    We identified that an upstream provider is returning errors for GPT 5.3 Codex requests, causing some users to experience failed or interrupted responses. Traffic is being automatically rerouted to mitigate impact. We are working with the upstream provider to resolve the underlying issue. We recommend using a different model at this time while we resolve the problem.

  4. investigating Jul 20, 2026, 05:21 PM UTC

    The upstream provider continues to return intermittent errors for GPT 5.3 Codex requests. Some users may experience failed or interrupted responses when using this model. Traffic continues to be automatically rerouted to reduce impact, and we are actively working with the upstream provider on a resolution. In the meantime, selecting an alternative model will avoid disruption.

  5. investigating Jul 20, 2026, 06:25 PM UTC

    We are seeing signs of sustained recovery from the upstream provider for GPT 5.3 Codex requests. Requests are succeeding as expected. We are awaiting confirmation from the provider that the issue is fully mitigated before resolving this incident.

  6. resolved Jul 20, 2026, 06: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.

Read the full incident report →

Major July 20, 2026 Disruption with some GitHub services 1h 20m

Started Jul 20, 2026, 12:25 AM UTC· resolved Jul 20, 2026, 01:46 AM UTC

  1. investigating Jul 20, 2026, 12:25 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. monitoring Jul 20, 2026, 12:25 AM UTC

    Some Git LFS operations, and loading files through the API are failing. We are investigating.

  3. monitoring Jul 20, 2026, 12:26 AM UTC

    Some Git LFS operations, and loading files through the API are failing. We are investigating.

  4. investigating Jul 20, 2026, 01:15 AM UTC

    The Git LFS API issues have been identified as being related to a separate incident where Actions is experiencing degraded availability. We’re consolidating our investigation efforts under that incident.

  5. investigating Jul 20, 2026, 01:45 AM UTC

    Git LFS API success rates have returned to normal. We will continue to monitor the service closely.

  6. resolved Jul 20, 2026, 01: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.

Read the full incident report →

Critical July 19, 2026 Incident with GitHub Actions 5h 9m API Requests, Issues, Actions, Pages

Started Jul 19, 2026, 11:34 PM UTC· resolved Jul 20, 2026, 04:44 AM UTC

  1. investigating Jul 19, 2026, 11:34 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Jul 19, 2026, 11:37 PM UTC

    We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.

  3. investigating Jul 19, 2026, 11:57 PM UTC

    We have identified the cause of failures in GitHub Actions and are working to restore service.

  4. investigating Jul 20, 2026, 12:07 AM UTC

    API Requests is experiencing degraded availability. We are continuing to investigate.

  5. investigating Jul 20, 2026, 12:20 AM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  6. investigating Jul 20, 2026, 12:48 AM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  7. investigating Jul 20, 2026, 12:49 AM UTC

    Actions and Pages are experiencing degraded performance. We are continuing to investigate.

  8. investigating Jul 20, 2026, 12:52 AM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  9. investigating Jul 20, 2026, 01:11 AM UTC

    We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services. A separate incident was opened before we understood they were related. We will continue to post updates on this incident.

  10. investigating Jul 20, 2026, 01:37 AM UTC

    Pages is operating normally.

  11. investigating Jul 20, 2026, 02:20 AM UTC

    Issues is operating normally.

  12. investigating Jul 20, 2026, 02:23 AM UTC

    API Requests is experiencing degraded performance. We are continuing to investigate.

  13. investigating Jul 20, 2026, 02:43 AM UTC

    Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.

  14. investigating Jul 20, 2026, 03:03 AM UTC

    API Requests is operating normally.

  15. investigating Jul 20, 2026, 03:27 AM UTC

    We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.

  16. monitoring Jul 20, 2026, 03:34 AM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  17. monitoring Jul 20, 2026, 04:43 AM UTC

    Actions has fully recovered, and we will continue to monitor the platform to ensure stability.

  18. resolved Jul 20, 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.

Read the full incident report →

Major July 16, 2026 Degraded REST API Availability 1h 22m API Requests

Started Jul 16, 2026, 10:51 PM UTC· resolved Jul 17, 2026, 12:14 AM UTC

  1. investigating Jul 16, 2026, 10:51 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jul 16, 2026, 10:58 PM UTC

    We are aware of degraded REST API availability and are investigating

  3. investigating Jul 16, 2026, 10:58 PM UTC

    API Requests is experiencing degraded performance. We are continuing to investigate.

  4. investigating Jul 16, 2026, 11:29 PM UTC

    We are continuing to investigate an issue causing approximately 35% of REST API requests to fail. Based on our current understanding, requests are not consistently reaching the application layer, resulting in failed requests returning HTML responses instead of the expected API response format. We are actively investigating the issue and will provide another update as soon as more information is available.

  5. monitoring Jul 17, 2026, 12:00 AM UTC

    The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

  6. monitoring Jul 17, 2026, 12:14 AM UTC

    As of 23:46 UTC, the REST API service is reachable and responding to requests normally.

  7. resolved Jul 17, 2026, 12:14 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.

Read the full incident report →

Minor July 16, 2026 Claude Fable 5 experiencing degraded performance 59m Copilot AI Model Providers

Started Jul 16, 2026, 09:05 PM UTC· resolved Jul 16, 2026, 10:04 PM UTC

  1. investigating Jul 16, 2026, 09:05 PM UTC

    We are investigating reports of degraded performance for Copilot AI Model Providers

  2. investigating Jul 16, 2026, 09:06 PM UTC

    We are experiencing degraded availability for the Claude Fable 5 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.

  3. resolved Jul 16, 2026, 10:04 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.

Read the full incident report →

Critical July 16, 2026 Disruption with some GitHub services 3h 7m

Started Jul 16, 2026, 09:13 AM UTC· resolved Jul 16, 2026, 12:20 PM UTC

  1. investigating Jul 16, 2026, 09:13 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. monitoring Jul 16, 2026, 09:30 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  3. monitoring Jul 16, 2026, 10:17 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  4. resolved Jul 16, 2026, 12:20 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.

Read the full incident report →

Minor July 14, 2026 Incident with Webhooks 23m Webhooks

Started Jul 14, 2026, 05:38 PM UTC· resolved Jul 14, 2026, 06:01 PM UTC

  1. investigating Jul 14, 2026, 05:38 PM UTC

    We are investigating reports of degraded performance for Webhooks

  2. investigating Jul 14, 2026, 05:55 PM UTC

    Between 15:17 and 15:27 UTC, an ongoing deployment had an unintended side effect where webhook delivery states were not persisted in all cases, even when deliveries were accepted and processed. Customers may notice missing webhook deliveries in the UI, and these deliveries will not be retryable. Impact resolved automatically once the deployment completed.

  3. monitoring Jul 14, 2026, 05:55 PM UTC

    The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.

  4. resolved Jul 14, 2026, 06:01 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.

Read the full incident report →

Minor July 14, 2026 Disruption with some GitHub services 1h 35m Codespaces

Started Jul 14, 2026, 08:21 AM UTC· resolved Jul 14, 2026, 09:56 AM UTC

  1. investigating Jul 14, 2026, 08:21 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jul 14, 2026, 08:22 AM UTC

    Codespaces is experiencing degraded performance. We are continuing to investigate.

  3. monitoring Jul 14, 2026, 09:51 AM UTC

    The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.

  4. resolved Jul 14, 2026, 09:56 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.

Read the full incident report →

Major July 13, 2026 Actions runs are experiencing failures to start 21m Actions, Pages

Started Jul 13, 2026, 01:32 PM UTC· resolved Jul 13, 2026, 01:53 PM UTC

  1. investigating Jul 13, 2026, 01:32 PM UTC

    We are investigating reports of degraded availability for Actions

  2. investigating Jul 13, 2026, 01:32 PM UTC

    Pages is experiencing degraded performance. We are continuing to investigate.

  3. monitoring Jul 13, 2026, 01:39 PM UTC

    The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

  4. resolved Jul 13, 2026, 01:53 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.

Read the full incident report →

Critical July 9, 2026 Delays starting Actions runs 9h 17m Actions, Pages

Started Jul 09, 2026, 04:34 AM UTC· resolved Jul 09, 2026, 01:52 PM UTC

  1. investigating Jul 09, 2026, 04:34 AM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Jul 09, 2026, 04:51 AM UTC

    Approximately 5% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.

  3. investigating Jul 09, 2026, 06:01 AM UTC

    We are continuing to work on a mitigation.

  4. investigating Jul 09, 2026, 10:07 AM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  5. investigating Jul 09, 2026, 10:15 AM UTC

    Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.

  6. investigating Jul 09, 2026, 12:01 PM UTC

    Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start. This has caused some customers to exceed their hosted compute concurrency and experience increased impact. We are continuing to working on infrastructure mitigations. Next update in one hour.

  7. investigating Jul 09, 2026, 12:36 PM UTC

    Pages is experiencing degraded performance. We are continuing to investigate.

  8. investigating Jul 09, 2026, 12:46 PM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  9. investigating Jul 09, 2026, 12:54 PM UTC

    We're seeing Actions and Pages recovery. For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing. GitHub pages builds were also failing during that period, but Pages are still accessible. We are continuing to monitor for full recovery.

  10. investigating Jul 09, 2026, 01:16 PM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  11. investigating Jul 09, 2026, 01:17 PM UTC

    We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog. Customers may see a small rate of API and job failures as the system is recovering. Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery. Pages were accessible throughout the incident.

  12. monitoring Jul 09, 2026, 01:39 PM UTC

    The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

  13. monitoring Jul 09, 2026, 01:41 PM UTC

    Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated. We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure.

  14. resolved Jul 09, 2026, 01:52 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.

Read the full incident report →

Major July 7, 2026 Actions and Codespaces APIs experiencing partial failures 2h 2m Actions, Codespaces

Started Jul 07, 2026, 02:14 PM UTC· resolved Jul 07, 2026, 04:17 PM UTC

  1. investigating Jul 07, 2026, 02:14 PM UTC

    We are investigating reports of degraded performance for Actions and Codespaces

  2. investigating Jul 07, 2026, 02:14 PM UTC

    Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time. Actions runs in progress are continuing successfully.

  3. investigating Jul 07, 2026, 02:32 PM UTC

    Codespaces is experiencing degraded availability. We are continuing to investigate.

  4. investigating Jul 07, 2026, 02:47 PM UTC

    Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time. Retries may be successful. Actions runs and codespaces in progress are continuing successfully. We are continuing to investigate the source of these errors.

  5. investigating Jul 07, 2026, 03:06 PM UTC

    Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful. We continue to investigate the source of these errors.

  6. investigating Jul 07, 2026, 03:50 PM UTC

    Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation.

  7. investigating Jul 07, 2026, 04:00 PM UTC

    We have rolled out the mitigation and are seeing recovery.

  8. monitoring Jul 07, 2026, 04:02 PM UTC

    The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability.

  9. resolved Jul 07, 2026, 04:17 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.

Read the full incident report →

Minor July 2, 2026 Incident with Pages 1h 31m Pages

Started Jul 02, 2026, 04:54 PM UTC· resolved Jul 02, 2026, 06:25 PM UTC

  1. investigating Jul 02, 2026, 04:54 PM UTC

    We are investigating reports of degraded performance for Pages

  2. investigating Jul 02, 2026, 04:56 PM UTC

    We are investigating reports of slow and failing Pages deployments. Access to Pages is unaffected.

  3. investigating Jul 02, 2026, 05:57 PM UTC

    Pages deployment latency is recovering. The team continues working toward full mitigation and a return to nominal state.

  4. resolved Jul 02, 2026, 06:25 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.

Read the full incident report →

Minor July 1, 2026 Delays in copilot budget limits resets for some users 2h 34m Copilot

Started Jul 01, 2026, 10:51 AM UTC· resolved Jul 01, 2026, 01:26 PM UTC

  1. investigating Jul 01, 2026, 10:51 AM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Jul 01, 2026, 11:44 AM UTC

    We have identified the likely reason for the delays and are working on a solution.

  3. investigating Jul 01, 2026, 12:42 PM UTC

    A fix for the delayed resets is currently being deployed.

  4. monitoring Jul 01, 2026, 01:04 PM UTC

    The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.

  5. monitoring Jul 01, 2026, 01:05 PM UTC

    The fix has been deployed globally and we are monitoring the results

  6. resolved Jul 01, 2026, 01:26 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.

Read the full incident report →

Minor June 30, 2026 Disruption with some GitHub services - Signup Flow 10m

Started Jun 30, 2026, 03:38 PM UTC· resolved Jun 30, 2026, 03:49 PM UTC

  1. investigating Jun 30, 2026, 03:38 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. resolved Jun 30, 2026, 03: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.

Read the full incident report →

Minor June 28, 2026 Disruption with some GitHub services 3h 5m

Started Jun 28, 2026, 05:50 PM UTC· resolved Jun 28, 2026, 08:55 PM UTC

  1. investigating Jun 28, 2026, 05:50 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jun 28, 2026, 05:59 PM UTC

    Copilot cloud agent is experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. We have identified the issue and are validating a fix.

  3. investigating Jun 28, 2026, 06:31 PM UTC

    Copilot cloud agent is experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. We have validated a fix and are deploying that fix now.

  4. investigating Jun 28, 2026, 08:02 PM UTC

    Copilot cloud agent had been experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. A fix has been deployed and we are validating that fix.

  5. resolved Jun 28, 2026, 08:55 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.

Read the full incident report →

Minor June 27, 2026 Disruption with some GitHub services 6h 30m

Started Jun 27, 2026, 02:02 PM UTC· resolved Jun 27, 2026, 08:33 PM UTC

  1. investigating Jun 27, 2026, 02:02 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jun 27, 2026, 02:02 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 19:00 UTC.

  3. monitoring Jun 27, 2026, 02:04 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  4. monitoring Jun 27, 2026, 06:22 PM UTC

    This is progressing as expected, but we're going to extend the maintenance window by a couple of hours. Our new expected completion time is 21:00 UTC.

  5. monitoring Jun 27, 2026, 08:19 PM UTC

    Maintenance has completed and we've begun normalizing traffic in EU. We will monitor for a while longer before confirming resolution.

  6. resolved Jun 27, 2026, 08:33 PM UTC

    This incident was used to notify for a maintenance event. There is no specific root cause analysis. Work progressed as planned without any issues to report.

Read the full incident report →

Major June 25, 2026 Degradation with Webhooks, Pull Requests and Actions 37m Webhooks, Issues, Pull Requests, Actions

Started Jun 25, 2026, 05:50 PM UTC· resolved Jun 25, 2026, 06:27 PM UTC

  1. investigating Jun 25, 2026, 05:50 PM UTC

    We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks

  2. investigating Jun 25, 2026, 05:53 PM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  3. investigating Jun 25, 2026, 05:58 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  4. monitoring Jun 25, 2026, 06:07 PM UTC

    The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

  5. monitoring Jun 25, 2026, 06:27 PM UTC

    We identified an issue that caused degradation across multiple services including Webhooks, Pull Requests, Actions, and Issues. Customers may have experienced delays or failures with these services. We have applied mitigations and affected services have recovered.

  6. resolved Jun 25, 2026, 06:27 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.

Read the full incident report →

Minor June 23, 2026 We are seeing elevated errors with Next Edit Suggestions and Completions 24m

Started Jun 23, 2026, 11:04 PM UTC· resolved Jun 23, 2026, 11:29 PM UTC

  1. investigating Jun 23, 2026, 11:04 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jun 23, 2026, 11:26 PM UTC

    We have applied a rollback and are seeing recovery.

  3. monitoring Jun 23, 2026, 11:27 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  4. resolved Jun 23, 2026, 11:29 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.

Read the full incident report →

Notice June 17, 2026 Incident With Webhooks –

Started Jun 17, 2026, 07:00 PM UTC· resolved Jun 17, 2026, 07:00 PM UTC

  1. resolved Jun 19, 2026, 02:38 PM UTC

    On June 17, 2026, between 11:35 UTC and 19:20 UTC, the Webhooks service was degraded and delivered webhook payloads with missing installation information. On average, 11.3% of webhook deliveries were impacted. Customers relying on the installation field for authentication or routing were unable to process affected webhooks. A smaller subset of deliveries for the security_advisory event (0.04%) were delivered successfully but were not recorded for redelivery. This was due to a defect in a new delivery code path that failed to include installation data in webhook payloads. We mitigated the incident by disabling the feature flag controlling the new code path. We are working to improve our automated validation of webhook payloads, and introduce automated alerting for webhook payload regressions to reduce our time to detection and mitigation of issues like this one in the future. The following events were affected: branch_protection_configuration, code_scanning_alert, commit_comment, custom_property, custom_property_values, dependabot_alert, deploy_key, deployment_protection_rule, deployment_review, dismissal_request_code_scanning, dismissal_request_secret_scanning, installation_target, member, membership, merge_queue_entry, org_block, organization, projects_v2, projects_v2_item, pull_request_review_thread, repository_ruleset, secret_scanning_alert, secret_scanning_alert_location, secret_scanning_scan, security_and_analysis, star, sub_issues, team, team_add, workflow_job.

Read the full incident report →

Minor June 17, 2026 Disruption with Copilot next edit suggestions 1h 30m

Started Jun 17, 2026, 05:57 PM UTC· resolved Jun 17, 2026, 07:28 PM UTC

  1. investigating Jun 17, 2026, 05:57 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jun 17, 2026, 06:40 PM UTC

    We have identified a likely cause and are applying a mitigation

  3. investigating Jun 17, 2026, 07:09 PM UTC

    We have applied mitigation and are seeing recovery

  4. monitoring Jun 17, 2026, 07:14 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  5. resolved Jun 17, 2026, 07:28 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.

Read the full incident report →