GitHub Outage History

GitHub is up right now

GitHub had 131 outages in the last 2 years totaling 49h 36m of downtime — averaging 5.4 incidents per month.

There were 131 GitHub outages since February 27, 2026 totaling 49h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.githubstatus.com · Aggregated across GitHub products

Notice August 21, 2026

Degraded Git Operations over SSH

Detected by Pingoru
Aug 21, 2026, 02:00 PM UTC
Resolved
Aug 21, 2026, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 24, 2026, 07:19 AM UTC

    On August 21, 2026, between 14:00 and 14:07 UTC, dotcom Git operations over SSH were degraded. Successful Git operations over SSH fell by more than 95% for during the peak impact window, making clone, fetch, or push over SSH effectively unavailable to most users for approximately four minutes. Git operations over HTTPS were not affected. The incident was caused by a software defect in our load-balancing infrastructure that was triggered by a configuration change. The defect only occurred when connections passed through multiple layers of load balancers running the new configuration, which meant it was not detected during canary testing. We mitigated the incident by rolling back the configuration change. We are adding regression coverage for multi-layer load-balancer configurations and improving monitoring and alerting for Git operations over SSH to reduce our time to detection and mitigation of similar issues in the future.

Read the full incident report →

Minor August 18, 2026

Intermittent failures in runner group and runner-related permissions pages

Detected by Pingoru
Aug 18, 2026, 07:40 AM UTC
Resolved
Aug 18, 2026, 11:42 AM UTC
Duration
4h 2m
Timeline · 5 updates
  1. investigating Aug 18, 2026, 07:40 AM UTC

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

  2. monitoring Aug 18, 2026, 07:40 AM UTC

    We are investigating reports of failure to load runner groups and runner-related permissions for customers using larger runners.

  3. monitoring Aug 18, 2026, 10:41 AM UTC

    We have identified the source of a communication issue between Actions services and are working toward mitigation. Customers may experience failure to load runner groups and runner-related permissions issues when using Larger Runners.

  4. monitoring Aug 18, 2026, 11:24 AM UTC

    We have applied a mitigation and are seeing recovery signals. We will continue monitoring recovery and providing updates.

  5. resolved Aug 18, 2026, 11:42 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 August 17, 2026

Incident with GitHub.com

Detected by Pingoru
Aug 17, 2026, 01:40 PM UTC
Resolved
Aug 17, 2026, 09:15 PM UTC
Duration
7h 35m
Affected: Git OperationsWebhooksAPI RequestsIssuesPull RequestsActionsPagesCopilot
Timeline · 36 updates

Read the full incident report →

Minor August 13, 2026

Disruption with GHEC Team Sync

Detected by Pingoru
Aug 13, 2026, 04:21 PM UTC
Resolved
Aug 13, 2026, 06:27 PM UTC
Duration
2h 6m
Timeline · 4 updates
  1. investigating Aug 13, 2026, 04:21 PM UTC

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

  2. investigating Aug 13, 2026, 04:21 PM UTC

    GHEC Team Sync is currently degraded for enterprises with personal accounts, causing delays when syncing teams to IdP groups. We have identified the cause of the delays and are working on a mitigation. We will provide an update on our progress at 20:00 UTC.

  3. investigating Aug 13, 2026, 06:27 PM UTC

    We have deployed a mitigation. At this time GHEC Team Sync has recovered for enterprises with personal accounts. Teams syncing to IdP groups have returned to their normal cadence.

  4. resolved Aug 13, 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 August 13, 2026

Errors with the Fable 5 Model in Copilot

Detected by Pingoru
Aug 13, 2026, 02:43 PM UTC
Resolved
Aug 13, 2026, 03:47 PM UTC
Duration
1h 3m
Affected: Copilot AI Model Providers
Timeline · 5 updates
  1. investigating Aug 13, 2026, 02:43 PM UTC

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

  2. investigating Aug 13, 2026, 02:50 PM UTC

    We are experiencing degraded availability for the 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. investigating Aug 13, 2026, 03:23 PM UTC

    We are seeing modest recovery, but are still experiencing degraded availability for the 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.

  4. investigating Aug 13, 2026, 03:47 PM UTC

    The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

  5. resolved Aug 13, 2026, 03:47 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 August 12, 2026

Disruption with Login and Release Asset downloads

Detected by Pingoru
Aug 12, 2026, 09:39 PM UTC
Resolved
Aug 12, 2026, 10:56 PM UTC
Duration
1h 17m
Timeline · 4 updates
  1. investigating Aug 12, 2026, 09:39 PM UTC

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

  2. investigating Aug 12, 2026, 09:43 PM UTC

    We are investigating issues with Login and when downloading Release Assets. We will continue to keep users updated on progress towards mitigation.

  3. investigating Aug 12, 2026, 10:22 PM UTC

    We have identified the root cause and are working on mitigation. Errors on the login page and downloading release assets have decreased, but we are not fully mitigated. We will continue to provide updates.

  4. resolved Aug 12, 2026, 10:56 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 August 12, 2026

Incident with Pull Requests and Issues

Detected by Pingoru
Aug 12, 2026, 04:16 PM UTC
Resolved
Aug 12, 2026, 04:41 PM UTC
Duration
25m
Affected: IssuesPull Requests
Timeline · 5 updates
  1. investigating Aug 12, 2026, 04:16 PM UTC

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

  2. investigating Aug 12, 2026, 04:24 PM UTC

    We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.

  3. monitoring Aug 12, 2026, 04:35 PM UTC

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

  4. monitoring Aug 12, 2026, 04:38 PM UTC

    We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.

  5. resolved Aug 12, 2026, 04: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.

Read the full incident report →

Minor August 11, 2026

Incident with GraphQL API Requests

Detected by Pingoru
Aug 11, 2026, 02:50 PM UTC
Resolved
Aug 11, 2026, 08:06 PM UTC
Duration
5h 16m
Affected: API Requests
Timeline · 6 updates
  1. investigating Aug 11, 2026, 02:50 PM UTC

    We are investigating reports of degraded performance for API Requests

  2. investigating Aug 11, 2026, 03:28 PM UTC

    We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information

  3. investigating Aug 11, 2026, 04:49 PM UTC

    We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.

  4. monitoring Aug 11, 2026, 04:49 PM UTC

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

  5. monitoring Aug 11, 2026, 08:06 PM UTC

    We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident.

  6. resolved Aug 11, 2026, 08:06 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 August 10, 2026

Disruption with Copilot for access to some models

Detected by Pingoru
Aug 10, 2026, 08:27 PM UTC
Resolved
Aug 10, 2026, 09:50 PM UTC
Duration
1h 23m
Timeline · 6 updates
  1. investigating Aug 10, 2026, 08:27 PM UTC

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

  2. monitoring Aug 10, 2026, 08:39 PM UTC

    We are currently investigating reports of some Copilot users experiencing issues accessing certain models. Affected users may see errors or degraded functionality when attempting to use specific models. We are actively working on a fix and will provide updates as we have more information.

  3. monitoring Aug 10, 2026, 08:49 PM UTC

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

  4. monitoring Aug 10, 2026, 09:19 PM UTC

    The issue has been mitigated across all affected environments. We are currently deploying on a fix to prevent reoccurrence. We will provide another update once the fix has been deployed.

  5. monitoring Aug 10, 2026, 09:50 PM UTC

    We have deployed and validated the fix to prevent immediate reoccurrence. We will be performing additional work to limit these kinds of failures in the future.

  6. resolved Aug 10, 2026, 09:50 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 August 10, 2026

Disruption with creation of fine grained personal access tokens

Detected by Pingoru
Aug 10, 2026, 06:02 PM UTC
Resolved
Aug 10, 2026, 06:46 PM UTC
Duration
44m
Timeline · 5 updates
  1. investigating Aug 10, 2026, 06:02 PM UTC

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

  2. investigating Aug 10, 2026, 06:09 PM UTC

    We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but the token was not created.

  3. monitoring Aug 10, 2026, 06:21 PM UTC

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

  4. monitoring Aug 10, 2026, 06:22 PM UTC

    We identified the source of the issue affecting creation of fine-grained personal access tokens and have applied a mitigation. Users should now be able to create new fine-grained tokens successfully. We are continuing to monitor to confirm full recovery.

  5. resolved Aug 10, 2026, 06:46 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 August 6, 2026

Incident with Pages - Deployment Lag

Detected by Pingoru
Aug 06, 2026, 03:03 PM UTC
Resolved
Aug 06, 2026, 04:22 PM UTC
Duration
1h 19m
Affected: Pages
Timeline · 3 updates
  1. investigating Aug 06, 2026, 03:03 PM UTC

    We are investigating reports of degraded performance for Pages

  2. monitoring Aug 06, 2026, 03:50 PM UTC

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

  3. resolved Aug 06, 2026, 04:22 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 August 5, 2026

Some Copilot Cloud Agent jobs not starting

Detected by Pingoru
Aug 05, 2026, 11:38 AM UTC
Resolved
Aug 05, 2026, 01:00 PM UTC
Duration
1h 21m
Timeline · 4 updates
  1. investigating Aug 05, 2026, 11:38 AM UTC

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

  2. monitoring Aug 05, 2026, 12:01 PM UTC

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

  3. monitoring Aug 05, 2026, 12:10 PM UTC

    Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.

  4. resolved Aug 05, 2026, 01:00 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 August 3, 2026

Incident with Copilot

Detected by Pingoru
Aug 03, 2026, 09:53 AM UTC
Resolved
Aug 03, 2026, 11:25 AM UTC
Duration
1h 31m
Affected: Copilot
Timeline · 5 updates
  1. investigating Aug 03, 2026, 09:53 AM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating Aug 03, 2026, 09:54 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.

  3. investigating Aug 03, 2026, 10:35 AM UTC

    We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations.

  4. monitoring Aug 03, 2026, 11:19 AM UTC

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

  5. resolved Aug 03, 2026, 11:25 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 August 1, 2026

Degraded availability GPT 5.6 Luna

Detected by Pingoru
Aug 01, 2026, 11:16 AM UTC
Resolved
Aug 01, 2026, 12:30 PM UTC
Duration
1h 13m
Affected: Copilot AI Model Providers
Timeline · 5 updates
  1. investigating Aug 01, 2026, 11:16 AM UTC

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

  2. investigating Aug 01, 2026, 11:20 AM UTC

    We are experiencing degraded availability for the GPT-5.6 Luna 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. investigating Aug 01, 2026, 12:13 PM UTC

    We keep working with our upstream model provider, and are observing recovery. We continue monitoring to ensure stability.

  4. investigating Aug 01, 2026, 12:29 PM UTC

    The issues with our upstream model provider have been resolved, and GPT-5.6 Luna is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

  5. resolved Aug 01, 2026, 12:30 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 30, 2026

Copilot model Claude Fable 5 experiencing elevated errors

Detected by Pingoru
Jul 30, 2026, 09:07 AM UTC
Resolved
Jul 30, 2026, 10:12 AM UTC
Duration
1h 4m
Affected: Copilot AI Model Providers
Timeline · 4 updates
  1. investigating Jul 30, 2026, 09:07 AM UTC

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

  2. investigating Jul 30, 2026, 09:17 AM 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. investigating Jul 30, 2026, 10:11 AM UTC

    The issues with our upstream model provider have been resolved, and Claude Fable 5 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

  4. resolved Jul 30, 2026, 10:12 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 →

Notice July 27, 2026

Test Incident Posted in Error – No Customer Impact (Will Be Removed)

Detected by Pingoru
Jul 27, 2026, 07:31 PM UTC
Resolved
Jul 27, 2026, 07:37 PM UTC
Duration
5m
Timeline · 3 updates
  1. investigating Jul 27, 2026, 07:31 PM UTC

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

  2. investigating Jul 27, 2026, 07:31 PM UTC

    This is just a test of our systems. Please ignore.

  3. resolved Jul 27, 2026, 07: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 →

Critical July 25, 2026

Actions run failures and delays

Detected by Pingoru
Jul 25, 2026, 12:31 PM UTC
Resolved
Jul 25, 2026, 01:13 PM UTC
Duration
41m
Affected: Actions
Timeline · 6 updates
  1. investigating Jul 25, 2026, 12:31 PM UTC

    We are investigating reports of degraded availability for Actions

  2. investigating Jul 25, 2026, 12:34 PM UTC

    We are experiencing issues with GitHub Actions that are causing workflow run failures and delays for some users. Our engineering team is actively investigating the infrastructure issue and working to restore full functionality.

  3. investigating Jul 25, 2026, 12:58 PM UTC

    We have applied a mitigation for the infrastructure issue affecting GitHub Actions. Workflow run failures and delays are improving but not yet fully resolved. Our engineering team continues to work on restoring full functionality across all affected infrastructure.

  4. monitoring Jul 25, 2026, 12:59 PM UTC

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

  5. monitoring Jul 25, 2026, 01:12 PM UTC

    We have seen recovery in GitHub Actions performance following our earlier mitigation. Workflow runs are processing normally, though jobs queued before 12:40 UTC may still experience failures and will need to be retried.

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

Several GPT models degraded

Detected by Pingoru
Jul 25, 2026, 09:42 AM UTC
Resolved
Jul 25, 2026, 10:11 AM UTC
Duration
28m
Affected: Copilot AI Model Providers
Timeline · 4 updates
  1. investigating Jul 25, 2026, 09:42 AM UTC

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

  2. investigating Jul 25, 2026, 09:48 AM UTC

    We are experiencing degraded availability for the GPT-5.2, GPT-5.3-Codex, GPT-5.4, GPT-5.4 Mini, GPT-5.6 Sol, GPT-5.6 Terra, and GPT-5.6 Luna models 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. monitoring Jul 25, 2026, 10:04 AM UTC

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

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

Read the full incident report →

Notice July 24, 2026

Incident With Blocked GitHub.com Traffic

Detected by Pingoru
Jul 24, 2026, 11:00 AM UTC
Resolved
Jul 24, 2026, 11:00 AM UTC
Duration
—
Timeline · 1 update
  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 →

Minor July 22, 2026

Disruption with actions hosted runners

Detected by Pingoru
Jul 22, 2026, 08:43 PM UTC
Resolved
Jul 22, 2026, 10:09 PM UTC
Duration
1h 25m
Affected: Actions
Timeline · 5 updates
  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

Detected by Pingoru
Jul 21, 2026, 10:31 AM UTC
Resolved
Jul 21, 2026, 11:57 AM UTC
Duration
1h 25m
Timeline · 4 updates
  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

Detected by Pingoru
Jul 20, 2026, 04:03 PM UTC
Resolved
Jul 20, 2026, 06:37 PM UTC
Duration
2h 33m
Affected: Copilot AI Model Providers
Timeline · 6 updates
  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 →