{"incident_id": "INC-2026-GITHUB-2dpbcq5j", "company": "GitHub", "date": "2026-10-01", "title": "Actions Job Delays", "severity": "MEDIUM", "service_stack": ["Actions", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-10-01 17:56:54 UTC] GitHub SRE (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.\n[2026-10-01 17:50:54 UTC] GitHub SRE (Investigating): GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.\n[2026-10-01 16:48:51 UTC] GitHub SRE (Investigating): We are currently applying a mitigation and anticipate recovery within thirty minutes.\n[2026-10-01 16:10:24 UTC] GitHub SRE (Investigating): We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.\n[2026-10-01 15:29:46 UTC] GitHub SRE (Investigating): We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.\n[2026-10-01 15:20:46 UTC] GitHub SRE (Investigating): Actions is experiencing degraded performance. We are continuing to investigate.\n[2026-10-01 15:10:52 UTC] GitHub SRE (Monitoring): The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.\n[2026-10-01 15:02:41 UTC] GitHub SRE (Investigating): Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: 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. GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition. We are currently applyi", "breaking_config_code": "# Incident architectural state during Actions Job Delays\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Actions\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/kdqxfjn5qg6q", "metadata": {"raw_id": "2dpbcq5j165n", "status": "resolved", "resolved_at": "2026-10-01T17:56:54.260Z"}}
{"incident_id": "INC-2026-GITHUB-c8466lzv", "company": "GitHub", "date": "2026-10-01", "title": "Elevated request latency", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-10-01 13:57:59 UTC] GitHub SRE (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.\n[2026-10-01 13:51:20 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-10-01 13:39:10 UTC] GitHub SRE (Investigating): We are investigating recurrent periods of elevated latency affecting web requests. We’ll share updates as more information becomes available.\n[2026-10-01 13:37:33 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: 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. The degradation has been mitigated. We are monitoring to ensure stability. We are investigating recurrent periods of elevated latency affecting web requests. We’ll share updates as more information becomes available. We are investigating reports of impacted performance", "breaking_config_code": "# Incident architectural state during Elevated request latency\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/cz0ngh11q0tf", "metadata": {"raw_id": "c8466lzvnmsv", "status": "resolved", "resolved_at": "2026-10-01T13:57:59.327Z"}}
{"incident_id": "INC-2026-GITHUB-dqn46wtv", "company": "GitHub", "date": "2026-10-01", "title": "[Retroactive] Actions workflow run failures after deployment gate approvals", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-10-01 11:34:16 UTC] GitHub SRE (Resolved): On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval.\n\n\nIf you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select \"Re-run all jobs.\" This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already completed to avoid repeating changes.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval.\n\n\nIf you're affected, you can trigger a new run or contact GitHub Support with links to your stuck r", "breaking_config_code": "# Incident architectural state during [Retroactive] Actions workflow run failures after deployment gate approvals\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/f0yg8jk2gm80", "metadata": {"raw_id": "dqn46wtvbdzv", "status": "resolved", "resolved_at": "2026-10-01T02:00:00.000Z"}}
{"incident_id": "INC-2026-GITHUB-169pg72g", "company": "GitHub", "date": "2026-09-28", "title": "Copilot Code Review is unable to complete reviews", "severity": "CRITICAL", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-28 22:08:20 UTC] GitHub SRE (Resolved): On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dependent service that stopped delivering data Copilot Code Review needs to complete a review. Review completion is an inherently delayed signal, because each review job takes time to start and finish, so it took longer to detect the impact.<br /><br />We mitigated the incident by reverting the change.<br /><br />We are working to add a faster signal for reviews that fail to complete, add deployment validation that confirms a Copilot Code Review completes end to end, improve how we track internal dependencies between services, and make our deployment pipeline more reliable to reduce our time to detection and mitigation of issues like this one in the future.\n[2026-09-28 22:08:12 UTC] GitHub SRE (Investigating): Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR.\n[2026-09-28 21:23:59 UTC] GitHub SRE (Investigating): Revert of the impacted change is in flight, expect full recovery once the deployment is done.\n[2026-09-28 21:16:39 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dependent service that stopped delivering data Copilot", "breaking_config_code": "# Incident architectural state during Copilot Code Review is unable to complete reviews\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/phqvtmdm3y2m", "metadata": {"raw_id": "169pg72gg9jr", "status": "resolved", "resolved_at": "2026-09-28T22:08:20.216Z"}}
{"incident_id": "INC-2026-GITHUB-1dk955gg", "company": "GitHub", "date": "2026-09-24", "title": "Disruption with billing information updates", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-24 20:41:12 UTC] GitHub SRE (Resolved): Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests failed at an average rate of 69.3%, reaching 100% at peak. <br /><br />An operating system upgrade exposed a compatibility issue in an adapter used by our HTTP client library, causing requests to stall. A subsequent change to shorten request timeouts caused stalled requests to return connection errors and increased the failure rate. <br /><br />We mitigated the incident on September 24, 2026 at 20:24 UTC by changing the HTTP client used for address validation. We have added alerting to detect similar issues sooner and are extending the fix to other integrations.\n[2026-09-24 20:24:57 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-09-24 20:10:12 UTC] GitHub SRE (Investigating): We have applied the mitigation and are seeing signs of recovery. We are continuing to monitor the system closely.\n[2026-09-24 18:22:35 UTC] GitHub SRE (Investigating): We are continuing to work on mitigation. We will post another update in approximately one hour.\n[2026-09-24 17:40:15 UTC] GitHub SRE (Investigating): We have identified the problem and are actively working on mitigation.\n[2026-09-24 16:51:48 UTC] GitHub SRE (Investigating): We are investigating failures on billing information updates. Customers may be unable to create or update their billing information in the meantime.\n[2026-09-24 16:51:32 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests failed at an average rate of 69.3%, reaching 100% at peak. <br /><br />An operating system upgrade exposed a compatibility issue in an adapter used by our HTTP client lib", "breaking_config_code": "# Incident architectural state during Disruption with billing information updates\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/g2q4g5kv9frp", "metadata": {"raw_id": "1dk955gg3bvz", "status": "resolved", "resolved_at": "2026-09-24T20:41:12.518Z"}}
{"incident_id": "INC-2026-GITHUB-8zc63m64", "company": "GitHub", "date": "2026-09-23", "title": "Incident across several services", "severity": "MEDIUM", "service_stack": ["API Requests", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-24 04:55:33 UTC] GitHub SRE (Resolved): Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced delayed label updates and stale search results in Projects. <br /><br />The infrastructure failure was isolated to our Azure Central US region. The API errors were mitigated by 10:58 UTC on September 23. Projects' processing continued to recover while an accumulated backlog was drained, and full service was restored at 04:55 UTC on September 24. <br /><br />The incident was caused by a failed planned maintenance operation on a primary database. Automated recovery initiated an emergency database failover, after which several replicas in the affected region were unable to resume replication correctly. This reduced available database capacity and caused the API errors and downstream Projects processing delays. <br /><br />We have mitigated the immediate failure mode. We are also improving maintenance safety checks, database failover handling, post-failover replica validation, and downstream processing resilience to reduce the likelihood and impact of similar incidents.\n[2026-09-24 04:55:27 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-09-24 03:14:15 UTC] GitHub SRE (Investigating): We are continuing to process the backlog of issue label updates for Projects. Label changes may still be delayed. All other services are operating normally.\n[2026-09-24 02:00:37 UTC] GitHub SRE (Investigating): We are continuing to process the backlog of issue label updates for Projects. Users may still see delays before label changes are reflected in Projects. All other services are operating normally.\n[2026-09-24 00:16:49 UTC] GitHub SRE (Investigating): We've deployed a change intended to accelerate processing of the backlog of issue label updates in Projects. A sizable backlog still remains and we continue working through it. All other services are operating normally. We will provide another update within the next hour.\n[2026-09-23 21:39:30 UTC] GitHub SRE (Investigating): Updates to issue labels may be delayed in being reflected in Projects. We are continuing to deploy a change that will accelerate processing of the backlog of label updates. All other services are available. We will provide another update within the next hour.\n[2026-09-23 20:26:02 UTC] GitHub SRE (Investigating): We are preparing to deploy a change that will mitigate the impact.\n[2026-09-23 18:42:01 UTC] GitHub SRE (Investigating): Continuing to investigate the lag that may be experienced in issue labels being accurately reflected in Projects. We are working on alternate solutions to process the backlog of label updates.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced delayed label updates and stale search results in Projects. <br /><br />The infrastructure failure was isolated to our Azure Central US region. The API errors were mitigated by ", "breaking_config_code": "# Incident architectural state during Incident across several services\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"API Requests\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API Requests cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/m1ps7yrhp4n8", "metadata": {"raw_id": "8zc63m64hy36", "status": "resolved", "resolved_at": "2026-09-24T04:55:33.949Z"}}
{"incident_id": "INC-2026-GITHUB-f6yrxnz5", "company": "GitHub", "date": "2026-09-20", "title": "Incident with Pull Requests", "severity": "MEDIUM", "service_stack": ["Pull Requests", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-09-20 23:22:16 UTC] GitHub SRE (Resolved): On September 20, 2026, between 21:46 and 22:24 UTC the Pull Requests service was degraded and pull request merge and test-merge commits were created late, with delays reaching approximately four minutes at peak. Merge commits were delayed rather than lost. Because some Actions workflow runs start only after a pull request's merge commit is created, a subset of workflow runs for pull request events were also delayed. <br /><br />This was due to a routine repository maintenance job for an unusually large repository consuming nearly all of the memory on a single Git storage server, which left that server unable to serve the Git operations used to create merge commits. <br /><br />We mitigated the incident by removing the affected server from service at 22:18 UTC, after which the queued merge commits were created within six minutes. <br /><br />We have capped the memory a single repository maintenance job may consume so that one repository cannot exhaust a server, and we have improved monitoring and alerting on storage server health to reduce our time to detection and mitigation of issues like this one in the future.\n[2026-09-20 22:32:02 UTC] GitHub SRE (Monitoring): A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.\n[2026-09-20 22:27:28 UTC] GitHub SRE (Monitoring): The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.\n[2026-09-20 22:13:37 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Pull Requests", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 20, 2026, between 21:46 and 22:24 UTC the Pull Requests service was degraded and pull request merge and test-merge commits were created late, with delays reaching approximately four minutes at peak. Merge commits were delayed rather than lost. Because some Actions workflow runs start only after a pull request's merge commit is created, a subset of workflow runs for pull request events were also delayed. <br /><br />This was due to a ", "breaking_config_code": "# Incident architectural state during Incident with Pull Requests\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Pull Requests\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Pull Requests cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/cx8xcm6k8f9s", "metadata": {"raw_id": "f6yrxnz5f7bs", "status": "resolved", "resolved_at": "2026-09-20T23:22:16.710Z"}}
{"incident_id": "INC-2026-GITHUB-nvy2q96m", "company": "GitHub", "date": "2026-09-17", "title": "Elevated rate of errors for OpenAI models provided by Copilot", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-17 21:49:01 UTC] GitHub SRE (Resolved): Between 20:26 and 21:17 UTC on September 17, 2026, GitHub Copilot experienced degradation affecting several GPT models, including GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-5.3-Codex, and GPT-6 Astra. Users encountered elevated error rates when using these models.<br /><br />The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.\n[2026-09-17 21:39:28 UTC] GitHub SRE (Monitoring): We are experiencing degraded availability for GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-6 Astra, GPT-5.3-Codex in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. The provider is working to mitigate the problem and we are monitoring recovery. We recommend choosing another model or selecting 'Auto' to continue using Copilot.\n[2026-09-17 20:59:02 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Between 20:26 and 21:17 UTC on September 17, 2026, GitHub Copilot experienced degradation affecting several GPT models, including GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-5.3-Codex, and GPT-6 Astra. Users encountered elevated error rates when using these models.<br /><br />The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider.", "breaking_config_code": "# Incident architectural state during Elevated rate of errors for OpenAI models provided by Copilot\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/t938cy7649sn", "metadata": {"raw_id": "nvy2q96mcmyg", "status": "resolved", "resolved_at": "2026-09-17T21:49:01.417Z"}}
{"incident_id": "INC-2026-GITHUB-nlxnbqnk", "company": "GitHub", "date": "2026-09-16", "title": "Degradation with Gemini 3.8 Flash", "severity": "HIGH", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-16 17:48:49 UTC] GitHub SRE (Resolved): On September 16, 2026, between 04:40 and 11:45 UTC, the Gemini 3.8 Flash model in GitHub Copilot experienced degraded availability. Requests to this model failed at an average rate of 6.4%, and the impact was highest during peak traffic hours. Other Copilot models were not affected. Users could continue to work with a different model or with 'Auto'.<br /><br />The degradation was caused due to a capacity issue with an upstream model provider. Failure rates returned to normal as the daily traffic peak passed. We monitored the model until it was healthy and resolved the incident at 17:48 UTC. We are working to make our systems resilient to cover peak demand for all the Copilot models.\n[2026-09-16 11:45:34 UTC] GitHub SRE (Monitoring): The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.\n[2026-09-16 10:58:41 UTC] GitHub SRE (Investigating): Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.\n[2026-09-16 08:28:57 UTC] GitHub SRE (Investigating): Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.\n[2026-09-16 07:21:00 UTC] GitHub SRE (Investigating): We are investigating reports of degraded availability for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 16, 2026, between 04:40 and 11:45 UTC, the Gemini 3.8 Flash model in GitHub Copilot experienced degraded availability. Requests to this model failed at an average rate of 6.4%, and the impact was highest during peak traffic hours. Other Copilot models were not affected. Users could continue to work with a different model or with 'Auto'.<br /><br />The degradation was caused due to a capacity issue with an upstream model provider. Fai", "breaking_config_code": "# Incident architectural state during Degradation with Gemini 3.8 Flash\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/hsjy12f57b24", "metadata": {"raw_id": "nlxnbqnkdzdl", "status": "resolved", "resolved_at": "2026-09-16T17:48:49.246Z"}}
{"incident_id": "INC-2026-GITHUB-bk7zgdcq", "company": "GitHub", "date": "2026-09-15", "title": "Disruption with some GitHub services", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-15 20:00:50 UTC] GitHub SRE (Resolved): On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock acquisition, which interrupted the job. We reverted the change to the internal caching service and restored normal operation by 20:00 UTC.<br /><br />We sincerely apologize for the disruption.\n[2026-09-15 19:48:02 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-09-15 19:11:31 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock acquisition, which interrupted the job. We reverted the change to the internal caching service and restored normal operation by 20:00 UTC.<br /><br />We sincerely apologi", "breaking_config_code": "# Incident architectural state during Disruption with some GitHub services\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/tbh60vgxfxj6", "metadata": {"raw_id": "bk7zgdcq7s9t", "status": "resolved", "resolved_at": "2026-09-15T20:00:50.512Z"}}
{"incident_id": "INC-2026-GITHUB-qwdwmtqg", "company": "GitHub", "date": "2026-09-15", "title": "Disruption with some GitHub services", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-15 11:17:22 UTC] GitHub SRE (Resolved): On September 15, 2026, between 05:45 and 09:50 UTC, the Claude Fable 5.1 model in GitHub Copilot experienced intermittently degraded availability, with an average error rate of 2.8%. During brief recurring 15 minute periods that recurred every ~45 minutes, availability for Claude Fable 5.1 dropped to a maximum of ~40% before recovering completely. Other Copilot models were not affected. Users could continue to work with a different model or with 'Auto'.<br /><br />The cause was an issue with an upstream model provider that intermittently rejected requests while overloaded. GitHub worked with the provider, who acknowledged and then resolved the underlying issue at 9:50 UTC, after which the model returned to constant normal availability. Once recovery was guaranteed, we resolved the incident at 11:17 UTC.<br /><br />To reduce the chance of recurrence and customer impact, GitHub is reviewing per-model availability alerting and automatic in-product fallback so that requests to a degraded model can shift to a healthy alternative more quickly.\n[2026-09-15 11:17:13 UTC] GitHub SRE (Investigating): The issues with our upstream model provider have been resolved, and Claude Fable 5.1 is once again available in Copilot products and IDE surfaces.<br /><br />We will continue monitoring to ensure stability, but mitigation is complete.\n[2026-09-15 11:09:33 UTC] GitHub SRE (Investigating): We continue to monitor intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customer-facing metrics have recovered, and we are awaiting confirmation from our upstream provider that the issue will not recur. Customers can select another model or Auto in the meantime.\n[2026-09-15 10:32:25 UTC] GitHub SRE (Investigating): We continue to investigate intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customers can use another model or select Auto while we monitor the situation.\n[2026-09-15 10:20:13 UTC] GitHub SRE (Investigating): Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.\n[2026-09-15 09:48:04 UTC] GitHub SRE (Monitoring): We are investigating degraded availability for Claude Fable 5.1, affecting some Copilot products and integrated development environments. The issue is caused by a problem with our upstream model provider. Customers can use another model or select Auto while we investigate.\n[2026-09-15 09:47:15 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 15, 2026, between 05:45 and 09:50 UTC, the Claude Fable 5.1 model in GitHub Copilot experienced intermittently degraded availability, with an average error rate of 2.8%. During brief recurring 15 minute periods that recurred every ~45 minutes, availability for Claude Fable 5.1 dropped to a maximum of ~40% before recovering completely. Other Copilot models were not affected. Users could continue to work with a different model or with ", "breaking_config_code": "# Incident architectural state during Disruption with some GitHub services\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6pn81yd1x4hz", "metadata": {"raw_id": "qwdwmtqghpk5", "status": "resolved", "resolved_at": "2026-09-15T11:17:22.038Z"}}
{"incident_id": "INC-2026-GITHUB-kzh5j0mt", "company": "GitHub", "date": "2026-09-14", "title": "Actions Larger Runner Jobs for some customers may be slow to start", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-14 19:35:48 UTC] GitHub SRE (Resolved): On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, <b>5.7%</b> of larger-runner jobs were affected. <br /><br />A routine expansion of our compute capacity exposed a bug in how our provisioning system handled capacity records when selecting where to create runner virtual machines. This slowed the creation of new runners, leaving insufficient runner capacity to start affected jobs promptly. <br /><br />We restored normal provisioning by correcting the affected capacity records. We have fixed the underlying capacity-selection bug to prevent this failure from recurring. We have also added alerts for VM-record creation failures associated with this capacity issue.\n[2026-09-14 19:01:52 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-09-14 18:40:25 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, <b>5.7%</b> of larger-runner jobs were affected. <br /><br />A routine expansion of our compute capacity exposed a bug in how our provisioning system handled capacity records when selecting where to create runner virtual machines. This slowed the creation of new run", "breaking_config_code": "# Incident architectural state during Actions Larger Runner Jobs for some customers may be slow to start\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/f2b6fd4l83wy", "metadata": {"raw_id": "kzh5j0mt7qwc", "status": "resolved", "resolved_at": "2026-09-14T19:35:48.136Z"}}
{"incident_id": "INC-2026-GITHUB-0rn90wk1", "company": "GitHub", "date": "2026-09-13", "title": "Incident with several GitHub Services", "severity": "CRITICAL", "service_stack": ["API Requests", "Issues", "Pull Requests", "Actions"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-13 10:44:55 UTC] GitHub SRE (Resolved): On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications, Code Scanning, Git LFS, and new account signup.  At peak, 8.8% of requests to create GitHub App installation access tokens failed. Token issuance for Actions workflows was also affected, impacting approximately 4% of workflows during the incident time frame. Creating issues through the web interface failed for about 96% of attempts, and signup failures were above 90%.  <br /> <br />The cause was an internal data-cleanup job that began writing to a shared database cluster at 07:33 UTC. That cluster stores permission data read on nearly every authenticated request. The safeguard that was pacing the background job watched only one health signal — how far the database replicas were lagging — and that signal stayed low the whole time. It did not account for the load building on the primary itself, so the job kept writing while the primary quietly ran toward its limit. <br /><br />When the primary ran out of available connections, requests that needed it could not complete. First, there was no quick timeout on these database calls, so request handlers waited on the stalled database instead of failing fast, and the shared request-handling capacity degraded into site-wide errors. Second, a retry loop around token creation kept re-sending the writes that were already failing, which held the database saturated rather than letting it recover. <br /><br />Monitoring declared the incident at 08:50 UTC, but due to the broad impact and amplification from token creation, it took time to identify the source of the load. First responders mitigated by shedding internal load and pausing the job, and all services recovered by 10:44 UTC. <br /><br />To prevent recurrence, we are rate-limiting background jobs against shared, customer-serving databases by default, and adding automatic pausing and paging on primary-server load rather than replication lag alone. We are also surfacing running background work directly alongside database health signals so responders can see and pause it without leaving those dashboards, bounding retries in the token-issuing path, and adding request-level timeouts so one unhealthy database cannot consume shared web server capacity. In addition, we are breaking apart this database cluster to remove the single point of failure. We will be moving various service-specific data, including the authorization data, out of this shared cluster in the next two weeks.\n[2026-09-13 10:28:45 UTC] GitHub SRE (Investigating): Pull Requests is experiencing degraded performance. We are continuing to investigate.\n[2026-09-13 10:26:55 UTC] GitHub SRE (Investigating): We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor\n[2026-09-13 09:36:23 UTC] GitHub SRE (Investigating): We're seeing increased database replication delays on collab which is causing increased error rates in authorization endpoints and follow-on increased error rates across the system - we are investigating\n[2026-09-13 09:25:56 UTC] GitHub SRE (Investigating): Actions is experiencing degraded performance. We are continuing to investigate.\n[2026-09-13 09:16:11 UTC] GitHub SRE (Investigating): We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications, Code Scanning, Git LFS, and new account signup.  At peak, 8.8% of requests to create GitHub App installation access tokens failed. Token issuance for Actions workflows was also affected, impacting approximately 4% of workflows during the incident ", "breaking_config_code": "# Incident architectural state during Incident with several GitHub Services\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"API Requests\", \"Issues\", \"Pull Requests\", \"Actions\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API Requests cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8f3xch4y0v2k", "metadata": {"raw_id": "0rn90wk115q9", "status": "resolved", "resolved_at": "2026-09-13T10:44:55.016Z"}}
{"incident_id": "INC-2026-GITHUB-zw1hbx2y", "company": "GitHub", "date": "2026-09-04", "title": "Disruption with Copilot Code Review", "severity": "HIGH", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-09-04 22:26:46 UTC] GitHub SRE (Resolved): On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments.<br /><br />The incident was caused by a change to the service’s authentication permissions that prevented it from submitting affected reviews to the GitHub API. We reverted the change and restored normal operation by 22:26 UTC.<br /><br />We apologize for the disruption.\n[2026-09-04 22:25:44 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-09-04 21:54:22 UTC] GitHub SRE (Investigating): We are applying the mitigation and expect recovery within approximately 30 minutes.\n[2026-09-04 20:57:53 UTC] GitHub SRE (Investigating): Some users may be experiencing failures when using Copilot code review. We have identified the root cause and are working on a mitigation.\n[2026-09-04 20:39:03 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments.<br /><br />The incident was caused by a change to the service’s authentication permissions that prevented it from submitting affected reviews to the GitHub API. We reverted the change and restored normal operation by 22:26 UTC.<br /><br />We apologize for the", "breaking_config_code": "# Incident architectural state during Disruption with Copilot Code Review\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/dddfhld6fj0z", "metadata": {"raw_id": "zw1hbx2yyhvr", "status": "resolved", "resolved_at": "2026-09-04T22:26:46.740Z"}}
{"incident_id": "INC-2026-GITHUB-r05vk75c", "company": "GitHub", "date": "2026-09-04", "title": "Degradation in repos contents API", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-04 22:23:34 UTC] GitHub SRE (Resolved): On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.<br /><br />The cause was a capacity change that spread one of our clusters across additional availability zones; our zone-aware traffic routing kept sending requests to the original zone for performance, overloading a small set of servers while the new capacity sat idle. We resolved the incident by reverting the change and letting traffic rebalance.<br /><br />We are improving per-zone capacity guarantees, cross-zone load-shedding, and pre-production testing of multi-zone changes to prevent recurrence.\n[2026-09-04 22:02:15 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.<br /><br />The cause was a capacity change that spread one of our clusters across additional availability zones; our zone-aware traffic routing kept sending requests to the original zone for performance, overloading a small set of servers while the new capacity", "breaking_config_code": "# Incident architectural state during Degradation in repos contents API\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/vhmsw2rhdcgv", "metadata": {"raw_id": "r05vk75c594j", "status": "resolved", "resolved_at": "2026-09-04T22:23:34.887Z"}}
{"incident_id": "INC-2026-GITHUB-ktdr5t0x", "company": "GitHub", "date": "2026-09-03", "title": "Incident with Grok Copilot AI Model Provider", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-03 17:11:47 UTC] GitHub SRE (Resolved): Between 13:22 and 17:11 UTC on September 03, 2026, GitHub Copilot experienced degradation affecting several Grok models, including Grok 4.5 and Grok 4.6. Users encountered elevated error rates, but other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.\n[2026-09-03 17:11:39 UTC] GitHub SRE (Investigating): The issues with our upstream model provider have been resolved, and Grok models are once again available in Copilot products and IDE surfaces.<br />We will continue monitoring to ensure stability, but mitigation is complete.\n[2026-09-03 14:22:44 UTC] GitHub SRE (Investigating): The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.\n[2026-09-03 14:20:35 UTC] GitHub SRE (Investigating): We are experiencing degraded availability for the Grok 4.6 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.<br />\n[2026-09-03 14:17:27 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Between 13:22 and 17:11 UTC on September 03, 2026, GitHub Copilot experienced degradation affecting several Grok models, including Grok 4.5 and Grok 4.6. Users encountered elevated error rates, but other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the pr", "breaking_config_code": "# Incident architectural state during Incident with Grok Copilot AI Model Provider\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/p217h6l54208", "metadata": {"raw_id": "ktdr5t0xwnhp", "status": "resolved", "resolved_at": "2026-09-03T17:11:47.860Z"}}
{"incident_id": "INC-2026-GITHUB-jk2dy5h9", "company": "GitHub", "date": "2026-09-01", "title": "Delays in commit processing", "severity": "MEDIUM", "service_stack": ["Pull Requests", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-09-01 16:01:21 UTC] GitHub SRE (Resolved): On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than 140,000 customer accounts had at least one delayed refresh during the most affected 75 minutes. Pushing commits and opening pull requests continued to work normally. The incident was caused by a sharp, concentrated surge in push volume that saturated worker pools and job queueing infrastructure. Autoscaling did not increase capacity as intended, so the backlog did not clear on its own. <br /><br />The incident was mitigated by manually scaling the affected worker pools and increasing push-processing capacity. This allowed the system to process the backlog, after which refresh times returned to normal. To reduce the likelihood and impact of similar incidents, we are adding quotas and throttling earlier in the push path so a single concentrated source of load cannot saturate shared capacity, improving worker-pool autoscaling so capacity is added automatically, and improving monitors for background job processing so on-call is paged before customers experience delayed pull request updates.\n[2026-09-01 16:00:50 UTC] GitHub SRE (Investigating): Time to update pull request diffs have improved to normal thresholds.\n[2026-09-01 15:00:46 UTC] GitHub SRE (Investigating): Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.\n[2026-09-01 15:00:22 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Pull Requests", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than 140,000 customer accounts had at least one delayed refresh during the most affected 75 minutes. Pushing commits and opening pull requests continued to work normally. The ", "breaking_config_code": "# Incident architectural state during Delays in commit processing\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Pull Requests\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Pull Requests cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0xbhhq84v4mt", "metadata": {"raw_id": "jk2dy5h9yp3m", "status": "resolved", "resolved_at": "2026-09-01T16:01:21.369Z"}}
{"incident_id": "INC-2026-GITHUB-7fxts6gm", "company": "GitHub", "date": "2026-08-31", "title": "Elevated rate of errors for OpenAI models provided by Copilot", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-31 09:58:14 UTC] GitHub SRE (Resolved): Between 08:37 and 09:41 UTC on August 31, 2026, GitHub Copilot experienced degradation affecting several GPT models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, and the gpt-5.6 family (Luna, Sol, and Terra). Users encountered elevated error rates and interrupted streaming responses. Other models were not affected.<br /><br />The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.\n[2026-08-31 09:58:02 UTC] GitHub SRE (Monitoring): The issues with our upstream model provider have been resolved, and gpt-5.3-codex, gpt-5.4-mini, gpt-5.4-nano, gpt-5.5, and the gpt-5.6 family of models are once again available in Copilot products and IDE surfaces.<br /><br />We will continue monitoring to ensure stability, but mitigation is complete.\n[2026-08-31 09:51:13 UTC] GitHub SRE (Monitoring): The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.\n[2026-08-31 09:48:12 UTC] GitHub SRE (Investigating): One of our model providers has confirmed an incident on their end. We have provided them details to help identify the issue. We are starting to see recovery.\n[2026-08-31 09:22:18 UTC] GitHub SRE (Investigating): Copilot is experiencing a higher rate of errors for OpenAI models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4, and the gpt-5.6 family of models. Other models are not impacted. <br />\n[2026-08-31 09:15:48 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Between 08:37 and 09:41 UTC on August 31, 2026, GitHub Copilot experienced degradation affecting several GPT models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, and the gpt-5.6 family (Luna, Sol, and Terra). Users encountered elevated error rates and interrupted streaming responses. Other models were not affected.<br /><br />The degradation was caused by an issue with an upstream model provider. GitHub engineers detecte", "breaking_config_code": "# Incident architectural state during Elevated rate of errors for OpenAI models provided by Copilot\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8trzn5bjrtnn", "metadata": {"raw_id": "7fxts6gmq5gr", "status": "resolved", "resolved_at": "2026-08-31T09:58:14.157Z"}}
{"incident_id": "INC-2026-GITHUB-5bn0vk44", "company": "GitHub", "date": "2026-08-26", "title": "Disruption with GitHub Billing", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE", "STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-08-27 19:44:08 UTC] GitHub SRE (Resolved): On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers (<1%). <br /><br />This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure. <br /><br />We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.\n[2026-08-27 17:58:39 UTC] GitHub SRE (Investigating): No material change since the previous update. Service conditions remain stable following the mitigation, and we have not observed any further customer impact. We are actively monitoring the service while implementing targeted fixes to address the underlying root cause.\n[2026-08-27 16:20:23 UTC] GitHub SRE (Investigating): Our mitigation continues to hold, and service conditions remain stable. We are continuing to investigate the concentrated workload responsible for the issue and are preparing additional preventative improvements. We have not identified a material change in customer impact since the previous update. We will provide another update as the investigation progresses.\n[2026-08-27 14:49:36 UTC] GitHub SRE (Investigating): Our mitigation is still holding as we continue to investigate to find the root cause.\n[2026-08-27 01:35:35 UTC] GitHub SRE (Investigating): We are continuing to monitor the mitigation that we have applied for the billing page disruption.\n[2026-08-27 00:31:22 UTC] GitHub SRE (Investigating): We've applied a mitigation to unblock Copilot usage and have observed recovery for this particular impact. We're continuing to investigate and apply mitigations for the billing page disruption while monitoring to ensure Copilot remains recovered.\n[2026-08-26 23:42:06 UTC] GitHub SRE (Investigating): We are currently investigating increased errors with billing services. Customers may observe failed billing budget page loads, and users of the Copilot CLI may observe failures starting or continuing sessions.\n[2026-08-26 23:37:20 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers (<1%). <br /><br />This was caused by a concentrated workload that created processing delays in our data ", "breaking_config_code": "# Incident architectural state during Disruption with GitHub Billing\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/cpgst4hly3mh", "metadata": {"raw_id": "5bn0vk444m1w", "status": "resolved", "resolved_at": "2026-08-27T19:44:08.799Z"}}
{"incident_id": "INC-2026-GITHUB-tx9qn4kh", "company": "GitHub", "date": "2026-08-27", "title": "Incident with Copilot AI Model Providers", "severity": "CRITICAL", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-27 12:12:58 UTC] GitHub SRE (Resolved): On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. <br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.\n[2026-08-27 12:12:47 UTC] GitHub SRE (Investigating): The issues with our upstream model provider have been mitigated, and Kimi K3 is once again available in Copilot products and IDE surfaces.<br />We will continue monitoring to ensure stability.\n[2026-08-27 11:58:04 UTC] GitHub SRE (Investigating): Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.\n[2026-08-27 10:43:00 UTC] GitHub SRE (Investigating): We are experiencing degraded availability for the Kimi K3 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.\n[2026-08-27 10:04:52 UTC] GitHub SRE (Investigating): We are investigating reports of degraded availability for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. <br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar", "breaking_config_code": "# Incident architectural state during Incident with Copilot AI Model Providers\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/573gc8p4328b", "metadata": {"raw_id": "tx9qn4khd664", "status": "resolved", "resolved_at": "2026-08-27T12:12:58.387Z"}}
{"incident_id": "INC-2026-GITHUB-kfspvrz1", "company": "GitHub", "date": "2026-08-26", "title": "Incident with Actions and Pull Requests", "severity": "MEDIUM", "service_stack": ["Pull Requests", "Actions", "GitHub Actions", "Git"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-27 00:26:44 UTC] GitHub SRE (Resolved): On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. <br /><br />Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. <br /><br />We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. <br /><br />We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load.\n[2026-08-27 00:26:05 UTC] GitHub SRE (Monitoring): The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.\n[2026-08-27 00:25:58 UTC] GitHub SRE (Investigating): We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health.\n[2026-08-27 00:01:05 UTC] GitHub SRE (Investigating): We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.\n[2026-08-26 22:57:08 UTC] GitHub SRE (Investigating): We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.\n[2026-08-26 22:56:31 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Actions and Pull Requests", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. <br /><br />Bac", "breaking_config_code": "# Incident architectural state during Incident with Actions and Pull Requests\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Pull Requests\", \"Actions\", \"GitHub Actions\", \"Git\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Pull Requests cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/nrbwjftcz72d", "metadata": {"raw_id": "kfspvrz14xr0", "status": "resolved", "resolved_at": "2026-08-27T00:26:44.772Z"}}
{"incident_id": "INC-2026-GITHUB-y1t7p9fz", "company": "GitHub", "date": "2026-08-26", "title": "Incident with Actions", "severity": "CRITICAL", "service_stack": ["Actions", "Pages", "GitHub Actions", "Git"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-26 18:01:30 UTC] GitHub SRE (Resolved): On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start. The following 2 hours until 17:40 UTC, Actions runs were delayed starting by more than 5 minutes as the system caught up with delayed load. This impact was triggered by saturation of writes to the database primary used by the service processing triggers for Actions workflows. The primary was failed over, but the system did not fully recover. The saturation was caused by growing daily peak load combined with an upstream issue in GitHub’s event processing infrastructure, https://www.githubstatus.com/incidents/hcbtzksccj2f, which caused burst amplification of already-high load. Downstream throttles that were later used to recover were set ~10% too high to protect the system.  <br /><br />At 15:45 UTC, throttling combined with service restarts recovered the service’s core health. Those throttles were gradually raised between 15:54 and 17:22 to restore full webhook processing for Actions runs. This ramp was deliberately slow to ensure we did not re-overwhelm the system given our original throttling was now known to be incorrectly set. The queue of webhook events was fully burned down at 17:40 UTC. <br /><br />3.7% of larger-runner jobs, along with some scale-set self-hosted jobs, remained stuck in queued or “waiting for runner” state. We deployed a change to force-revoke jobs in this state, and they transitioned to failed at 18:40 UTC, about 50 minutes after incident mitigation. Releasing these jobs also freed hosted concurrency for larger-runner jobs. <br /><br />Customers using concurrency groups saw longer impact due to a separate issue where runners assigned to a subset of jobs disconnected before the force-revoke mitigation was deployed, which prevented runner acquisition from progressing and left jobs in a waiting-for-runner state. This was resolved at 01:00 UTC on August 27. <br /><br />Some runs triggered during the 15:02-15:45 UTC incident window encountered a bug that left them showing as queued even after service recovery. In the backend, these runs had already failed and will automatically move to canceled state 24 hours after creation. As follow-up, we are fixing the root cause of this queued state and improving our ability to bulk-cancel affected runs. <br /><br />Several changes to improve the general scalability of this part of Actions were already complete and deploying to production. Rollout of those changes will be complete within the next 24 hours. Further work to improve scale, resiliency, and more graceful degradation of Actions workflows are in flight. We are also taking a repair item to accelerate clearing of stuck queued or waiting jobs in similar future cases.\n[2026-08-26 18:00:48 UTC] GitHub SRE (Monitoring): All inbound queues have recovered and Actions is operating as expected. 3.7% of jobs assigned to larger runners during the early stage of this incident are stuck waiting for runner assignment. Those will be canceled within the hour. Other runners are successfully processing all new jobs.\n[2026-08-26 17:54:33 UTC] GitHub SRE (Monitoring): The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.\n[2026-08-26 17:32:22 UTC] GitHub SRE (Investigating): We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits.\n[2026-08-26 16:50:28 UTC] GitHub SRE (Investigating): We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour.\n[2026-08-26 16:49:07 UTC] GitHub SRE (Investigating): Pages is operating normally.\n[2026-08-26 16:14:16 UTC] GitHub SRE (Investigating): We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.\n[2026-08-26 15:48:07 UTC] GitHub SRE (Investigating): primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start. The following 2 hours until 17:40 UTC, Actions runs were delayed starting by more than 5 minutes as the system caught up with delayed load. This impact was triggered by saturation of writes to the database primary used by the service processing triggers for Actions workflows. The primary was failed over, but the system did not fully recover. The saturation was caused by gro", "breaking_config_code": "# Incident architectural state during Incident with Actions\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Actions\", \"Pages\", \"GitHub Actions\", \"Git\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/pg14nv9m3095", "metadata": {"raw_id": "y1t7p9fzrlj2", "status": "resolved", "resolved_at": "2026-08-26T18:01:30.665Z"}}
{"incident_id": "INC-2026-GITHUB-hcbtzksc", "company": "GitHub", "date": "2026-08-26", "title": "Disruption with some GitHub services", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-26 16:07:52 UTC] GitHub SRE (Resolved): Please refer to the combined summary in this related incident:  https://www.githubstatus.com/incidents/y1t7p9fzrlj2\n[2026-08-26 15:09:03 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Please refer to the combined summary in this related incident:  https://www.githubstatus.com/incidents/y1t7p9fzrlj2 We are investigating reports of impacted performance for some GitHub services.", "breaking_config_code": "# Incident architectural state during Disruption with some GitHub services\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4s4bvnc0frrj", "metadata": {"raw_id": "hcbtzksccj2f", "status": "resolved", "resolved_at": "2026-08-26T16:07:52.512Z"}}
{"incident_id": "INC-2026-GITHUB-lyppgxbq", "company": "GitHub", "date": "2026-08-24", "title": "Actions delays in starting runs", "severity": "MEDIUM", "service_stack": ["Actions", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE", "STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-08-24 14:34:42 UTC] GitHub SRE (Resolved): On August 24, 2026, between 13:33 UTC and 14:04 UTC,  3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. <br /> <br />The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely degraded and unable to perform disk operations, it continued sending healthy signals, preventing the system from immediately moving its work elsewhere. During this period, events assigned to the affected component accumulated until an automatic rebalance redirected processing to healthy components at 13:54 UTC. The queue backlog was cleared at 14:00 UTC, and processing returned to normal by 14:04 UTC. <br /><br />To prevent a recurrence, we are improving detection and automated remediation for unhealthy nodes that aren’t fully offline. We are also strengthening application-level resiliency, so stalled consumers are automatically removed quickly and their work reassigned without waiting for the affected node to recover.\n[2026-08-24 14:26:11 UTC] GitHub SRE (Monitoring): The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.\n[2026-08-24 14:22:59 UTC] GitHub SRE (Investigating): Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.\n[2026-08-24 13:56:55 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Actions", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 24, 2026, between 13:33 UTC and 14:04 UTC,  3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. <br /> <br />The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely", "breaking_config_code": "# Incident architectural state during Actions delays in starting runs\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Actions\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/v6ysclb9vcbd", "metadata": {"raw_id": "lyppgxbq1nyk", "status": "resolved", "resolved_at": "2026-08-24T14:34:42.451Z"}}
{"incident_id": "INC-2026-GITHUB-wt3hjqcr", "company": "GitHub", "date": "2026-08-24", "title": "Elevated errors on Fable 5 due to upstream provider", "severity": "HIGH", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-24 07:58:41 UTC] GitHub SRE (Resolved): On August 24th, 2026, between approximately 06:35 and 07:25 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates when using Claude Fable 5, with requests sometimes failing mid-response. No other models were impacted.<br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.\n[2026-08-24 07:12:33 UTC] GitHub SRE (Investigating): We are experiencing degraded availability for the Fable model in Copilot products and IDE surfaces. This is due to an issue with the upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.\n[2026-08-24 07:12:05 UTC] GitHub SRE (Investigating): We are investigating reports of degraded availability for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 24th, 2026, between approximately 06:35 and 07:25 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates when using Claude Fable 5, with requests sometimes failing mid-response. No other models were impacted.<br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to furth", "breaking_config_code": "# Incident architectural state during Elevated errors on Fable 5 due to upstream provider\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4dz9rv14dz14", "metadata": {"raw_id": "wt3hjqcrczfg", "status": "resolved", "resolved_at": "2026-08-24T07:58:41.636Z"}}
{"incident_id": "INC-2026-GITHUB-wms44hv6", "company": "GitHub", "date": "2026-08-21", "title": "Degraded Git Operations over SSH", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-24 07:19:23 UTC] GitHub SRE (Resolved): 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.  \n\nThe 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. \n\nWe mitigated the incident by rolling back the configuration change.  \n\nWe 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.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: 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.  \n\nThe incident was caused by a software defect in our load-balancing infrastructure that was triggered by a c", "breaking_config_code": "# Incident architectural state during Degraded Git Operations over SSH\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9nls6g9ln8p4", "metadata": {"raw_id": "wms44hv62t3p", "status": "resolved", "resolved_at": "2026-08-21T14:00:00.000Z"}}
{"incident_id": "INC-2026-GITHUB-bhbcjn4n", "company": "GitHub", "date": "2026-08-20", "title": "Intermittent failures creating agent tasks", "severity": "CRITICAL", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-08-21 00:37:20 UTC] GitHub SRE (Resolved): Between 13:57 UTC on August 20 and 00:37 UTC on August 21, 2026, some users of the Copilot Cloud Agent experienced delays of up to 60 to 90 minutes in seeing the status and results of their agent tasks. The agent tasks themselves continued to run and complete during this time; only the visibility of their status was delayed.<br /><br />The cause was a regional outage in a third-party cloud database service that Copilot uses to store agent task status. We failed over the affected database to a healthy region, added processing capacity to work through the backlog, and restored normal operation once the underlying service recovered. No task data was lost during the incident.<br /><br />To prevent repetition of similar incidents, we are removing the database configuration that made us vulnerable to this regional outage and improving our database failover procedures.\n[2026-08-20 20:37:06 UTC] GitHub SRE (Investigating): We are seeing gradual recovery in Copilot Cloud Agent task status visibility as we deploy a fix for the root cause. Session output remains delayed by approximately one hour while remediation continues.\n[2026-08-20 19:35:31 UTC] GitHub SRE (Investigating): We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility. Session output continues to be delayed by approximately 1 hour as our remediation steps take effect.\n[2026-08-20 18:45:23 UTC] GitHub SRE (Investigating): We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed by approximately 1 hour. We have taken additional steps to accelerate the recovery and expect this to take effect within the next hour.\n[2026-08-20 18:04:55 UTC] GitHub SRE (Investigating): We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed by approximately 1 hour. We have taken additional steps to accelerate the recovery and are continuing to monitor the impact.\n[2026-08-20 17:32:39 UTC] GitHub SRE (Investigating): We are observing gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed approximately 1 hour. We have taken additional steps to accelerate the recovery and are continuing to monitor the impact.\n[2026-08-20 17:05:20 UTC] GitHub SRE (Investigating): We are seeing signs of recovery for Copilot Cloud Agent task status visibility, but this recovery is slower than anticipated. We are pursuing additional mitigating measures to accelerate recovery.\n[2026-08-20 16:14:46 UTC] GitHub SRE (Investigating): Users are experiencing delays when starting tasks using Copilot Cloud Agent and are not be able to see the status of these tasks. Copilot Cloud Agent tasks are still being completed. We have identified the cause of the issue and are putting mitigations in place to return service to normal levels. We will provide another update about the expected recovery time shortly.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Between 13:57 UTC on August 20 and 00:37 UTC on August 21, 2026, some users of the Copilot Cloud Agent experienced delays of up to 60 to 90 minutes in seeing the status and results of their agent tasks. The agent tasks themselves continued to run and complete during this time; only the visibility of their status was delayed.<br /><br />The cause was a regional outage in a third-party cloud database service that Copilot uses to store agent task st", "breaking_config_code": "# Incident architectural state during Intermittent failures creating agent tasks\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/py1yl5mnq89c", "metadata": {"raw_id": "bhbcjn4n3jzp", "status": "resolved", "resolved_at": "2026-08-21T00:37:20.224Z"}}
{"incident_id": "INC-2026-GITHUB-bmpybhnr", "company": "GitHub", "date": "2026-08-18", "title": "Intermittent failures in runner group and runner-related permissions pages", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-18 11:42:59 UTC] GitHub SRE (Resolved): On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. <br /><br />The issue was caused by failures in backend requests reading runner and runner group data. The failures were caused by an expired authentication certificate unique to this service. The certificate had been rotated in KeyVault, but a step to enable use at runtime had been paused to prevent recurrence of previous incidents triggered by this operation. <br /><br />The impact was mitigated by completing the enablement of the new certificate in the backend system. We have added additional monitoring to this and other certificates. This service is also in the process of being replaced as part of our availability and scale work, bringing this authentication path and secret management in line with patterns across all GitHub services.\n[2026-08-18 11:24:06 UTC] GitHub SRE (Monitoring): We have applied a mitigation and are seeing recovery signals. We will continue monitoring recovery and providing updates.\n[2026-08-18 10:41:40 UTC] GitHub SRE (Monitoring): 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.\n[2026-08-18 07:40:42 UTC] GitHub SRE (Monitoring): We are investigating reports of failure to load runner groups and runner-related permissions for customers using larger runners.\n[2026-08-18 07:40:35 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. <br /><br />The issue was caused by failures in backend requests reading runner and runner group data. The failures were caused by an expired authentication certificate unique to this service. The certificate had been rotated in KeyVault, but a step to enable use at runtime had been paused t", "breaking_config_code": "# Incident architectural state during Intermittent failures in runner group and runner-related permissions pages\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/98zqb1k9jh0x", "metadata": {"raw_id": "bmpybhnrky3x", "status": "resolved", "resolved_at": "2026-08-18T11:42:59.304Z"}}
{"incident_id": "INC-2026-GITHUB-gx7js8bd", "company": "GitHub", "date": "2026-08-18", "title": "Incident with Actions", "severity": "HIGH", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-18 10:23:23 UTC] GitHub SRE (Resolved): On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to run jobs on Actions Larger Runners and were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. <br /><br />These issues were caused by failures in backend requests resolving essential metadata for starting Larger Runner workflow runs and for reading runner and runner group data. The failures were caused by an expired authentication certificate unique to this service. The certificate had been rotated in KeyVault, but a step to enable use at runtime had been paused to prevent recurrence of previous incidents that had been triggered by this operation. <br /><br />We mitigated the issues by completing the enablement of the new certificate in the backend system. We have added additional monitoring to this and other certificates. The relevant service is also in the process of being replaced as part of our availability and scale work, bringing this authentication path and secret management in line with patterns across all GitHub services.\n[2026-08-18 09:36:40 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to run jobs on Actions Larger Runners and were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. <br /><br />These issues were caused by failures in backend requests resolving essential metadata for starting Larger Runner workflow runs and for reading runner and runner group data. The failures were caused by an expired authentication", "breaking_config_code": "# Incident architectural state during Incident with Actions\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/q3ck88mqw08z", "metadata": {"raw_id": "gx7js8bd0jpz", "status": "resolved", "resolved_at": "2026-08-18T10:23:23.000Z"}}
{"incident_id": "INC-2026-GITHUB-zkxwbgr0", "company": "GitHub", "date": "2026-08-17", "title": "Incident with GitHub.com", "severity": "CRITICAL", "service_stack": ["Git Operations", "Webhooks", "API Requests", "Issues"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-08-17 21:15:46 UTC] GitHub SRE (Resolved): On August 17, 2026, from 13:28–21:15 UTC (7h 47m), GitHub.com experienced elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot. At peak, web/API error rates were approximately 20%, while archive and raw-content downloads reached approximately 50%. SAML/OIDC authentication, SCIM, and Team Sync were also affected, as well as Actions workflows in GHEC with Data Residency that depend on public workflow step definitions hosted on GitHub.com. Most services recovered by 16:36 UTC as our Central US datacenter recovered; Actions was degraded until approximately 18:03 UTC; and Copilot Token Service fully recovered by 21:02. <br /><br />Some of the failing traffic was moved from Central US to Northern Virginia where it was served successfully until the network failure in Central US was debugged and resolved. Delayed replies to a single internal endpoint triggered a latent retry bug in VS Code that amplified traffic by approximately 10x and caused delayed recovery for the Copilot Token Service. <br /><br />The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. Originally this was caused by an Istio sidecar pod reaching its concurrency limits and failing to auto scale correctly because of a misconfigured policy that watched host service but not sidecar limits. One failure cascaded to more and eventually four HAProxy nodes exhausted their flow limits, degrading the gateway auth path and causing widespread authentication latency and failures. The problem was worsened by optimistic retry logic which overloaded internal load balancers. Pausing HAProxy on those nodes simultaneously produced immediate broad recovery. <br /><br />The retry storm in Northern VA was fixed by 1) temporarily reducing gateway retry logic with a PR and 2) blocking inbound Copilot Token Service token requests at the load balancers with a 403, and then gradually ramping back up traffic per-site to allow callers to succeed. <br /><br />Residual Copilot authentication failures continued because client retry behavior amplified load: a failed token operation could generate many extra requests and enter a retry loop. Copilot Token Service traffic increased from a normal 7–9K RPS to 70–100K RPS. Reducing gateway authentication retries and blocking retry-triggering responses stabilized Copilot Token Service and completed recovery. <br /><br />Complicating factors that impeded recovery included a number of scraping attacks on codeload endpoints. <br /><br />To prevent recurrence, our follow-up actions include: <br /><br />- Correcting autoscaling policies to account for service-mesh sidecar concurrency and capacity. <br /><br />- Auditing Istio request, concurrency, and scaling limits across affected services. <br /><br />- Reviewing retry limits and backoff behavior across gateways and clients. <br /><br />- Addressing the VS Code retry behavior that amplified Copilot token traffic. <br /><br />- Improving load-balancer capacity monitoring and regional failover safeguards.\n[2026-08-17 20:45:28 UTC] GitHub SRE (Investigating): We are continuing to apply mitigations to address sporadic Copilot authentication failures in some applications. We expect full recovery within the next 30 minutes. Copilot usage via the GitHub CLI and GitHub App are unaffected.\n[2026-08-17 20:22:28 UTC] GitHub SRE (Investigating): Issues is operating normally.\n[2026-08-17 20:08:40 UTC] GitHub SRE (Investigating): We are continuing to investigate sporadic failures affecting Copilot authentication in some applications. Copilot usage via the GitHub CLI and GitHub App are unaffected.\n[2026-08-17 19:13:20 UTC] GitHub SRE (Investigating): We are continuing to investigate sporadic authentication failures. We have partially disabled authentication token retries and have seen improvement, and we are monitoring impact before fully applying this mitigation.\n[2026-08-17 19:01:45 UTC] GitHub SRE (Investigating): API Requests is operating normally.\n[2026-08-17 18:48:19 UTC] GitHub SRE (Investigating): API Requests is experiencing degraded availability. We are continuing to investigate.\n[2026-08-17 18:23:47 UTC] GitHub SRE (Investigating): The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 17, 2026, from 13:28–21:15 UTC (7h 47m), GitHub.com experienced elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot. At peak, web/API error rates were approximately 20%, while archive and raw-content downloads reached approximately 50%. SAML/OIDC authentication, SCIM, and Team Sync were also affected, as well as Actions workflows in GHEC with Data Residency that depend on public workflow step definitions", "breaking_config_code": "# Incident architectural state during Incident with GitHub.com\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Git Operations\", \"Webhooks\", \"API Requests\", \"Issues\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Git Operations cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/y1fl26l6wpzr", "metadata": {"raw_id": "zkxwbgr0cnmx", "status": "resolved", "resolved_at": "2026-08-17T21:15:46.623Z"}}
{"incident_id": "INC-2026-GITHUB-pf25whpq", "company": "GitHub", "date": "2026-08-13", "title": "Disruption with GHEC Team Sync", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-13 18:27:54 UTC] GitHub SRE (Resolved): On August 13, 2026, from 15:31:21 UTC to 18:27:55 UTC, GitHub Enterprise Cloud team synchronization was degraded for enterprises using personal accounts. Organization teams experienced delays of up to 3 to 13 hours (median 8 hours) when syncing with IdP groups, resulting in delayed access grants or removals for enterprise users across 2.8% of teams. <br /><br />A temporary change introduced to address a previous issue due to increased usage of this feature remained active after it was intended to be removed, causing synchronization delays during periods of high volume. We removed the temporary change and provisioned additional resources to handle the increased volume.\n[2026-08-13 18:27:38 UTC] GitHub SRE (Investigating): 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.\n[2026-08-13 16:21:51 UTC] GitHub SRE (Investigating): 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.\n[2026-08-13 16:21:33 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 13, 2026, from 15:31:21 UTC to 18:27:55 UTC, GitHub Enterprise Cloud team synchronization was degraded for enterprises using personal accounts. Organization teams experienced delays of up to 3 to 13 hours (median 8 hours) when syncing with IdP groups, resulting in delayed access grants or removals for enterprise users across 2.8% of teams. <br /><br />A temporary change introduced to address a previous issue due to increased usage of th", "breaking_config_code": "# Incident architectural state during Disruption with GHEC Team Sync\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/l6tmhqw07cmj", "metadata": {"raw_id": "pf25whpq58hh", "status": "resolved", "resolved_at": "2026-08-13T18:27:54.660Z"}}
{"incident_id": "INC-2026-GITHUB-24t8gsgq", "company": "GitHub", "date": "2026-08-13", "title": "Errors with the Fable 5 Model in Copilot", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-13 15:47:22 UTC] GitHub SRE (Resolved): On August 13th, 2026, between approximately 14:06 and 15:47 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates, peaking at 43% and averaging 12%. Users who selected Auto or alternative models were unaffected.<br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.\n[2026-08-13 15:47:15 UTC] GitHub SRE (Investigating): The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces.<br /><br />We will continue monitoring to ensure stability, but mitigation is complete.\n[2026-08-13 15:23:39 UTC] GitHub SRE (Investigating): 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.\n[2026-08-13 14:50:10 UTC] GitHub SRE (Investigating): 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.\n[2026-08-13 14:43:25 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 13th, 2026, between approximately 14:06 and 15:47 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates, peaking at 43% and averaging 12%. Users who selected Auto or alternative models were unaffected.<br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further imp", "breaking_config_code": "# Incident architectural state during Errors with the Fable 5 Model in Copilot\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8htrnxk0q09v", "metadata": {"raw_id": "24t8gsgqx2qb", "status": "resolved", "resolved_at": "2026-08-13T15:47:22.384Z"}}
{"incident_id": "INC-2026-GITHUB-k8vbzwqj", "company": "GitHub", "date": "2026-08-13", "title": "Incident with Webhooks", "severity": "MEDIUM", "service_stack": ["Git Operations", "Webhooks", "Issues", "Pull Requests"], "categories": ["DATABASE_DEGRADATION", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-13 15:36:34 UTC] GitHub SRE (Resolved): Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with smaller impact to Git operations, pull requests, issues, packages, sign-in, and Copilot. Impact cleared on its own at about 14:53 UTC once the job finished; we resolved the incident at 15:36 UTC. <br /><br />Affected users may have experienced a brief increase in errors and slower responses, primarily when creating, listing, or updating webhooks, with smaller impacts to pull requests, issues, packages, and Git operations. Failures peaked at about 1% for several minutes around 14:37 UTC. <br /><br />To prevent future incidents, we've already shipped an update that turns on the safer deletion path for organizations, along with caps on deletion holds on databases. Building on these changes, we're auditing all bulk deletion and cleanup jobs that write to shared databases to prevent similar issues in future.\n[2026-08-13 15:33:54 UTC] GitHub SRE (Monitoring): We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.\n[2026-08-13 15:33:02 UTC] GitHub SRE (Monitoring): The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.\n[2026-08-13 14:58:49 UTC] GitHub SRE (Investigating): We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies to prevent recurrence.\n[2026-08-13 14:56:45 UTC] GitHub SRE (Investigating): Packages is experiencing degraded performance. We are continuing to investigate.\n[2026-08-13 14:46:52 UTC] GitHub SRE (Investigating): Git Operations is experiencing degraded performance. We are continuing to investigate.\n[2026-08-13 14:46:23 UTC] GitHub SRE (Investigating): Issues is experiencing degraded performance. We are continuing to investigate.\n[2026-08-13 14:46:11 UTC] GitHub SRE (Investigating): Pull Requests is experiencing degraded performance. We are continuing to investigate.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with smaller impact to Git operations, pull requests, issues, packages, sign-in, and Copilot. Impact cleared on its own at about 14:53 UTC once the job finished; we resolved the inci", "breaking_config_code": "# Incident architectural state during Incident with Webhooks\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Git Operations\", \"Webhooks\", \"Issues\", \"Pull Requests\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Git Operations cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/f0cgtdc0kqxg", "metadata": {"raw_id": "k8vbzwqjkxzn", "status": "resolved", "resolved_at": "2026-08-13T15:36:34.631Z"}}
{"incident_id": "INC-2026-GITHUB-lsvy8xsf", "company": "GitHub", "date": "2026-08-12", "title": "Disruption with Login and Release Asset downloads", "severity": "HIGH", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-08-12 22:56:39 UTC] GitHub SRE (Resolved): On August 12 and 13, 2026, some anonymous (logged-out) requests to github.com experienced HTTP 5xx errors when loading pages like the sign-in page, and when downloading release assets, due to an unusual traffic pattern that repeatedly overloaded a part of our infrastructure that serves these types of requests. There were three windows of impact: (1) August 12 from 16:34 to 18:34 UTC, with an average error rate of 16.16% that peaked at 28.6%; (2) August 12 from 19:00 to 22:56 UTC, with an average error rate of 16.55% that peaked at 24.18%; and (3) August 13 from 06:19 to 08:05 UTC, with an average error rate of 2.01% that peaked at 7.49%.<br />Requests from signed-in users were unaffected.<br /><br />We mitigated the incidents by applying traffic controls at our network edge that limited any requests matching the pattern identified previously, thereby preventing overload on our systems.<br /><br />Since these incidents occurred, we have tightened our monitoring systems to alert server-side errors that affect logged-out traffic. We are also working to further strengthen our edge protections and reduce the time to detect and mitigate similar incidents.\n[2026-08-12 22:22:11 UTC] GitHub SRE (Investigating): 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.\n[2026-08-12 21:43:25 UTC] GitHub SRE (Investigating): We are investigating issues with Login and when downloading Release Assets. We will continue to keep users updated on progress towards mitigation.\n[2026-08-12 21:39:05 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 12 and 13, 2026, some anonymous (logged-out) requests to github.com experienced HTTP 5xx errors when loading pages like the sign-in page, and when downloading release assets, due to an unusual traffic pattern that repeatedly overloaded a part of our infrastructure that serves these types of requests. There were three windows of impact: (1) August 12 from 16:34 to 18:34 UTC, with an average error rate of 16.16% that peaked at 28.6%; (2) ", "breaking_config_code": "# Incident architectural state during Disruption with Login and Release Asset downloads\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/xp36nwz4rrh1", "metadata": {"raw_id": "lsvy8xsf0gxv", "status": "resolved", "resolved_at": "2026-08-12T22:56:39.025Z"}}
{"incident_id": "INC-2026-GITHUB-76t89hbf", "company": "GitHub", "date": "2026-08-12", "title": "Incident with Pull Requests and Issues", "severity": "MEDIUM", "service_stack": ["Issues", "Pull Requests", "GitHub Actions", "Git"], "categories": ["DATABASE_DEGRADATION"], "symptom_logs": "[2026-08-12 16:41:18 UTC] GitHub SRE (Resolved): Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application configuration to prevent similar mismatches from causing errors.\n[2026-08-12 16:38:38 UTC] GitHub SRE (Monitoring): 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.\n[2026-08-12 16:35:40 UTC] GitHub SRE (Monitoring): The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.\n[2026-08-12 16:24:30 UTC] GitHub SRE (Investigating): 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.\n[2026-08-12 16:16:18 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Issues and Pull Requests", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progress", "breaking_config_code": "# Incident architectural state during Incident with Pull Requests and Issues\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Issues\", \"Pull Requests\", \"GitHub Actions\", \"Git\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Issues cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ssd9z8l2g46v", "metadata": {"raw_id": "76t89hbfb09h", "status": "resolved", "resolved_at": "2026-08-12T16:41:18.768Z"}}
{"incident_id": "INC-2026-GITHUB-vm1w8zq9", "company": "GitHub", "date": "2026-08-11", "title": "Incident with GraphQL API Requests", "severity": "MEDIUM", "service_stack": ["API Requests", "GitHub Actions", "Git", "REST API"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-11 20:06:56 UTC] GitHub SRE (Resolved): On August 11, 2026, between 14:00 UTC and 16:00 UTC the GraphQL API service was degraded and customers in  saw higher than normal timeouts. On average, the timeout rate was 0.06% and peaked at 0.14% of requests routing to the service. <br /><br />This was due to increased utilization at one of our sites which caused resource contention across our dependencies, leading to an increase in timeouts for GraphQL requests. We mitigated the incident by increasing capacity to alleviate the capacity bottleneck.  <br /><br />We are working to improve our monitoring so that we can proactively reduce the impact of high consumption requests in addition to scaling up; Additionally, we will improve our time to detection and mitigation of issues like this one in the future.\n[2026-08-11 20:06:50 UTC] GitHub SRE (Monitoring): 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.\n[2026-08-11 16:49:34 UTC] GitHub SRE (Monitoring): The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.\n[2026-08-11 16:49:24 UTC] GitHub SRE (Investigating): 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.\n[2026-08-11 15:28:44 UTC] GitHub SRE (Investigating): 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\n[2026-08-11 14:50:40 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for API Requests", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 11, 2026, between 14:00 UTC and 16:00 UTC the GraphQL API service was degraded and customers in  saw higher than normal timeouts. On average, the timeout rate was 0.06% and peaked at 0.14% of requests routing to the service. <br /><br />This was due to increased utilization at one of our sites which caused resource contention across our dependencies, leading to an increase in timeouts for GraphQL requests. We mitigated the incident by i", "breaking_config_code": "# Incident architectural state during Incident with GraphQL API Requests\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"API Requests\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API Requests cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/3xn46bst0bjh", "metadata": {"raw_id": "vm1w8zq95wkt", "status": "resolved", "resolved_at": "2026-08-11T20:06:56.575Z"}}
{"incident_id": "INC-2026-GITHUB-1t7x65n7", "company": "GitHub", "date": "2026-08-10", "title": "Disruption with Copilot for access to some models", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-10 21:50:43 UTC] GitHub SRE (Resolved): On August 10, 2026, between 19:48 UTC and 20:49 UTC, GitHub Copilot users saw an incomplete list of available models. During this window, the service could return as few as one model instead of the full catalog. Requests that tried to use a model missing from that shortened list failed with a \"model not found\" error. Copilot requests that used an available model were not affected. This did not affect customers on data-residency (Proxima) environments.<br /><br />The issue was caused by a change to how model data was published, which our systems could not read back correctly and fell back to a limited default list.<br /><br />We mitigated the incident by 20:49 UTC and deployed a fix to prevent immediate recurrence by 21:50 UTC. We are adding validation and retry safeguards so that model data is verified before it is served.<br /><br />We apologize for the disruption.\n[2026-08-10 21:50:40 UTC] GitHub SRE (Monitoring): 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.\n[2026-08-10 21:19:06 UTC] GitHub SRE (Monitoring): 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.\n[2026-08-10 20:49:46 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-08-10 20:39:11 UTC] GitHub SRE (Monitoring): 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.\n[2026-08-10 20:27:19 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 10, 2026, between 19:48 UTC and 20:49 UTC, GitHub Copilot users saw an incomplete list of available models. During this window, the service could return as few as one model instead of the full catalog. Requests that tried to use a model missing from that shortened list failed with a \"model not found\" error. Copilot requests that used an available model were not affected. This did not affect customers on data-residency (Proxima) environm", "breaking_config_code": "# Incident architectural state during Disruption with Copilot for access to some models\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4x5bd0ghzy0x", "metadata": {"raw_id": "1t7x65n7kvt1", "status": "resolved", "resolved_at": "2026-08-10T21:50:43.756Z"}}
{"incident_id": "INC-2026-GITHUB-s19bth7w", "company": "GitHub", "date": "2026-08-10", "title": "Disruption with creation of fine grained personal access tokens", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-08-10 18:46:22 UTC] GitHub SRE (Resolved): On August 10, 2026, between 17:16 and 18:21 UTC, users were unable to create new fine-grained personal access tokens (FG PAT) through the GitHub website. When a user submitted the FG PAT creation form, they were returned to the FG PAT list without an error message and no FG PAT was created. Creating classic personal access tokens, as well as editing or deleting existing FG PAT were not affected.<br /><br />The cause was a change to how the website loads certain front-end JavaScript that was enabled for all users at 17:15 UTC; the change interacted with an issue in the token creation form's confirmation step that prevented it from running, so the final submission that actually creates the token never completed. Because the page still loaded and the server returned a normal response, the failure produced no error message. GitHub mitigated the incident by disabling the change at 18:21 UTC, at which point token creation recovered immediately, and the incident was resolved at 18:46 UTC.<br /><br />To reduce the chance of recurrence, GitHub is adding monitoring and alerting for anomalies in the FG PAT creation success rate and is removing the issue in the FG PAT creation form that prevented the confirmation step from running. GitHub is also adding automated detection of the issue so other areas of the GitHub front end do not repeat the problem.\n[2026-08-10 18:22:18 UTC] GitHub SRE (Monitoring): 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.\n[2026-08-10 18:21:41 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-08-10 18:09:36 UTC] GitHub SRE (Investigating): 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.\n[2026-08-10 18:02:04 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 10, 2026, between 17:16 and 18:21 UTC, users were unable to create new fine-grained personal access tokens (FG PAT) through the GitHub website. When a user submitted the FG PAT creation form, they were returned to the FG PAT list without an error message and no FG PAT was created. Creating classic personal access tokens, as well as editing or deleting existing FG PAT were not affected.<br /><br />The cause was a change to how the websit", "breaking_config_code": "# Incident architectural state during Disruption with creation of fine grained personal access tokens\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/tjf46x5zq25c", "metadata": {"raw_id": "s19bth7wzkf7", "status": "resolved", "resolved_at": "2026-08-10T18:46:22.280Z"}}
{"incident_id": "INC-2026-GITHUB-qcvjkzcs", "company": "GitHub", "date": "2026-08-06", "title": "Incident with Actions", "severity": "CRITICAL", "service_stack": ["Actions", "Pages", "GitHub Actions", "Git"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-07 02:04:44 UTC] GitHub SRE (Resolved): On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were affected. At peak, 71% of workflow runs experienced infrastructure failures and 75% of the remaining workflow runs were delayed by more than 5 minutes. <br /><br />The incident was triggered by a routine deployment to an internal Actions service responsible for processing events and generating Actions jobs. The deployment exposed an existing capacity and concurrency weakness. As pods were replaced during the deployment, remaining capacity became saturated, causing services to crash and triggering a cascading impact across multiple clusters and downstream services. <br /><br />These services recovered at 17:00 after expanding capacity, throttling incoming webhook-triggered work to allow the system to recover, and increasing processing capacity for the backlog of affected events. <br /><br />As the incident progressed, a backlog of work accumulated across the systems responsible for assigning jobs to runners. Due to a latent bug in one of the services responsible for job assignment, runners were getting assigned jobs that were no longer valid and then getting stuck retrying those jobs, preventing them from picking up valid work. <br /><br />This second stage of impact was mitigated by deploying changes to prevent runners from repeatedly attempting to acquire invalid jobs. These mitigations allowed the accumulated queues to drain and Actions to recover to normal operation. <br /><br />Some Actions Runner Controller (ARC) runners remained stuck after the incident. A mitigation deployed during the incident inadvertently affected these runners, causing some to remain offline until they were manually recovered. We subsequently rolled back the change and are adding automatic recovery in upcoming Runner and ARC releases. <br /><br />Some jobs created during the incident were also left stuck unable to be retried or canceled.  CLI and UI solutions for customers to address these were shared at https://github.com/orgs/community/discussions/204152#discussioncomment-17946043. <br /><br />To prevent recurrence, we are making improvements to deployment and capacity safeguards for the affected services, strengthening monitoring for the conditions that preceded the incident, improving the resiliency and recovery of queued work and runner assignment, and adding automatic recovery for self-hosted runners affected by similar failure conditions. We are also making additional improvements to reduce the risk of cascading failures and accelerate recovery during large-scale Actions disruptions.\n[2026-08-07 02:03:41 UTC] GitHub SRE (Monitoring): During the incident, some Actions Runner Controller (ARC) runner pods became stuck in an idle state. Affected users can delete those pods using kubectl or redeploy their Actions Runner Controller application. ARC will automatically create replacement runners.<br /><br />The next releases of Actions Runner and Actions Runner Controller will include an automatic recovery mechanism, preventing the need for these manual steps in the future.<br /><br />Some workflow-triggering events, including push and pull request events, were not processed during the incident and cannot be replayed automatically. Customers may need to repeat the triggering action by pushing a new commit, updating the pull request, or manually re-running the workflow where applicable.\n[2026-08-07 00:59:01 UTC] GitHub SRE (Monitoring): We’re investigating reports that some Actions Runner Controller runners are taking longer than expected to recover. We’ll provide an update as our investigation progresses.\n[2026-08-07 00:06:24 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-08-07 00:05:05 UTC] GitHub SRE (Investigating): The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.\n[2026-08-07 00:01:26 UTC] GitHub SRE (Investigating): System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.<br /><br />Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.<br /><br />We are monitoring all affected services for sustained recovery and will provide another update shortly.\n[2026-08-07 00:01:15 UTC] GitHub SRE (Investigating): <br />System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.<br /><br />Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.<br /><br />We are monitoring all affected services for sustained recovery and will provide another update shortly.\n[2026-08-06 23:13:30 UTC] GitHub SRE (Investigating): We have deployed fixes that address runners being assigned invalid jobs and are taking additional steps to clear the backlog of affected jobs. Job completion rates for running workflows have improved significantly, with success rates now at 99%. Global queues for hosted runner assignment are nearly burned down and concurrency queues for customers are being processed. Another change was deployed to accelerate processing the backlog of job requests.<br /><br />We are gradually restoring throughput for webhook-triggered Actions workflows and monitoring system stability. We have deployed a fix for self-hosted runners that were not picking up jobs and are enabling it incrementally.<br /><br />GitHub Pages, Copilot code review, and Copilot coding agent may still experience intermittent failures or delays. Migrations using GitHub Enterprise Importer remain paused.<br /><br />We continue to monitor recovery across all affected services and will provide another update as conditions improve.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were affected. At peak, 71% of workflow runs experienced infrastructure failures and 75% of the remaining workflow runs were delayed by more than 5 minutes. <br /><br />The incident wa", "breaking_config_code": "# Incident architectural state during Incident with Actions\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Actions\", \"Pages\", \"GitHub Actions\", \"Git\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rcz3fcm83sff", "metadata": {"raw_id": "qcvjkzcs7j74", "status": "resolved", "resolved_at": "2026-08-07T02:04:44.460Z"}}
{"incident_id": "INC-2026-GITHUB-1xqvzyv9", "company": "GitHub", "date": "2026-08-06", "title": "Incident with Pages - Deployment Lag", "severity": "MEDIUM", "service_stack": ["Pages", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-06 16:22:59 UTC] GitHub SRE (Resolved): On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased. <br /><br />At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing status deployment processing to lower the load on our Redis cluster. Latency returned to normal levels at 15:40 UTC. <br /><br />Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments. <br /><br />We have updated our alerts to detect elevated processing latency sooner and to notify us immediately when latency causes deployment processing failures. We've confirmed this incident was not fully captured by our availability metrics. In the coming days, we'll update how GitHub Pages availability is measured so incidents like this are accurately reflected going forward.\n[2026-08-06 15:50:51 UTC] GitHub SRE (Monitoring): The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.\n[2026-08-06 15:03:55 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Pages", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased. <br /><br />At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing stat", "breaking_config_code": "# Incident architectural state during Incident with Pages - Deployment Lag\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Pages\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Pages cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/b0n00sx9z3ht", "metadata": {"raw_id": "1xqvzyv99skw", "status": "resolved", "resolved_at": "2026-08-06T16:22:59.638Z"}}
{"incident_id": "INC-2026-GITHUB-9wzhl5jr", "company": "GitHub", "date": "2026-08-05", "title": "Some Copilot Cloud Agent jobs not starting", "severity": "MEDIUM", "service_stack": ["GitHub Actions", "Git", "REST API", "Webhooks"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-08-05 13:00:25 UTC] GitHub SRE (Resolved): On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadly than intended delaying more traffic than expected. <br /> <br />The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic. <br /> <br />We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future.\n[2026-08-05 12:10:46 UTC] GitHub SRE (Monitoring): Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.\n[2026-08-05 12:01:29 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We are monitoring to ensure stability.\n[2026-08-05 11:38:57 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services.", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadl", "breaking_config_code": "# Incident architectural state during Some Copilot Cloud Agent jobs not starting\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"GitHub Actions\", \"Git\", \"REST API\", \"Webhooks\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on GitHub Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/kxdh3hfxm3zl", "metadata": {"raw_id": "9wzhl5jr80jt", "status": "resolved", "resolved_at": "2026-08-05T13:00:25.857Z"}}
{"incident_id": "INC-2026-GITHUB-7s119p1y", "company": "GitHub", "date": "2026-08-03", "title": "Incident with Copilot", "severity": "MEDIUM", "service_stack": ["Copilot", "GitHub Actions", "Git", "REST API"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-08-03 11:25:12 UTC] GitHub SRE (Resolved): On 2026-08-03, between 06:52 and 11:25 UTC, some GitHub Copilot users experienced errors when using chat and agent features. Requests to list the available models failed, and because every chat or agent interaction begins by retrieving the list of models, affected users saw their requests fail. On average about 3% of these model-listing requests failed during the incident (roughly 97% succeeded), but failures were significantly higher during peak-traffic periods, at times approaching 100% for the affected internal lookups. Approximately 4,066 users were affected in a single 60-minute window, concentrated among IDE-based clients. The underlying AI models themselves remained healthy throughout.<br /><br />The incident was caused by an increase in how often clients requested the model list, which pushed an internal user-authorization lookup past a rate limit; the rate-limited responses were surfaced to users as errors. We mitigated the impact by increasing how long Copilot caches that authorization lookup, which reduced load on the internal service, and we have additional capacity and rate-limit changes in progress. To prevent recurrence we are improving monitoring for this class of failure, adjusting cache and rate-limit settings, and coordinating with client teams on request patterns.\n[2026-08-03 11:19:04 UTC] GitHub SRE (Monitoring): The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.\n[2026-08-03 10:35:19 UTC] GitHub SRE (Investigating): We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations.\n[2026-08-03 09:54:22 UTC] GitHub SRE (Investigating): 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.\n[2026-08-03 09:53:27 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On 2026-08-03, between 06:52 and 11:25 UTC, some GitHub Copilot users experienced errors when using chat and agent features. Requests to list the available models failed, and because every chat or agent interaction begins by retrieving the list of models, affected users saw their requests fail. On average about 3% of these model-listing requests failed during the incident (roughly 97% succeeded), but failures were significantly higher during peak", "breaking_config_code": "# Incident architectural state during Incident with Copilot\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/y3tm8v1gmn85", "metadata": {"raw_id": "7s119p1yxttr", "status": "resolved", "resolved_at": "2026-08-03T11:25:12.371Z"}}
{"incident_id": "INC-2026-GITHUB-sj1tzyrx", "company": "GitHub", "date": "2026-08-01", "title": "Incident with Copilot AI Model Providers", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-08-01 18:44:28 UTC] GitHub SRE (Resolved): On August 1, 2026, between 17:47 UTC and 18:20 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.007%, while failures for Fable 5 peaked at 5.6%. Other models remained available. This was caused by degradation of an upstream model provider.<br /><br />The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future.\n[2026-08-01 18:23:40 UTC] GitHub SRE (Monitoring): The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces.<br /><br />We will continue monitoring to ensure stability, but mitigation is complete.\n[2026-08-01 18:20:48 UTC] GitHub SRE (Monitoring): The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.\n[2026-08-01 18:20:20 UTC] GitHub SRE (Investigating): 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.\n[2026-08-01 18:03:15 UTC] GitHub SRE (Investigating): We are seeing increased error rates from specific upstream AI Model Providers\n[2026-08-01 18:03:05 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 1, 2026, between 17:47 UTC and 18:20 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.007%, while failures for Fable 5 peaked at 5.6%. Other models remained available. This was caused by degradation of an upstream model provider.<br /><br />The affected endpoint recovered, and we monitored the service until error rates and lat", "breaking_config_code": "# Incident architectural state during Incident with Copilot AI Model Providers\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/z58g1g529hzz", "metadata": {"raw_id": "sj1tzyrx599x", "status": "resolved", "resolved_at": "2026-08-01T18:44:28.733Z"}}
{"incident_id": "INC-2026-GITHUB-kk183dsl", "company": "GitHub", "date": "2026-08-01", "title": "Degraded availability GPT 5.6 Luna", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-08-01 12:30:21 UTC] GitHub SRE (Resolved): On August 1st, 2026, the GPT-5.6 Luna model in GitHub Copilot experienced degraded availability in intermittent time intervals between ~08:05 UTC and ~16:30 UTC. Specifically the timeframes observed were 10:00-10:20 UTC, 10:45-11:50 UTC, 13:00-14:25 UTC, and 16:00-16:30 UTC. During this time, requests to GPT-5.6 Luna in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for GPT-5.6 Luna fully recovered once the provider resolved their outage at 16:30 UTC.\n[2026-08-01 12:29:20 UTC] GitHub SRE (Investigating): 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.<br />We will continue monitoring to ensure stability, but mitigation is complete.\n[2026-08-01 12:13:24 UTC] GitHub SRE (Investigating): We keep working with our upstream model provider, and are observing recovery. We continue monitoring to ensure stability.\n[2026-08-01 11:20:02 UTC] GitHub SRE (Investigating): 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\n[2026-08-01 11:16:25 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On August 1st, 2026, the GPT-5.6 Luna model in GitHub Copilot experienced degraded availability in intermittent time intervals between ~08:05 UTC and ~16:30 UTC. Specifically the timeframes observed were 10:00-10:20 UTC, 10:45-11:50 UTC, 13:00-14:25 UTC, and 16:00-16:30 UTC. During this time, requests to GPT-5.6 Luna in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other", "breaking_config_code": "# Incident architectural state during Degraded availability GPT 5.6 Luna\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/pj5lgggbc2rb", "metadata": {"raw_id": "kk183dslzdzd", "status": "resolved", "resolved_at": "2026-08-01T12:30:21.775Z"}}
{"incident_id": "INC-2026-GITHUB-9tpgqq1h", "company": "GitHub", "date": "2026-07-30", "title": "Copilot model Claude Fable 5 experiencing elevated errors", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-30 10:12:15 UTC] GitHub SRE (Resolved): On July 30, 2026, the Claude Fable 5 model in GitHub Copilot experienced degraded availability for approximately 73 minutes, from 08:33 to 09:46 UTC. During this time, requests to Claude Fable 5 in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for Claude Fable 5 fully recovered once the provider resolved their outage at 09:46 UTC, and we confirmed resolution at 10:12 UTC.\n[2026-07-30 10:11:55 UTC] GitHub SRE (Investigating): The issues with our upstream model provider have been resolved, and Claude Fable 5 is once again available in Copilot products and IDE surfaces.<br /><br />We will continue monitoring to ensure stability, but mitigation is complete.\n[2026-07-30 09:17:26 UTC] GitHub SRE (Investigating): 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.\n[2026-07-30 09:07:42 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On July 30, 2026, the Claude Fable 5 model in GitHub Copilot experienced degraded availability for approximately 73 minutes, from 08:33 to 09:46 UTC. During this time, requests to Claude Fable 5 in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for C", "breaking_config_code": "# Incident architectural state during Copilot model Claude Fable 5 experiencing elevated errors\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/45g8r57kv3n9", "metadata": {"raw_id": "9tpgqq1h4bs7", "status": "resolved", "resolved_at": "2026-07-30T10:12:15.489Z"}}
{"incident_id": "INC-2026-GITHUB-dsrfymph", "company": "GitHub", "date": "2026-07-29", "title": "Incident with Copilot AI Model Providers", "severity": "MEDIUM", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-07-29 21:51:26 UTC] GitHub SRE (Resolved): On July 29, 2026, between 19:45 UTC and 21:51 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.006%, while failures for Fable 5 peaked at 21%. Other models remained available. This was caused by degradation of an upstream model provider.<br /><br />The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future.\n[2026-07-29 21:51:15 UTC] GitHub SRE (Investigating): The external ai model provider has resolved the issues, and we have verified Copilot's traffic is fully recovered.\n[2026-07-29 21:08:31 UTC] GitHub SRE (Investigating): The external AI model provider is continuing to investigate.\n[2026-07-29 20:38:32 UTC] GitHub SRE (Investigating): The external AI model provider has identified the issue and is working to resolve.\n[2026-07-29 20:18:18 UTC] GitHub SRE (Investigating): We are investigating increased error rates affecting GitHub Copilot requests to external AI model providers. Some users may experience failures or degraded performance when using Copilot features.\n[2026-07-29 20:07:43 UTC] GitHub SRE (Investigating): We are seeing increased error rates with requests to specific model providers.\n[2026-07-29 20:07:08 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On July 29, 2026, between 19:45 UTC and 21:51 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.006%, while failures for Fable 5 peaked at 21%. Other models remained available. This was caused by degradation of an upstream model provider.<br /><br />The affected endpoint recovered, and we monitored the service until error rates and laten", "breaking_config_code": "# Incident architectural state during Incident with Copilot AI Model Providers\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/tdw1hjz3lj91", "metadata": {"raw_id": "dsrfymph7my0", "status": "resolved", "resolved_at": "2026-07-29T21:51:26.803Z"}}
{"incident_id": "INC-2026-GITHUB-75g5xmzp", "company": "GitHub", "date": "2026-07-29", "title": "Incident with Actions", "severity": "HIGH", "service_stack": ["Actions", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-29 16:00:54 UTC] GitHub SRE (Resolved): On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts. <br /><br />The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future.\n[2026-07-29 15:40:35 UTC] GitHub SRE (Monitoring): The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.\n[2026-07-29 15:34:07 UTC] GitHub SRE (Investigating): We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure.\n[2026-07-29 15:26:24 UTC] GitHub SRE (Investigating): We are investigating reports of degraded availability for Actions", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait ", "breaking_config_code": "# Incident architectural state during Incident with Actions\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Actions\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8nsh6820sff9", "metadata": {"raw_id": "75g5xmzptjqb", "status": "resolved", "resolved_at": "2026-07-29T16:00:54.006Z"}}
{"incident_id": "INC-2026-GITHUB-fmmsrcg5", "company": "GitHub", "date": "2026-07-27", "title": "Incident with GraphQL API Requests", "severity": "MEDIUM", "service_stack": ["API Requests", "GitHub Actions", "Git", "REST API"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-07-27 04:09:10 UTC] GitHub SRE (Resolved): On July 26, 2026 at 21:34 UTC we began seeing intermittent errors on the GitHub GraphQL API. A subset of GraphQL API requests returned HTTP 502 errors in short bursts. During the impact window an average of 0.09% of GraphQL API requests in the affected region failed, with a peak of 0.50% of requests failing during the worst two-minute period at 03:02 UTC on July 27. Requests that failed generally succeeded when retried, and no data was lost or altered. Other GitHub services were not affected.<br /><br />The errors were traced to a single group of servers handling a share of GraphQL API traffic. Application processes on that group intermittently closed connections before completing responses. Impact ended at 03:52 UTC on July 27 when those processes were replaced, and we resolved the incident at 04:09 UTC on July 27 after confirming error rates had returned to normal.<br /><br />We are still investigating why those processes closed connections, and that work is being carried out by the team that owns the underlying compute platform. In the meantime we are adding detection and automated mitigation for when a single group of servers behaves differently from its peers.\n[2026-07-27 04:09:01 UTC] GitHub SRE (Monitoring): The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.\n[2026-07-27 03:53:19 UTC] GitHub SRE (Investigating): We are investigating reports of degraded performance for API Requests", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On July 26, 2026 at 21:34 UTC we began seeing intermittent errors on the GitHub GraphQL API. A subset of GraphQL API requests returned HTTP 502 errors in short bursts. During the impact window an average of 0.09% of GraphQL API requests in the affected region failed, with a peak of 0.50% of requests failing during the worst two-minute period at 03:02 UTC on July 27. Requests that failed generally succeeded when retried, and no data was lost or al", "breaking_config_code": "# Incident architectural state during Incident with GraphQL API Requests\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"API Requests\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API Requests cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/vr201n49yl53", "metadata": {"raw_id": "fmmsrcg5x638", "status": "resolved", "resolved_at": "2026-07-27T04:09:10.590Z"}}
{"incident_id": "INC-2026-GITHUB-pz7g535g", "company": "GitHub", "date": "2026-07-25", "title": "Actions run failures and delays", "severity": "CRITICAL", "service_stack": ["Actions", "GitHub Actions", "Git", "REST API"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-25 13:13:21 UTC] GitHub SRE (Resolved): Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/s65j9gslmfm8\n[2026-07-25 13:12:41 UTC] GitHub SRE (Monitoring): 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.\n[2026-07-25 12:59:58 UTC] GitHub SRE (Monitoring): The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.\n[2026-07-25 12:58:32 UTC] GitHub SRE (Investigating): 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.\n[2026-07-25 12:34:26 UTC] GitHub SRE (Investigating): 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.\n[2026-07-25 12:31:51 UTC] GitHub SRE (Investigating): We are investigating reports of degraded availability for Actions", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/s65j9gslmfm8 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. The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. We have applied a miti", "breaking_config_code": "# Incident architectural state during Actions run failures and delays\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Actions\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Actions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/448g37mrq066", "metadata": {"raw_id": "pz7g535gbs6p", "status": "resolved", "resolved_at": "2026-07-25T13:13:21.503Z"}}
{"incident_id": "INC-2026-GITHUB-vv9vvksm", "company": "GitHub", "date": "2026-07-25", "title": "Several GPT models degraded", "severity": "HIGH", "service_stack": ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-25 10:11:16 UTC] GitHub SRE (Resolved): On July 25, 2026, between 09:07 and 10:04 UTC, 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 experienced degraded availability in GitHub Copilot products and IDE surfaces. Requests to these models had an average failure rate of 5.6%. Other Copilot models remained available as alternatives.<br /><br />The degradation was caused by an issue with an upstream model provider. Success rates returned to normal after the upstream issue was mitigated, and we continued monitoring before resolving the incident. We are working on improving the automated failover for the affected models to prevent similar incidents in the future.\n[2026-07-25 10:04:39 UTC] GitHub SRE (Monitoring): The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.\n[2026-07-25 09:48:30 UTC] GitHub SRE (Investigating): 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.\n[2026-07-25 09:42:28 UTC] GitHub SRE (Investigating): We are investigating reports of degraded availability for Copilot AI Model Providers", "root_cause_analysis": "Official investigation timeline recorded by GitHub engineering: On July 25, 2026, between 09:07 and 10:04 UTC, 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 experienced degraded availability in GitHub Copilot products and IDE surfaces. Requests to these models had an average failure rate of 5.6%. Other Copilot models remained available as alternatives.<br /><br />The degradation was caused by an issue with an upstream model provider. Success rates return", "breaking_config_code": "# Incident architectural state during Several GPT models degraded\nservice_cluster:\n  provider: \"GitHub\"\n  impacted_components: [\"Copilot AI Model Providers\", \"GitHub Actions\", \"Git\", \"REST API\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by GitHub SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Copilot AI Model Providers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/vh0xxw69dr6v", "metadata": {"raw_id": "vv9vvksmj4s9", "status": "resolved", "resolved_at": "2026-07-25T10:11:16.738Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-q2bck6r3", "company": "Cloudflare", "date": "2026-10-03", "title": "Issues with Workers Build failing to start", "severity": "MEDIUM", "service_stack": ["Workers Builds", "Cloudflare Edge", "DNS", "WAF"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-10-05 07:28:10 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-10-03 08:54:50 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-10-03 05:54:59 UTC] Cloudflare SRE (Investigating): Cloudflare is aware of and investigating an issue with Cloudflare Workers build failing to start. We are working to analyse and mitigate this problem. More updates to follow shortly.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare is aware of and investigating an issue with Cloudflare Workers build failing to start. We are working to analyse and mitigate this problem. More updates to follow shortly.", "breaking_config_code": "# Incident architectural state during Issues with Workers Build failing to start\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Workers Builds\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Workers Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/q2bck6r39bzk", "metadata": {"raw_id": "q2bck6r39bzk", "status": "resolved", "resolved_at": "2026-10-05T07:28:10.019Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-2xnmsnv8", "company": "Cloudflare", "date": "2026-10-02", "title": "Cloudflare CDN experiencing increase in errors.", "severity": "CRITICAL", "service_stack": ["CDN/Cache", "CDN Cache Purge", "Cloudflare Edge", "DNS"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-10-02 21:57:57 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-10-02 21:46:34 UTC] Cloudflare SRE (Monitoring): Cloudflare is investigating an increase in errors for CDN configuration changes and purge calls specifically issued from the dashboard. Purges sent via API were unaffected. CDN configuration changes across the dashboard, API and others saw impact.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. Cloudflare is investigating an increase in errors for CDN configuration changes and purge calls specifically issued from the dashboard. Purges sent via API were unaffected. CDN configuration changes across the dashboard, API and others saw impact.", "breaking_config_code": "# Incident architectural state during Cloudflare CDN experiencing increase in errors.\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"CDN/Cache\", \"CDN Cache Purge\", \"Cloudflare Edge\", \"DNS\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on CDN/Cache cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/2xnmsnv8yv5x", "metadata": {"raw_id": "2xnmsnv8yv5x", "status": "resolved", "resolved_at": "2026-10-02T21:57:57.692Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-0kj5cjjq", "company": "Cloudflare", "date": "2026-10-02", "title": "Network Performance Issues - Seoul (ICN)", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-10-02 22:33:54 UTC] Cloudflare SRE (Resolved): Between 17:11 and 17:22 UTC, Cloudflare experienced network performance degradation impacting Seoul, South Korea (ICN).\nThe issue has been identified and fully mitigated, and network performance has returned to normal levels.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Between 17:11 and 17:22 UTC, Cloudflare experienced network performance degradation impacting Seoul, South Korea (ICN).\nThe issue has been identified and fully mitigated, and network performance has returned to normal levels.", "breaking_config_code": "# Incident architectural state during Network Performance Issues - Seoul (ICN)\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/0kj5cjjq93xn", "metadata": {"raw_id": "0kj5cjjq93xn", "status": "resolved", "resolved_at": "2026-10-02T16:00:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-fs7dz54l", "company": "Cloudflare", "date": "2026-09-30", "title": "Network Performance Issues in Madrid", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-10-02 05:42:29 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-30 14:06:40 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-30 11:31:16 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-30 10:31:12 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating issues with network performance in Madrid (MAD). \nWe are working to analyse and mitigate this problem. More updates to follow shortly.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. Cloudflare is investigating issues with network performance in Madrid (MAD). \nWe are working to analyse and mitigate this problem. More updates to follow shortly.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in Madrid\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/fs7dz54l226c", "metadata": {"raw_id": "fs7dz54l226c", "status": "resolved", "resolved_at": "2026-10-02T05:42:29.851Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-4m03612l", "company": "Cloudflare", "date": "2026-09-30", "title": "Cloudflare Workers build delays", "severity": "MEDIUM", "service_stack": ["Workers Builds", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-10-01 21:27:12 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-30 17:42:28 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-30 15:33:06 UTC] Cloudflare SRE (Investigating): Cloudflare is aware of and investigating an issue with Cloudflare Workers build delays which potentially impacts multiple customers. Further detail will be provided as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare is aware of and investigating an issue with Cloudflare Workers build delays which potentially impacts multiple customers. Further detail will be provided as more information becomes available.", "breaking_config_code": "# Incident architectural state during Cloudflare Workers build delays\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Workers Builds\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Workers Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/4m03612lprhr", "metadata": {"raw_id": "4m03612lprhr", "status": "resolved", "resolved_at": "2026-10-01T21:27:12.818Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-hyv5p7wn", "company": "Cloudflare", "date": "2026-10-01", "title": "Increased Errors for Durable Objects and R2", "severity": "MEDIUM", "service_stack": ["Durable Objects", "R2", "Cloudflare Edge", "DNS"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-10-01 21:18:42 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-10-01 21:06:14 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-10-01 20:59:56 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating issues causing an increase of errors for Durable Objects and R2 as a result in Amsterdam. We are working to analyse and mitigate this problem. More updates to follow shortly.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare is investigating issues causing an increase of errors for Durable Objects and R2 as a result in Amsterdam. We are working to analyse and mitigate this problem. More updates to follow shortly.", "breaking_config_code": "# Incident architectural state during Increased Errors for Durable Objects and R2\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Durable Objects\", \"R2\", \"Cloudflare Edge\", \"DNS\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Durable Objects cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/hyv5p7wn1c8v", "metadata": {"raw_id": "hyv5p7wn1c8v", "status": "resolved", "resolved_at": "2026-10-01T21:18:42.733Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-4c842mwy", "company": "Cloudflare", "date": "2026-10-01", "title": "Intermittent network connectivity issues in Mumbai", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-10-01 22:52:25 UTC] Cloudflare SRE (Resolved): Cloudflare had intermittent network connectivity issues between 19:45-22:13UTC on October 1st 2026 in Mumbai. This is resolved now.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare had intermittent network connectivity issues between 19:45-22:13UTC on October 1st 2026 in Mumbai. This is resolved now.", "breaking_config_code": "# Incident architectural state during Intermittent network connectivity issues in Mumbai\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/4c842mwy6z4l", "metadata": {"raw_id": "4c842mwy6z4l", "status": "resolved", "resolved_at": "2026-10-01T19:30:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-n2645m15", "company": "Cloudflare", "date": "2026-10-01", "title": "Network Performance Issues in Columbus colo in Ohio", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-10-01 16:14:32 UTC] Cloudflare SRE (Resolved): Cloudflare observed network performance issues between 15:30-15:40UTC on October 1st 2026 in Columbus, Ohio(CMH) . The issue is resolved as of now.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare observed network performance issues between 15:30-15:40UTC on October 1st 2026 in Columbus, Ohio(CMH) . The issue is resolved as of now.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in Columbus colo in Ohio\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/n2645m15vwc9", "metadata": {"raw_id": "n2645m15vwc9", "status": "resolved", "resolved_at": "2026-10-01T15:30:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-mq69fw5y", "company": "Cloudflare", "date": "2026-09-30", "title": "Network Performance Issues in Los Angeles (LAX)", "severity": "MEDIUM", "service_stack": ["Containers", "Durable Objects", "Hyperdrive", "R2"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-30 19:18:41 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-30 14:39:04 UTC] Cloudflare SRE (Investigating): We are continuing to investigate this issue.\n[2026-09-30 13:49:25 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating possible network congestion in Los Angeles (LAX) affecting Vectorize, Durable Objects, R2, Hyperdrive, Stream, and Cloudchamber. We are working to mitigate the impact to Internet users in the region.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. We are continuing to investigate this issue. Cloudflare is investigating possible network congestion in Los Angeles (LAX) affecting Vectorize, Durable Objects, R2, Hyperdrive, Stream, and Cloudchamber. We are working to mitigate the impact to Internet users in the region.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in Los Angeles (LAX)\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Containers\", \"Durable Objects\", \"Hyperdrive\", \"R2\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Containers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/mq69fw5ykdwb", "metadata": {"raw_id": "mq69fw5ykdwb", "status": "resolved", "resolved_at": "2026-09-30T19:18:41.309Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-2h896759", "company": "Cloudflare", "date": "2026-09-30", "title": "Membership Permission Change Delays", "severity": "MEDIUM", "service_stack": ["API", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-30 18:10:55 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-30 18:04:02 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-30 13:36:42 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating delays in applying changes to account member roles and permissions. Recently updated permissions may not be immediately reflected in some Cloudflare services. We are working to mitigate this issue.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare is investigating delays in applying changes to account member roles and permissions. Recently updated permissions may not be immediately reflected in some Cloudflare services. We are working to mitigate this issue.", "breaking_config_code": "# Incident architectural state during Membership Permission Change Delays\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"API\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/2h896759fg2f", "metadata": {"raw_id": "2h896759fg2f", "status": "resolved", "resolved_at": "2026-09-30T18:10:55.604Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-0dq5fbp2", "company": "Cloudflare", "date": "2026-09-30", "title": "WARP connectivity in Newark, NJ", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-30 02:26:25 UTC] Cloudflare SRE (Resolved): Between 00:45- 01:35 UTC, Cloudflare WARP and Zero Trust users in Newark, NJ, may have experienced connectivity issues or a degraded Internet experience.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Between 00:45- 01:35 UTC, Cloudflare WARP and Zero Trust users in Newark, NJ, may have experienced connectivity issues or a degraded Internet experience.", "breaking_config_code": "# Incident architectural state during WARP connectivity in Newark, NJ\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/0dq5fbp2xwbj", "metadata": {"raw_id": "0dq5fbp2xwbj", "status": "resolved", "resolved_at": "2026-09-30T00:45:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-8wmvkv5j", "company": "Cloudflare", "date": "2026-09-23", "title": "Network Performance Degradation — Asia-Pacific", "severity": "MEDIUM", "service_stack": ["Network", "Cloudflare Edge", "DNS", "WAF"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-29 23:01:27 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-25 08:50:56 UTC] Cloudflare SRE (Identified): Cloudflare continues to mitigate intermittent connectivity degradation for a small subset of customers caused by significant degradation of capacity in the region.\n[2026-09-23 18:44:55 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-23 18:42:39 UTC] Cloudflare SRE (Investigating): Since September 21, 2026 at 02:20 UTC, multiple subsea cable outages have caused congestion between Tokyo and Singapore datacenters. We have rerouted traffic to reduce impact and are working with third-party vendors to restore capacity.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. Cloudflare continues to mitigate intermittent connectivity degradation for a small subset of customers caused by significant degradation of capacity in the region. The issue has been identified and a fix is being implemented. Since September 21, 2026 at 02:20 UTC, multiple subsea cable outages have caused congestion between Tokyo and Singapore datacenters. We have rerouted traffic to reduce impact and are working ", "breaking_config_code": "# Incident architectural state during Network Performance Degradation — Asia-Pacific\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Network\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/8wmvkv5jkf15", "metadata": {"raw_id": "8wmvkv5jkf15", "status": "resolved", "resolved_at": "2026-09-29T23:01:27.182Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-vcstgt8g", "company": "Cloudflare", "date": "2026-09-29", "title": "OTP Deliverability Errors", "severity": "MEDIUM", "service_stack": ["Access", "Cloudflare Edge", "DNS", "WAF"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-09-29 20:50:35 UTC] Cloudflare SRE (Resolved): Cloudflare engineering determined that customers didn't actually experience elevated levels of OTP failures. The rise in failures was an isolated incident without widespread impact.\n[2026-09-29 20:11:20 UTC] Cloudflare SRE (Investigating): We are investigating an issue causing a high percentage of Access One Time Pin emails to fail. All other authentication methods are operating as normal.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare engineering determined that customers didn't actually experience elevated levels of OTP failures. The rise in failures was an isolated incident without widespread impact. We are investigating an issue causing a high percentage of Access One Time Pin emails to fail. All other authentication methods are operating as normal.", "breaking_config_code": "# Incident architectural state during OTP Deliverability Errors\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Access\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Access cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/vcstgt8gqkyk", "metadata": {"raw_id": "vcstgt8gqkyk", "status": "resolved", "resolved_at": "2026-09-29T20:50:35.186Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-32sg73xw", "company": "Cloudflare", "date": "2026-09-28", "title": "Network Performance Issues in Eastern North America", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-28 20:36:00 UTC] Cloudflare SRE (Resolved): Cloudflare observed issues with network performance in Eastern North America today, 2026-09-28, between approximately 19:50 and 20:20 UTC. Customers may have observed elevated error rates for traffic in this region during this period.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare observed issues with network performance in Eastern North America today, 2026-09-28, between approximately 19:50 and 20:20 UTC. Customers may have observed elevated error rates for traffic in this region during this period.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in Eastern North America\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/32sg73xwyq89", "metadata": {"raw_id": "32sg73xwyq89", "status": "resolved", "resolved_at": "2026-09-28T20:36:00.227Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-smn1d93z", "company": "Cloudflare", "date": "2026-09-28", "title": "Replicate Flux Hotswap Models Stuck", "severity": "MEDIUM", "service_stack": ["Replicate", "Cloudflare Edge", "DNS", "WAF"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-28 20:28:58 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-28 20:11:05 UTC] Cloudflare SRE (Investigating): We are investigating Flux hotswap models that haven't made progress since last Thursday, 2026-09-24.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. We are investigating Flux hotswap models that haven't made progress since last Thursday, 2026-09-24.", "breaking_config_code": "# Incident architectural state during Replicate Flux Hotswap Models Stuck\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Replicate\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Replicate cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/smn1d93zd3hr", "metadata": {"raw_id": "smn1d93zd3hr", "status": "resolved", "resolved_at": "2026-09-28T20:28:58.448Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-6m2w2ls1", "company": "Cloudflare", "date": "2026-09-26", "title": "R2 Service Issues in Western North America (WNAM)", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-26 18:06:56 UTC] Cloudflare SRE (Resolved): Between 17:13 and 17:36 UTC, an issue affected R2 buckets in the Western North America (WNAM) region. This incident has been resolved.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Between 17:13 and 17:36 UTC, an issue affected R2 buckets in the Western North America (WNAM) region. This incident has been resolved.", "breaking_config_code": "# Incident architectural state during R2 Service Issues in Western North America (WNAM)\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/6m2w2ls1gv75", "metadata": {"raw_id": "6m2w2ls1gv75", "status": "resolved", "resolved_at": "2026-09-26T16:00:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-39dzwkhz", "company": "Cloudflare", "date": "2026-09-26", "title": "Cloudflare Cloud Access Security Broker (CASB) Issues", "severity": "MEDIUM", "service_stack": ["Cloud Access Security Broker (CASB)", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-26 10:58:05 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-26 10:47:41 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-26 10:44:49 UTC] Cloudflare SRE (Investigating): We are continuing to investigate this issue.\n[2026-09-26 10:20:37 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating degraded availability impacting Cloudflare CASB and policy sharing between accounts in Cloudflare Organizations. CASB findings may be delayed, and changes to shared policies may take longer to propagate to destination accounts.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to investigate this issue. Cloudflare is investigating degraded availability impacting Cloudflare CASB and policy sharing between accounts in Cloudflare Organizations. CASB findings may be delayed, and changes to shared policies may take longer to propagate to destination accounts.", "breaking_config_code": "# Incident architectural state during Cloudflare Cloud Access Security Broker (CASB) Issues\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloud Access Security Broker (CASB)\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloud Access Security Broker (CASB) cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/39dzwkhzcvv5", "metadata": {"raw_id": "39dzwkhzcvv5", "status": "resolved", "resolved_at": "2026-09-26T10:58:05.152Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-gv29fd07", "company": "Cloudflare", "date": "2026-09-25", "title": "Issues with Durable Objects", "severity": "MEDIUM", "service_stack": ["Durable Objects", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-25 14:49:01 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-25 08:48:52 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-25 02:32:19 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating issues causing an increase of errors for Durable Objects .We are working to analyse and mitigate this problem. More updates to follow shortly.\n[2026-09-25 01:31:54 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-25 00:03:24 UTC] Cloudflare SRE (Investigating): Cloudflare is aware of and investigating an issue impacting some customers where new Workflows instances may be stuck in a Queued state. More updates to follow shortly.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare is investigating issues causing an increase of errors for Durable Objects .We are working to analyse and mitigate this problem. More updates to follow shortly. A fix has been implemented and we are monitoring the results. Cloudflare is aware of and investigating an issue impacting some customers where new Workflows instances may be stuck in a", "breaking_config_code": "# Incident architectural state during Issues with Durable Objects\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Durable Objects\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Durable Objects cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/gv29fd076q2t", "metadata": {"raw_id": "gv29fd076q2t", "status": "resolved", "resolved_at": "2026-09-25T14:49:01.414Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-drq3pdx1", "company": "Cloudflare", "date": "2026-09-25", "title": "Edit Compression Rule Issue", "severity": "MEDIUM", "service_stack": ["Rules", "Cloudflare Edge", "DNS", "WAF"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-25 06:31:10 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-25 06:26:47 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-25 05:58:40 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-25 04:58:31 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating an issue with editing rules in the Dashboard. \n\nCustomers may see errors when trying to edit or create a Compression rule. Existing Compression rules are unaffected.\n\nWe are working to understand the full impact and mitigate this problem. More updates to follow shortly.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. Cloudflare is investigating an issue with editing rules in the Dashboard. \n\nCustomers may see errors when trying to edit or create a Compression rule. Existing Compression rules are unaffected.\n\nWe are working to understand the full impact and mitigate this problem. More updates to follow sho", "breaking_config_code": "# Incident architectural state during Edit Compression Rule Issue\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Rules\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Rules cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/drq3pdx1f11y", "metadata": {"raw_id": "drq3pdx1f11y", "status": "resolved", "resolved_at": "2026-09-25T06:31:10.232Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-7dt6f0ch", "company": "Cloudflare", "date": "2026-09-25", "title": "Secondary DNS Update Delays", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-25 10:10:32 UTC] Cloudflare SRE (Resolved): Cloudflare observed and resolved delays with Secondary DNS zone transfers. Customers may have experienced delays when record updates made on primary nameservers propagate to Cloudflare Secondary DNS as well as in the other direction. DNS resolution and edge proxying remain unaffected and continue to function normally. Impact on DNS transfers may have been observed today, from 00:05:10 UTC to 01:52:54.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare observed and resolved delays with Secondary DNS zone transfers. Customers may have experienced delays when record updates made on primary nameservers propagate to Cloudflare Secondary DNS as well as in the other direction. DNS resolution and edge proxying remain unaffected and continue to function normally. Impact on DNS transfers may have been observed today, from 00:05:10 UTC to 01:52:54.", "breaking_config_code": "# Incident architectural state during Secondary DNS Update Delays\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/7dt6f0chnclh", "metadata": {"raw_id": "7dt6f0chnclh", "status": "resolved", "resolved_at": "2026-09-25T01:52:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-mltthh0j", "company": "Cloudflare", "date": "2026-09-24", "title": "Browser isolation session data sync issues", "severity": "MEDIUM", "service_stack": ["Browser Isolation", "Cloudflare Edge", "DNS", "WAF"], "categories": ["STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-09-24 22:37:13 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-24 17:28:20 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-24 17:26:03 UTC] Cloudflare SRE (Identified): Cloudflare is investigating issues with Browser Isolation's session data sync. Customers that use Browser Isolation may observe errors on acquiring a browser stating that browser storage is unavailable, and they will need to sign into web apps again. They will continue to be able to use browsers during this time.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare is investigating issues with Browser Isolation's session data sync. Customers that use Browser Isolation may observe errors on acquiring a browser stating that browser storage is unavailable, and they will need to sign into web apps again. They will continue to be able to use browsers during this time.", "breaking_config_code": "# Incident architectural state during Browser isolation session data sync issues\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Browser Isolation\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Browser Isolation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/mltthh0jxxpz", "metadata": {"raw_id": "mltthh0jxxpz", "status": "resolved", "resolved_at": "2026-09-24T22:37:13.982Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-2x4qt2q2", "company": "Cloudflare", "date": "2026-09-24", "title": "Intermittent 500 errors for backend services on Replicate", "severity": "MEDIUM", "service_stack": ["Replicate", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-24 22:34:56 UTC] Cloudflare SRE (Resolved): The impacted backend has been redeployed, and all related services should now be back up and running. There may be some increased latency as they continue to come online.\n[2026-09-24 20:40:47 UTC] Cloudflare SRE (Investigating): We have a backend component that entered an unexpected reboot, causing issues for services downstream.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: The impacted backend has been redeployed, and all related services should now be back up and running. There may be some increased latency as they continue to come online. We have a backend component that entered an unexpected reboot, causing issues for services downstream.", "breaking_config_code": "# Incident architectural state during Intermittent 500 errors for backend services on Replicate\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Replicate\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Replicate cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/2x4qt2q2ds9x", "metadata": {"raw_id": "2x4qt2q2ds9x", "status": "resolved", "resolved_at": "2026-09-24T22:34:56.071Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-dwfzz0bw", "company": "Cloudflare", "date": "2026-09-24", "title": "Delays Starting Cloudflare Workers Builds", "severity": "MEDIUM", "service_stack": ["Workers Builds", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-24 20:52:46 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-24 19:54:48 UTC] Cloudflare SRE (Monitoring): Queue levels & latency are returning to normal\n[2026-09-24 17:33:57 UTC] Cloudflare SRE (Monitoring): Customers may experience delays starting Cloudflare Workers builds.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. Queue levels & latency are returning to normal Customers may experience delays starting Cloudflare Workers builds.", "breaking_config_code": "# Incident architectural state during Delays Starting Cloudflare Workers Builds\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Workers Builds\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Workers Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/dwfzz0bwhmsq", "metadata": {"raw_id": "dwfzz0bwhmsq", "status": "resolved", "resolved_at": "2026-09-24T20:52:46.358Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-xbgbb80y", "company": "Cloudflare", "date": "2026-09-24", "title": "Cloudflare Access updates delayed", "severity": "MEDIUM", "service_stack": ["Access", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-09-24 18:25:30 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-24 15:31:57 UTC] Cloudflare SRE (Monitoring): We have applied a fix and are actively monitoring.\n[2026-09-24 15:20:39 UTC] Cloudflare SRE (Investigating): Cloudflare engineering is investigating an issue causing a delay in configuration updates. This includes applications and policy updates. Authentication and policy enforcement are not impacted.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. We have applied a fix and are actively monitoring. Cloudflare engineering is investigating an issue causing a delay in configuration updates. This includes applications and policy updates. Authentication and policy enforcement are not impacted.", "breaking_config_code": "# Incident architectural state during Cloudflare Access updates delayed\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Access\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Access cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/xbgbb80yw0jh", "metadata": {"raw_id": "xbgbb80yw0jh", "status": "resolved", "resolved_at": "2026-09-24T18:25:30.401Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-gwrzznc9", "company": "Cloudflare", "date": "2026-09-24", "title": "Customers using BYOIP can have issues updating their BGP prefixes, including advertising or withdrawing prefixes.", "severity": "MEDIUM", "service_stack": ["Bring Your Own IP (BYOIP)", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-24 10:25:52 UTC] Cloudflare SRE (Resolved): This incident has now been resolved - Customers with BYOIP addresses were unable to update their BGP prefixes, including advertising or withdrawing prefixes. Customers making changes to their address maps may also have experienced delays.\n[2026-09-24 10:22:34 UTC] Cloudflare SRE (Investigating): We are currently investigating an issue where customers with BYOIP addresses will be unable to update their BGP prefixes, including advertising or withdrawing prefixes.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has now been resolved - Customers with BYOIP addresses were unable to update their BGP prefixes, including advertising or withdrawing prefixes. Customers making changes to their address maps may also have experienced delays. We are currently investigating an issue where customers with BYOIP addresses will be unable to update their BGP prefixes, including advertising or withdrawing prefixes.", "breaking_config_code": "# Incident architectural state during Customers using BYOIP can have issues updating their BGP prefixes, including advertising or withdrawing prefixes.\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Bring Your Own IP (BYOIP)\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Bring Your Own IP (BYOIP) cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/gwrzznc9f642", "metadata": {"raw_id": "gwrzznc9f642", "status": "resolved", "resolved_at": "2026-09-24T10:25:52.106Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-jg6ys8sb", "company": "Cloudflare", "date": "2026-09-23", "title": "Intermittent authentication errors for API and R2", "severity": "MEDIUM", "service_stack": ["R2", "Cloudflare Edge", "DNS", "WAF"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-09-23 20:59:35 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-23 20:09:18 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-23 09:08:53 UTC] Cloudflare SRE (Identified): A known issue affected authentication for a small percentage of requests to the API and R2.\nThe issue was identified on Sep 22 at 13:30 UTC, and major impact was mitigated at 19:00 UTC.\nOur team is actively working to resolve the residual impact.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. A known issue affected authentication for a small percentage of requests to the API and R2.\nThe issue was identified on Sep 22 at 13:30 UTC, and major impact was mitigated at 19:00 UTC.\nOur team is actively working to resolve the residual impact.", "breaking_config_code": "# Incident architectural state during Intermittent authentication errors for API and R2\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"R2\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on R2 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/jg6ys8sbd6ny", "metadata": {"raw_id": "jg6ys8sbd6ny", "status": "resolved", "resolved_at": "2026-09-23T20:59:35.579Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-f8wg5htd", "company": "Cloudflare", "date": "2026-09-23", "title": "Elevated Errors with any / all in http_response_cache_settings", "severity": "MEDIUM", "service_stack": ["Rules", "Cloudflare Edge", "DNS", "WAF"], "categories": ["API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-23 18:08:18 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-23 15:54:28 UTC] Cloudflare SRE (Identified): We have identified an issue causing unexpected errors when creating or updating configurations using any or all expressions in the http_response_cache_settings. \nThis issue strictly affects API operations; existing active configurations and live traffic are not impacted. A fix is currently being deployed, and we will provide an update once the rollout is complete.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. We have identified an issue causing unexpected errors when creating or updating configurations using any or all expressions in the http_response_cache_settings. \nThis issue strictly affects API operations; existing active configurations and live traffic are not impacted. A fix is currently being deployed, and we will provide an update once the rollout is complete.", "breaking_config_code": "# Incident architectural state during Elevated Errors with any / all in http_response_cache_settings\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Rules\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Rules cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/f8wg5htd3zz4", "metadata": {"raw_id": "f8wg5htd3zz4", "status": "resolved", "resolved_at": "2026-09-23T18:08:18.013Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-tl0vrgjy", "company": "Cloudflare", "date": "2026-09-22", "title": "Cloudflare One Clients are incorrectly challenged on some sites", "severity": "MEDIUM", "service_stack": ["Cloudflare One Client", "Cloudflare Edge", "DNS", "WAF"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-23 11:02:41 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-22 19:23:17 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: The issue has been identified and a fix is being implemented. Cloudflare is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.", "breaking_config_code": "# Incident architectural state during Cloudflare One Clients are incorrectly challenged on some sites\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare One Client\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare One Client cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/tl0vrgjy99r0", "metadata": {"raw_id": "tl0vrgjy99r0", "status": "identified", "resolved_at": null}}
{"incident_id": "INC-2026-CLOUDFLARE-78c19w4x", "company": "Cloudflare", "date": "2026-09-23", "title": "Increased Errors for Durable Objects", "severity": "MEDIUM", "service_stack": ["Durable Objects", "Cloudflare Edge", "DNS", "WAF"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-23 10:00:09 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-23 09:20:17 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-23 08:35:32 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-23 08:09:23 UTC] Cloudflare SRE (Investigating): Cloudflare is aware of, and investigating an issue with Durable Objects which potentially impacts a subset of customers. Durable Objects are experiencing an elevated level of errors. We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. Cloudflare is aware of, and investigating an issue with Durable Objects which potentially impacts a subset of customers. Durable Objects are experiencing an elevated level of errors. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Increased Errors for Durable Objects\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Durable Objects\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Durable Objects cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/78c19w4xw4z2", "metadata": {"raw_id": "78c19w4xw4z2", "status": "resolved", "resolved_at": "2026-09-23T10:00:09.478Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-x86v1qk8", "company": "Cloudflare", "date": "2026-09-23", "title": "Elevated number of R2 503 errors in Australian Eastern Coast region", "severity": "MEDIUM", "service_stack": ["Sydney, NSW, Australia - (SYD)", "R2", "Cloudflare Edge", "DNS"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-23 04:25:51 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-23 04:22:07 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-23 04:09:54 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-23 04:08:46 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating issues with R2 buckets in the Australian Eastern Coast region.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. Cloudflare is investigating issues with R2 buckets in the Australian Eastern Coast region.", "breaking_config_code": "# Incident architectural state during Elevated number of R2 503 errors in Australian Eastern Coast region\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Sydney, NSW, Australia - (SYD)\", \"R2\", \"Cloudflare Edge\", \"DNS\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sydney, NSW, Australia - (SYD) cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/x86v1qk8yp5v", "metadata": {"raw_id": "x86v1qk8yp5v", "status": "resolved", "resolved_at": "2026-09-23T04:25:51.870Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-rcjbfb0l", "company": "Cloudflare", "date": "2026-09-23", "title": "Issues with 1.1.1.1 for Families", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-09-23 01:26:28 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-23 01:21:02 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-23 00:55:34 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-23 00:42:50 UTC] Cloudflare SRE (Investigating): Cloudflare is aware of, and investigating, an issue which impacts DNS over HTTPS requests to 1.1.1.1 for Families (1.1.1.2 and 1.1.1.3)\nAuthoritative DNS provided by Cloudflare is unaffected.\n\nFurther detail will be provided as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. Cloudflare is aware of, and investigating, an issue which impacts DNS over HTTPS requests to 1.1.1.1 for Families (1.1.1.2 and 1.1.1.3)\nAuthoritative DNS provided by Cloudflare is unaffected.\n\nFurther detail will be provided as more information becomes available.", "breaking_config_code": "# Incident architectural state during Issues with 1.1.1.1 for Families\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/rcjbfb0lyn65", "metadata": {"raw_id": "rcjbfb0lyn65", "status": "resolved", "resolved_at": "2026-09-23T01:26:28.629Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-zpkwd9fx", "company": "Cloudflare", "date": "2026-09-22", "title": "Network Performance Issues in Taipei", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-22 21:41:05 UTC] Cloudflare SRE (Resolved): Customer may have observed network performance issues for traffic handled by our Taipei (TPE) facility between approximately 19:30 and 19:35 UTC today, 2026-09-22.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Customer may have observed network performance issues for traffic handled by our Taipei (TPE) facility between approximately 19:30 and 19:35 UTC today, 2026-09-22.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in Taipei\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/zpkwd9fxsby5", "metadata": {"raw_id": "zpkwd9fxsby5", "status": "resolved", "resolved_at": "2026-09-22T21:41:05.884Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-c2f7zj7f", "company": "Cloudflare", "date": "2026-09-22", "title": "Bot Management Configuration Propagation Issues", "severity": "MEDIUM", "service_stack": ["Bot Management", "Cloudflare Edge", "DNS", "WAF"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-22 16:35:19 UTC] Cloudflare SRE (Resolved): We have identified and applied an effective fix for this issue. This incident is now resolved.\n[2026-09-22 15:31:39 UTC] Cloudflare SRE (Investigating): We are currently investigating an issue where Bot Management configuration updates are not propagating to the edge. Our engineering team is aware of the issue and is actively working on a resolution. The running Bot Configuration at the Edge is not impacted. We will provide further updates as soon as we have more information.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: We have identified and applied an effective fix for this issue. This incident is now resolved. We are currently investigating an issue where Bot Management configuration updates are not propagating to the edge. Our engineering team is aware of the issue and is actively working on a resolution. The running Bot Configuration at the Edge is not impacted. We will provide further updates as soon as we have more information.", "breaking_config_code": "# Incident architectural state during Bot Management Configuration Propagation Issues\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Bot Management\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Bot Management cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/c2f7zj7fs8l8", "metadata": {"raw_id": "c2f7zj7fs8l8", "status": "resolved", "resolved_at": "2026-09-22T16:35:19.676Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-pvvq3811", "company": "Cloudflare", "date": "2026-09-22", "title": "Elevated error rates for Stream Live LL-HLS", "severity": "MEDIUM", "service_stack": ["Stream", "Cloudflare Edge", "DNS", "WAF"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-22 15:38:50 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-22 14:44:18 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-22 14:37:45 UTC] Cloudflare SRE (Investigating): We are investigating an issue where some Stream Live customers are receiving errors when playing back live broadcasts with LL-HLS enabled.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are investigating an issue where some Stream Live customers are receiving errors when playing back live broadcasts with LL-HLS enabled.", "breaking_config_code": "# Incident architectural state during Elevated error rates for Stream Live LL-HLS\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Stream\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Stream cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/pvvq3811tpyq", "metadata": {"raw_id": "pvvq3811tpyq", "status": "resolved", "resolved_at": "2026-09-22T15:38:50.535Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-z84lp04f", "company": "Cloudflare", "date": "2026-09-22", "title": "Connectivity issues in Los Angeles (LAX)", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-22 15:22:24 UTC] Cloudflare SRE (Resolved): We investigated and resolved reports of connectivity issues in Los Angeles. Traffic congestion between in our Los Angeles (LAX) colo, which resulted in intermittent packet drops between 13:37 UTC and 14:49 UTC today. The capacity constraint has been addressed and traffic flow has returned to normal.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: We investigated and resolved reports of connectivity issues in Los Angeles. Traffic congestion between in our Los Angeles (LAX) colo, which resulted in intermittent packet drops between 13:37 UTC and 14:49 UTC today. The capacity constraint has been addressed and traffic flow has returned to normal.", "breaking_config_code": "# Incident architectural state during Connectivity issues in Los Angeles (LAX)\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/z84lp04f9sht", "metadata": {"raw_id": "z84lp04f9sht", "status": "resolved", "resolved_at": "2026-09-22T14:49:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-dcmwvjwf", "company": "Cloudflare", "date": "2026-09-22", "title": "Partial visibility of Workers and Durable Objects analytics for Fedramp High customers", "severity": "MEDIUM", "service_stack": ["Analytics", "Cloudflare Edge", "DNS", "WAF"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-22 12:51:46 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-22 10:08:10 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-22 09:36:11 UTC] Cloudflare SRE (Identified): Cloudflare is monitoring the restoration of Workers and Durable Objects analytics visibility for all Fedramp High customers. While the underlying data remains intact, affected datasets were not being correctly returned by our analytics dashboard and GraphQL API since June 11th. Services are currently recovering as we propagate the fix.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare is monitoring the restoration of Workers and Durable Objects analytics visibility for all Fedramp High customers. While the underlying data remains intact, affected datasets were not being correctly returned by our analytics dashboard and GraphQL API since June 11th. Services are currently recovering as we propagate the fix.", "breaking_config_code": "# Incident architectural state during Partial visibility of Workers and Durable Objects analytics for Fedramp High customers\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Analytics\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Analytics cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/dcmwvjwfyhjg", "metadata": {"raw_id": "dcmwvjwfyhjg", "status": "resolved", "resolved_at": "2026-09-22T12:51:46.718Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-g4vvd0xr", "company": "Cloudflare", "date": "2026-09-22", "title": "Network Performance Issues in San Jose (SJC-A)", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-22 08:34:47 UTC] Cloudflare SRE (Resolved): Cloudflare verified and resolved performance issues in our San Jose (SJC-A) data center. Users in the region may have experienced increased latency or connectivity issues between 07:20 and 08:20 UTC today.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare verified and resolved performance issues in our San Jose (SJC-A) data center. Users in the region may have experienced increased latency or connectivity issues between 07:20 and 08:20 UTC today.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in San Jose (SJC-A)\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/g4vvd0xrc2m8", "metadata": {"raw_id": "g4vvd0xrc2m8", "status": "resolved", "resolved_at": "2026-09-22T08:20:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-nhf2kr8q", "company": "Cloudflare", "date": "2026-09-22", "title": "Network connectivity issues in LHR, London", "severity": "MEDIUM", "service_stack": ["London, United Kingdom - (LHR)", "Cloudflare Edge", "DNS", "WAF"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-22 03:36:56 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-22 02:26:27 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-22 02:25:45 UTC] Cloudflare SRE (Investigating): Cloudflare is observing network connectivity issues in LHR, London. We are working to analyse and mitigate this problem. More updates to follow shortly", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. The issue has been identified and a fix is being implemented. Cloudflare is observing network connectivity issues in LHR, London. We are working to analyse and mitigate this problem. More updates to follow shortly", "breaking_config_code": "# Incident architectural state during Network connectivity issues in LHR, London\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"London, United Kingdom - (LHR)\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on London, United Kingdom - (LHR) cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/nhf2kr8q3nfw", "metadata": {"raw_id": "nhf2kr8q3nfw", "status": "resolved", "resolved_at": "2026-09-22T03:36:56.633Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-mrqb4d6q", "company": "Cloudflare", "date": "2026-09-21", "title": "Increased Cache Failures", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-21 18:15:16 UTC] Cloudflare SRE (Resolved): Cloudflare investigated an elevated rate of PUT request failures to R2 within the WNAM and ENAM regions. As a result, storing assets in Cache Reserve failed for some requests. This impact was from 15:25 - 18:00 UTC.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare investigated an elevated rate of PUT request failures to R2 within the WNAM and ENAM regions. As a result, storing assets in Cache Reserve failed for some requests. This impact was from 15:25 - 18:00 UTC.", "breaking_config_code": "# Incident architectural state during Increased Cache Failures\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/mrqb4d6q0y26", "metadata": {"raw_id": "mrqb4d6q0y26", "status": "resolved", "resolved_at": "2026-09-21T18:15:16.618Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-rxmmx07y", "company": "Cloudflare", "date": "2026-09-21", "title": "Unable to start containers in Asia-Pacific", "severity": "MEDIUM", "service_stack": ["Containers", "Cloudflare Edge", "DNS", "WAF"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-21 13:23:38 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-21 13:21:57 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-21 13:15:02 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-21 12:42:26 UTC] Cloudflare SRE (Investigating): Cloudflare is aware of problems launching containers in the Asia-Pacific Region", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. Cloudflare is aware of problems launching containers in the Asia-Pacific Region", "breaking_config_code": "# Incident architectural state during Unable to start containers in Asia-Pacific\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Containers\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Containers cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/rxmmx07ys7qg", "metadata": {"raw_id": "rxmmx07ys7qg", "status": "resolved", "resolved_at": "2026-09-21T13:23:38.015Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-lb5514cv", "company": "Cloudflare", "date": "2026-09-21", "title": "Unable to register certain domains", "severity": "MEDIUM", "service_stack": ["Registrar", "Cloudflare Edge", "DNS", "WAF"], "categories": ["PIPELINE_EXECUTION_FAILURE", "STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-09-21 09:49:13 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-21 09:37:56 UTC] Cloudflare SRE (Identified): Cloudflare is aware of an issue affecting the registration of the following top-level domains (TLDs):\n\n\"audio\", \"baby\", \"build\", \"cam\", \"ceo\", \"christmas\", \"college\", \"dealer\", \"diet\", \"fans\", \"flowers\", \"fm\", \"game\", \"guitars\", \"help\", \"hosting\", \"icu\", \"inc\", \"lol\", \"mom\", \"monster\", \"pics\", \"protection\", \"rent\", \"security\", \"storage\", \"theatre\", \"xyz\"", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. Cloudflare is aware of an issue affecting the registration of the following top-level domains (TLDs):\n\n\"audio\", \"baby\", \"build\", \"cam\", \"ceo\", \"christmas\", \"college\", \"dealer\", \"diet\", \"fans\", \"flowers\", \"fm\", \"game\", \"guitars\", \"help\", \"hosting\", \"icu\", \"inc\", \"lol\", \"mom\", \"monster\", \"pics\", \"protection\", \"rent\", \"security\", \"storage\", \"theatre\", \"xyz\"", "breaking_config_code": "# Incident architectural state during Unable to register certain domains\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Registrar\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Registrar cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/lb5514cvngd7", "metadata": {"raw_id": "lb5514cvngd7", "status": "resolved", "resolved_at": "2026-09-21T09:49:13.586Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-3rjsfq4q", "company": "Cloudflare", "date": "2026-09-19", "title": "Elevated errors in Ashburn, VA (IAD)", "severity": "MEDIUM", "service_stack": ["Network", "Cloudflare Edge", "DNS", "WAF"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-19 01:36:49 UTC] Cloudflare SRE (Resolved): Between 22:00 and 01:00 UTC on September 18, 2026, customers reaching Cloudflare's Ashburn, VA (IAD) data center may have experienced an elevated number of errors, including 499 and 522 responses, due to a network hardware issue. The issue has been resolved.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Between 22:00 and 01:00 UTC on September 18, 2026, customers reaching Cloudflare's Ashburn, VA (IAD) data center may have experienced an elevated number of errors, including 499 and 522 responses, due to a network hardware issue. The issue has been resolved.", "breaking_config_code": "# Incident architectural state during Elevated errors in Ashburn, VA (IAD)\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Network\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/3rjsfq4q663b", "metadata": {"raw_id": "3rjsfq4q663b", "status": "resolved", "resolved_at": "2026-09-19T01:36:49.241Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-3czg2lc9", "company": "Cloudflare", "date": "2026-09-18", "title": "Network Performance Issues in Ashburn", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-18 18:36:47 UTC] Cloudflare SRE (Resolved): Between 17:13-17:28UTC on 2026-09-18, Cloudflare experienced an elevated rate of 5xx HTTP errors affecting traffic passing through Ashburn (IAD). The issue has been resolved, and impact to the IAD location is mitigated.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Between 17:13-17:28UTC on 2026-09-18, Cloudflare experienced an elevated rate of 5xx HTTP errors affecting traffic passing through Ashburn (IAD). The issue has been resolved, and impact to the IAD location is mitigated.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in Ashburn\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/3czg2lc9y1t8", "metadata": {"raw_id": "3czg2lc9y1t8", "status": "resolved", "resolved_at": "2026-09-18T17:15:12.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-jds6b1j6", "company": "Cloudflare", "date": "2026-09-18", "title": "Cloudflare Dashboard Workers KV Issue", "severity": "MEDIUM", "service_stack": ["Dashboard", "Workers KV", "Cloudflare Edge", "DNS"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-18 08:15:41 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-18 08:04:48 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-18 07:24:20 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-18 06:42:21 UTC] Cloudflare SRE (Investigating): When searching for a Workers KV in the dashboard, the page hangs, typically upon the second attempt, causing the entire dashboard to freeze. This issue only impacts searching in the dashboard. Workers and Workers KV themselves are not affected.\n\nWe are working to analyse and mitigate this problem. More updates to follow shortly.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. When searching for a Workers KV in the dashboard, the page hangs, typically upon the second attempt, causing the entire dashboard to freeze. This issue only impacts searching in the dashboard. Workers and Workers KV themselves are not affected.\n\nWe are working to analyse and mitigate this pro", "breaking_config_code": "# Incident architectural state during Cloudflare Dashboard Workers KV Issue\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Dashboard\", \"Workers KV\", \"Cloudflare Edge\", \"DNS\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/jds6b1j6dj8q", "metadata": {"raw_id": "jds6b1j6dj8q", "status": "resolved", "resolved_at": "2026-09-18T08:15:41.658Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-n3n98pb4", "company": "Cloudflare", "date": "2026-09-17", "title": "Increased Errors for Durable Objects and Downstream Services in Asia Pacific (APAC) Region", "severity": "MEDIUM", "service_stack": ["AI Search", "Artifacts", "Containers", "D1"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-18 00:54:03 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-18 00:45:48 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-17 23:37:18 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating an issue causing elevated error rates for Durable Objects and downstream services in the Asia Pacific region. We are working to mitigate this issue and will provide additional updates shortly.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare is investigating an issue causing elevated error rates for Durable Objects and downstream services in the Asia Pacific region. We are working to mitigate this issue and will provide additional updates shortly.", "breaking_config_code": "# Incident architectural state during Increased Errors for Durable Objects and Downstream Services in Asia Pacific (APAC) Region\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"AI Search\", \"Artifacts\", \"Containers\", \"D1\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on AI Search cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/n3n98pb4x9f4", "metadata": {"raw_id": "n3n98pb4x9f4", "status": "resolved", "resolved_at": "2026-09-18T00:54:03.781Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-823rbdm2", "company": "Cloudflare", "date": "2026-09-17", "title": "Replicate Pruna issue", "severity": "MEDIUM", "service_stack": ["Replicate", "Cloudflare Edge", "DNS", "WAF"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-17 21:51:43 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-17 01:09:40 UTC] Cloudflare SRE (Identified): Some Pruna models may not be able to scale up and are therefore either experiencing long queue times or entirely unavailable. We are working with Pruna to resolve the issue.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. Some Pruna models may not be able to scale up and are therefore either experiencing long queue times or entirely unavailable. We are working with Pruna to resolve the issue.", "breaking_config_code": "# Incident architectural state during Replicate Pruna issue\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Replicate\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Replicate cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/823rbdm2k25x", "metadata": {"raw_id": "823rbdm2k25x", "status": "resolved", "resolved_at": "2026-09-17T21:51:43.704Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-l3t86mb1", "company": "Cloudflare", "date": "2026-09-17", "title": "Network Performance Issues in Vancouver, Canada", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-17 20:42:03 UTC] Cloudflare SRE (Resolved): Cloudflare experienced network performance issues in Vancouver, Canada, between 20:12 and 20:24 UTC. This incident has been resolved.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare experienced network performance issues in Vancouver, Canada, between 20:12 and 20:24 UTC. This incident has been resolved.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in Vancouver, Canada\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/l3t86mb1xdxc", "metadata": {"raw_id": "l3t86mb1xdxc", "status": "resolved", "resolved_at": "2026-09-17T20:42:03.416Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-rhmpng7k", "company": "Cloudflare", "date": "2026-09-17", "title": "Network Performance Issues in Ashburn, VA, United States", "severity": "MEDIUM", "service_stack": ["Ashburn, VA, United States - (IAD)", "Cloudflare Edge", "DNS", "WAF"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-17 19:58:13 UTC] Cloudflare SRE (Resolved): This incident has been resolved.\n[2026-09-17 18:32:36 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-17 18:29:43 UTC] Cloudflare SRE (Investigating): Cloudflare identified an issue affecting network performance in Ashburn, VA, United States. A fix has been implemented, and we are monitoring the results.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Cloudflare identified an issue affecting network performance in Ashburn, VA, United States. A fix has been implemented, and we are monitoring the results.", "breaking_config_code": "# Incident architectural state during Network Performance Issues in Ashburn, VA, United States\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Ashburn, VA, United States - (IAD)\", \"Cloudflare Edge\", \"DNS\", \"WAF\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Ashburn, VA, United States - (IAD) cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/rhmpng7klcqw", "metadata": {"raw_id": "rhmpng7klcqw", "status": "resolved", "resolved_at": "2026-09-17T19:58:13.245Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-83kl8stz", "company": "Cloudflare", "date": "2026-09-17", "title": "Increased HTTP Errors in GIG (Rio de Janeiro)", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-17 14:41:09 UTC] Cloudflare SRE (Resolved): Cloudflare is aware that there was an increased level of HTTP errors in the GIG (Rio de Janeiro) datacenter, between 14:00 and 14:30 UTC. This has since recovered and normal operations have resumed.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Cloudflare is aware that there was an increased level of HTTP errors in the GIG (Rio de Janeiro) datacenter, between 14:00 and 14:30 UTC. This has since recovered and normal operations have resumed.", "breaking_config_code": "# Incident architectural state during Increased HTTP Errors in GIG (Rio de Janeiro)\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/83kl8stzw5zn", "metadata": {"raw_id": "83kl8stzw5zn", "status": "resolved", "resolved_at": "2026-09-17T14:00:00.000Z"}}
{"incident_id": "INC-2026-CLOUDFLARE-k4crxsx8", "company": "Cloudflare", "date": "2026-09-16", "title": "Hyperdrive Elevated Origin Connection Failure Rates", "severity": "MEDIUM", "service_stack": ["Cloudflare Edge", "DNS", "WAF", "Workers"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-17 20:06:00 UTC] Cloudflare SRE (Resolved): Some Hyperdrives experienced elevated failure rates when connecting to origin databases between 2026-09-16 22:45 UTC and 2026-09-17 00:45 UTC due to a misconfigured release. Hyperdrives connecting through Workers VPC or Cloudflare Access tunnels were not affected. \n\nThis incident has been resolved.", "root_cause_analysis": "Official investigation timeline recorded by Cloudflare engineering: Some Hyperdrives experienced elevated failure rates when connecting to origin databases between 2026-09-16 22:45 UTC and 2026-09-17 00:45 UTC due to a misconfigured release. Hyperdrives connecting through Workers VPC or Cloudflare Access tunnels were not affected. \n\nThis incident has been resolved.", "breaking_config_code": "# Incident architectural state during Hyperdrive Elevated Origin Connection Failure Rates\nservice_cluster:\n  provider: \"Cloudflare\"\n  impacted_components: [\"Cloudflare Edge\", \"DNS\", \"WAF\", \"Workers\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Cloudflare SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloudflare Edge cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://www.cloudflarestatus.com/incidents/k4crxsx8xk36", "metadata": {"raw_id": "k4crxsx8xk36", "status": "resolved", "resolved_at": "2026-09-16T22:30:00.000Z"}}
{"incident_id": "INC-2026-OPENAI-01M45E0J", "company": "OpenAI", "date": "2026-10-05", "title": "Elevated Work Mode errors", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-10-05 07:14:08 UTC] OpenAI SRE (Investigating): We are continuing to observe elevated Work Mode errors. Scheduled tasks may also be impacted.\n[2026-10-05 07:03:53 UTC] OpenAI SRE (Investigating): We are observing elevated Work Mode errors. Scheduled tasks may also be impacted.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: We are continuing to observe elevated Work Mode errors. Scheduled tasks may also be impacted. We are observing elevated Work Mode errors. Scheduled tasks may also be impacted.", "breaking_config_code": "# Incident architectural state during Elevated Work Mode errors\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M45E0JFFJZ6EQ3BWYPW74R2Z", "metadata": {"raw_id": "01M45E0JFFJZ6EQ3BWYPW74R2Z", "status": "investigating", "resolved_at": null}}
{"incident_id": "INC-2026-OPENAI-01M3YNNV", "company": "OpenAI", "date": "2026-10-02", "title": "Issues with data analysis and file creation in ChatGPT", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-10-02 16:51:13 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-10-02 16:03:10 UTC] OpenAI SRE (Monitoring): Some users experienced errors when running code, analyzing data or creating files in ChatGPT.\n\nWe have applied the mitigation and are monitoring the recovery.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. Some users experienced errors when running code, analyzing data or creating files in ChatGPT.\n\nWe have applied the mitigation and are monitoring the recovery.", "breaking_config_code": "# Incident architectural state during Issues with data analysis and file creation in ChatGPT\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3YNNVTSCXS8YM2V1YMHMVSE", "metadata": {"raw_id": "01M3YNNVTSCXS8YM2V1YMHMVSE", "status": "resolved", "resolved_at": "2026-10-02T16:51:13Z"}}
{"incident_id": "INC-2026-OPENAI-01M3R1T4", "company": "OpenAI", "date": "2026-09-30", "title": "Elevated errors in ChatGPT Space Pages", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-10-01 23:44:57 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-10-01 16:51:16 UTC] OpenAI SRE (Monitoring): We are continuing to monitor our mitigiations. Some users may see slow or timed out results, especially for creating new pages or spaces.\n[2026-09-30 15:00:05 UTC] OpenAI SRE (Monitoring): We have applied mitigations and are monitoring the recovery.\n[2026-09-30 10:34:34 UTC] OpenAI SRE (Monitoring): All impacted services are recovered, we are continuing to monitor for any reoccurrence.\n[2026-09-30 06:03:10 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-30 02:20:32 UTC] OpenAI SRE (Identified): We have identified that users may experience errors creating or interacting with Pages, including failures when using Page tools or connecting to live Page sessions.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We are continuing to monitor our mitigiations. Some users may see slow or timed out results, especially for creating new pages or spaces. We have applied mitigations and are monitoring the recovery. All impacted services are recovered, we are continuing to monitor for any reoccurrence. We have applied the mitigation and are monitoring the recovery. We have identified that users may experience errors", "breaking_config_code": "# Incident architectural state during Elevated errors in ChatGPT Space Pages\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3R1T4FCR1337FBBYY9K2RPB", "metadata": {"raw_id": "01M3R1T4FCR1337FBBYY9K2RPB", "status": "resolved", "resolved_at": "2026-10-01T23:44:57Z"}}
{"incident_id": "INC-2026-OPENAI-01M3WCKT", "company": "OpenAI", "date": "2026-10-01", "title": "Issues with login, signup, and ads", "severity": "HIGH", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-10-01 19:39:30 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-10-01 19:26:50 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-10-01 19:17:04 UTC] OpenAI SRE (Identified): We have identified that users are experiencing login issues for the impacted services.\n\nWe are working on implementing a mitigation.\n[2026-10-01 19:06:18 UTC] OpenAI SRE (Investigating): We are investigating issues affecting login, signup, and ads\n[2026-10-01 18:46:17 UTC] OpenAI SRE (Investigating): We are investigating an issue affecting login and signup. We will share further updates as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We have identified that users are experiencing login issues for the impacted services.\n\nWe are working on implementing a mitigation. We are investigating issues affecting login, signup, and ads We are investigating an issue affecting login and signup. We will share further updates as we learn more.", "breaking_config_code": "# Incident architectural state during Issues with login, signup, and ads\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3WCKTAN41RZ01SBRRTY4AYM", "metadata": {"raw_id": "01M3WCKTAN41RZ01SBRRTY4AYM", "status": "resolved", "resolved_at": "2026-10-01T19:39:30Z"}}
{"incident_id": "INC-2026-OPENAI-01M3SMF1", "company": "OpenAI", "date": "2026-09-30", "title": "Elevated latency for some API requests", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-30 20:35:46 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-30 18:21:53 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-30 17:51:40 UTC] OpenAI SRE (Identified): We have implemented an initial mitigation and are seeing improvements in API latency. We are continuing to investigate the scope of the issue and apply additional mitigations as needed. Some requests to the Responses and Chat Completions APIs may still experience elevated latency or timeouts.\n[2026-09-30 17:13:13 UTC] OpenAI SRE (Identified): We have identified that users are experiencing elevated latency for the impacted services.\n\nWe are working on implementing a mitigation.\n[2026-09-30 17:05:46 UTC] OpenAI SRE (Identified): We have identified that users are experiencing elevated latency for the impacted services.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We have implemented an initial mitigation and are seeing improvements in API latency. We are continuing to investigate the scope of the issue and apply additional mitigations as needed. Some requests to the Responses and Chat Completions APIs may still experience elevated latency or timeouts. We have identified that users are experienci", "breaking_config_code": "# Incident architectural state during Elevated latency for some API requests\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3SMF1Q0TDCQVNYSXYG37QMR", "metadata": {"raw_id": "01M3SMF1Q0TDCQVNYSXYG37QMR", "status": "resolved", "resolved_at": "2026-09-30T20:35:46Z"}}
{"incident_id": "INC-2026-OPENAI-01M3RDNY", "company": "OpenAI", "date": "2026-09-30", "title": "Elevated error rates for ChatGPT Pro and Plus users", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-30 13:23:37 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-30 10:36:34 UTC] OpenAI SRE (Monitoring): All impacted services are recovered, we are continuing to monitor for any reoccurrence.\n[2026-09-30 05:56:48 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-30 05:47:57 UTC] OpenAI SRE (Identified): We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. All impacted services are recovered, we are continuing to monitor for any reoccurrence. We have applied the mitigation and are monitoring the recovery. We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "breaking_config_code": "# Incident architectural state during Elevated error rates for ChatGPT Pro and Plus users\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3RDNY37CAPQGRKPBVMNRT4K", "metadata": {"raw_id": "01M3RDNY37CAPQGRKPBVMNRT4K", "status": "resolved", "resolved_at": "2026-09-30T13:23:37Z"}}
{"incident_id": "INC-2026-OPENAI-01M3Q4HM", "company": "OpenAI", "date": "2026-09-29", "title": "Support available via email", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-29 23:18:57 UTC] OpenAI SRE (Resolved): The issue affecting support chat has been resolved. You can now contact our support team through the Help Center as usual.\n\nThank you for your patience while we worked to restore service.\n[2026-09-29 21:50:57 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-29 18:50:38 UTC] OpenAI SRE (Investigating): Our Help Center is available, but support chat remains unavailable. If you need assistance, you can browse the Help Center or email [support@openai.com](mailto:support@openai.com \"support@openai.com\").\n[2026-09-29 17:55:17 UTC] OpenAI SRE (Investigating): Our Help Center is available, but support chat remains unavailable. If you need assistance, you can browse the Help Center or email [support@openai.com](mailto:support@openai.com \"support@openai.com\").\n[2026-09-29 17:49:05 UTC] OpenAI SRE (Investigating): Our Help Center and support chat are currently unavailable. If you need assistance, you can still reach our support team by emailing [support@openai.com](mailto:support@openai.com \"support@openai.com\").\n\nWe apologize for the inconvenience.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: The issue affecting support chat has been resolved. You can now contact our support team through the Help Center as usual.\n\nThank you for your patience while we worked to restore service. We have applied the mitigation and are monitoring the recovery. Our Help Center is available, but support chat remains unavailable. If you need assistance, you can browse the Help Center or email [support@openai.com](mailto:support@openai.com \"support@openai.com", "breaking_config_code": "# Incident architectural state during Support available via email\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3Q4HMNP8SZ27DTZKW6F5BJ4", "metadata": {"raw_id": "01M3Q4HMNP8SZ27DTZKW6F5BJ4", "status": "resolved", "resolved_at": "2026-09-29T23:18:57Z"}}
{"incident_id": "INC-2026-OPENAI-01M3Q4RK", "company": "OpenAI", "date": "2026-09-29", "title": "Elevated errors across ChatGPT, Codex, and the API including the Agents API", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-29 23:14:02 UTC] OpenAI SRE (Resolved): The issue causing elevated errors across ChatGPT, Codex, and the API has been resolved, and all affected services have recovered.\n\nThank you for your patience while we worked to restore service.\n\nThe detailed Root Cause Analysis (RCA) will be published in the next 5 business days.\n[2026-09-29 22:47:10 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-29 22:03:22 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-29 21:09:11 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-29 19:39:36 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-29 19:08:39 UTC] OpenAI SRE (Investigating): We’re still investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API.\n\nSome users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more.\n[2026-09-29 18:24:17 UTC] OpenAI SRE (Investigating): We’re investigating elevated errors affecting ChatGPT, Codex, and the API including the Agents API.\n\nSome users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more.\n[2026-09-29 17:52:52 UTC] OpenAI SRE (Investigating): We’re investigating elevated errors affecting ChatGPT, Codex, and the API. Some users may experience failed requests, difficulty logging in or signing up, and tasks that do not complete. We’ll share updates as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: The issue causing elevated errors across ChatGPT, Codex, and the API has been resolved, and all affected services have recovered.\n\nThank you for your patience while we worked to restore service.\n\nThe detailed Root Cause Analysis (RCA) will be published in the next 5 business days. We have applied the mitigation and are monitoring the recovery. We have applied the mitigation and are monitoring the recovery. We have applied the mitigation and are m", "breaking_config_code": "# Incident architectural state during Elevated errors across ChatGPT, Codex, and the API including the Agents API\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3Q4RK1SM4EMK445GGPG7C0N", "metadata": {"raw_id": "01M3Q4RK1SM4EMK445GGPG7C0N", "status": "resolved", "resolved_at": "2026-09-29T23:14:02Z"}}
{"incident_id": "INC-2026-OPENAI-01M3DCNW", "company": "OpenAI", "date": "2026-09-25", "title": "Issues with Codex", "severity": "CRITICAL", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-09-25 23:54:41 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-25 23:45:27 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-25 23:34:02 UTC] OpenAI SRE (Identified): We have identified root cause and are moving towards mitigation.\n[2026-09-25 23:19:11 UTC] OpenAI SRE (Identified): Login via API key will unblock access at this time.\n[2026-09-25 23:03:04 UTC] OpenAI SRE (Identified): We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.\n[2026-09-25 22:58:48 UTC] OpenAI SRE (Identified): We have identified that users are experiencing a codex outage.\nWe have identified the internal issue and are heading towards a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We have identified root cause and are moving towards mitigation. Login via API key will unblock access at this time. We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation. We have identified that users are experiencing a codex outage.\nWe have identified the", "breaking_config_code": "# Incident architectural state during Issues with Codex\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3DCNWMW57HYK8FJ5FBFPA39", "metadata": {"raw_id": "01M3DCNWMW57HYK8FJ5FBFPA39", "status": "resolved", "resolved_at": "2026-09-25T23:54:41Z"}}
{"incident_id": "INC-2026-OPENAI-01M3ACKD", "company": "OpenAI", "date": "2026-09-24", "title": "Elevated Error Rates on GPT-6 Astra Pro", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-24 19:46:28 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-24 19:32:45 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-24 18:59:44 UTC] OpenAI SRE (Identified): We have identified that users are experiencing elevated errors for GPT-6 Astra Pro.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We have identified that users are experiencing elevated errors for GPT-6 Astra Pro.\n\nWe are working on implementing a mitigation.", "breaking_config_code": "# Incident architectural state during Elevated Error Rates on GPT-6 Astra Pro\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M3ACKDE4GYY67FXXNRRSC0CE", "metadata": {"raw_id": "01M3ACKDE4GYY67FXXNRRSC0CE", "status": "resolved", "resolved_at": "2026-09-24T19:46:28Z"}}
{"incident_id": "INC-2026-OPENAI-01M389CD", "company": "OpenAI", "date": "2026-09-23", "title": "Mobile users unable to see Work Mode and the Model Picker", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-23 23:49:06 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-23 23:32:53 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-23 23:25:00 UTC] OpenAI SRE (Investigating): We have identified that mobile users are not able to see work mode or the model picker when using ChatGPT.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We have identified that mobile users are not able to see work mode or the model picker when using ChatGPT.\n\nWe are working on implementing a mitigation.", "breaking_config_code": "# Incident architectural state during Mobile users unable to see Work Mode and the Model Picker\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M389CDQ97B11QPMSRAAYSE5S", "metadata": {"raw_id": "01M389CDQ97B11QPMSRAAYSE5S", "status": "resolved", "resolved_at": "2026-09-23T23:49:06Z"}}
{"incident_id": "INC-2026-OPENAI-01M36RMC", "company": "OpenAI", "date": "2026-09-23", "title": "Elevated Error Rates for ChatGPT across Plus and Pro plans.", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-23 09:54:16 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-23 09:45:17 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-23 09:13:00 UTC] OpenAI SRE (Identified): We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "breaking_config_code": "# Incident architectural state during Elevated Error Rates for ChatGPT across Plus and Pro plans.\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M36RMC01ZFWQ861WYJKC4XE1", "metadata": {"raw_id": "01M36RMC01ZFWQ861WYJKC4XE1", "status": "resolved", "resolved_at": "2026-09-23T09:54:16Z"}}
{"incident_id": "INC-2026-OPENAI-01M34TAF", "company": "OpenAI", "date": "2026-09-22", "title": "Elevated Error Rates for ChatGPT Work, across Plus, Pro, Business, Enterprise and Education plans.", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-22 15:58:32 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-22 15:26:41 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-22 15:04:05 UTC] OpenAI SRE (Identified): We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "breaking_config_code": "# Incident architectural state during Elevated Error Rates for ChatGPT Work, across Plus, Pro, Business, Enterprise and Education plans.\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M34TAFM9WBGEBE3G1GBH4SE8", "metadata": {"raw_id": "01M34TAFM9WBGEBE3G1GBH4SE8", "status": "resolved", "resolved_at": "2026-09-22T15:58:32Z"}}
{"incident_id": "INC-2026-OPENAI-01M348TX", "company": "OpenAI", "date": "2026-09-22", "title": "Increased error rate for Plus and Pro users.", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-22 10:37:42 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-22 09:58:28 UTC] OpenAI SRE (Investigating): We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "breaking_config_code": "# Incident architectural state during Increased error rate for Plus and Pro users.\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M348TX2DX7KPM9X857N4APNV", "metadata": {"raw_id": "01M348TX2DX7KPM9X857N4APNV", "status": "resolved", "resolved_at": "2026-09-22T10:37:42Z"}}
{"incident_id": "INC-2026-OPENAI-01M2VA7X", "company": "OpenAI", "date": "2026-09-18", "title": "Overbilling for OpenAI-hosted containers in the Agent API", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-19 07:52:40 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-19 05:00:57 UTC] OpenAI SRE (Monitoring): We have applied the mitigation, and any new sessions would not run into this issue. We are monitoring the recovery.\n[2026-09-19 01:08:42 UTC] OpenAI SRE (Identified): We are still implementing the mitigation.\n[2026-09-18 23:22:34 UTC] OpenAI SRE (Investigating): We’re continuing to work on a fix for the container overbilling issue.\n\nWe’re also reviewing affected usage to identify impacted customers and calculate refunds.\n[2026-09-18 22:29:53 UTC] OpenAI SRE (Investigating): We’re investigating an issue causing higher-than-expected charges for OpenAI-hosted containers in the Agent API.\n\nWe’re working on a fix and preparing refunds for affected customers. We’ll share further updates as we make progress.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation, and any new sessions would not run into this issue. We are monitoring the recovery. We are still implementing the mitigation. We’re continuing to work on a fix for the container overbilling issue.\n\nWe’re also reviewing affected usage to identify impacted customers and calculate refunds. We’re investigating an issue causing higher-than-expected charges for OpenAI-hoste", "breaking_config_code": "# Incident architectural state during Overbilling for OpenAI-hosted containers in the Agent API\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2VA7X37P1ASADSNZ1CG4N4D", "metadata": {"raw_id": "01M2VA7X37P1ASADSNZ1CG4N4D", "status": "resolved", "resolved_at": "2026-09-19T07:52:40Z"}}
{"incident_id": "INC-2026-OPENAI-01M2V76G", "company": "OpenAI", "date": "2026-09-18", "title": "Delayed support responses", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-19 01:10:40 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-18 21:59:34 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n\nSome support responses by email and chat may still be delayed while we work through affected cases.\n[2026-09-18 21:36:41 UTC] OpenAI SRE (Identified): Some users are experiencing delayed responses from OpenAI Support by email and chat.\n\nWe’re investigating and will share updates as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery.\n\nSome support responses by email and chat may still be delayed while we work through affected cases. Some users are experiencing delayed responses from OpenAI Support by email and chat.\n\nWe’re investigating and will share updates as we learn more.", "breaking_config_code": "# Incident architectural state during Delayed support responses\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2V76GEPJB0HQGRA0QERRZ3T", "metadata": {"raw_id": "01M2V76GEPJB0HQGRA0QERRZ3T", "status": "resolved", "resolved_at": "2026-09-19T01:10:40Z"}}
{"incident_id": "INC-2026-OPENAI-01M2VBZB", "company": "OpenAI", "date": "2026-09-18", "title": "SSO sign-in and SCIM provisioning issues", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-09-18 23:18:55 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-18 23:10:37 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-18 23:00:09 UTC] OpenAI SRE (Identified): Some users are unable to sign in with single sign-on (SSO). User and group provisioning through SCIM is also affected.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. Some users are unable to sign in with single sign-on (SSO). User and group provisioning through SCIM is also affected.\n\nWe are working on implementing a mitigation.", "breaking_config_code": "# Incident architectural state during SSO sign-in and SCIM provisioning issues\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2VBZB1RYSMXHZNRA25ZJ36X", "metadata": {"raw_id": "01M2VBZB1RYSMXHZNRA25ZJ36X", "status": "resolved", "resolved_at": "2026-09-18T23:18:55Z"}}
{"incident_id": "INC-2026-OPENAI-01M2RMCS", "company": "OpenAI", "date": "2026-09-17", "title": "We are seeing elevated error rates across API models", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-17 21:50:36 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-17 21:31:05 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-17 21:29:35 UTC] OpenAI SRE (Identified): We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We have identified that users are experiencing elevated errors for the impacted services.\n\nWe are working on implementing a mitigation.", "breaking_config_code": "# Incident architectural state during We are seeing elevated error rates across API models\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2RMCS2HVBXGBFKEZ9RZR4FA", "metadata": {"raw_id": "01M2RMCS2HVBXGBFKEZ9RZR4FA", "status": "resolved", "resolved_at": "2026-09-17T21:50:36Z"}}
{"incident_id": "INC-2026-OPENAI-01M2RC0W", "company": "OpenAI", "date": "2026-09-17", "title": "Elevated errors affecting ChatGPT Work mode", "severity": "HIGH", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-17 20:24:45 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-17 19:57:22 UTC] OpenAI SRE (Identified): We are still implementing the mitigation.\n[2026-09-17 19:38:03 UTC] OpenAI SRE (Investigating): We are investigating the issue for the listed services.\n[2026-09-17 19:03:17 UTC] OpenAI SRE (Investigating): We are investigating the issue for the listed services. Some users may experience failures when starting or running Work tasks.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We are still implementing the mitigation. We are investigating the issue for the listed services. We are investigating the issue for the listed services. Some users may experience failures when starting or running Work tasks.", "breaking_config_code": "# Incident architectural state during Elevated errors affecting ChatGPT Work mode\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2RC0WHGTX8EHDH7D60JJ7FC", "metadata": {"raw_id": "01M2RC0WHGTX8EHDH7D60JJ7FC", "status": "resolved", "resolved_at": "2026-09-17T20:24:45Z"}}
{"incident_id": "INC-2026-OPENAI-01M2NRHT", "company": "OpenAI", "date": "2026-09-16", "title": "Elevated errors in ChatGPT Work", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-16 19:34:36 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-16 19:20:27 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-16 19:15:47 UTC] OpenAI SRE (Investigating): We are continuing to investigate elevated errors affecting ChatGPT Work. We will provide updates as we learn more.\n[2026-09-16 18:44:32 UTC] OpenAI SRE (Investigating): We are investigating elevated errors affecting ChatGPT Work. We will provide updates as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We are continuing to investigate elevated errors affecting ChatGPT Work. We will provide updates as we learn more. We are investigating elevated errors affecting ChatGPT Work. We will provide updates as we learn more.", "breaking_config_code": "# Incident architectural state during Elevated errors in ChatGPT Work\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2NRHTYAM3K3M93X1D068MCY", "metadata": {"raw_id": "01M2NRHTYAM3K3M93X1D068MCY", "status": "resolved", "resolved_at": "2026-09-16T19:34:36Z"}}
{"incident_id": "INC-2026-OPENAI-01M2KQNE", "company": "OpenAI", "date": "2026-09-15", "title": "Elevated errors with gpt-image-2.5-flare", "severity": "HIGH", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-16 00:30:48 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-15 23:58:30 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-15 23:50:32 UTC] OpenAI SRE (Investigating): We are experiencing elevated error rates for image generation and editing requests using gpt-image-2.5-flare in the API.\n\nOur team is working to mitigate the issue. We will provide another update as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We are experiencing elevated error rates for image generation and editing requests using gpt-image-2.5-flare in the API.\n\nOur team is working to mitigate the issue. We will provide another update as more information becomes available.", "breaking_config_code": "# Incident architectural state during Elevated errors with gpt-image-2.5-flare\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2KQNE5C42NEZPX6V01NHH5W", "metadata": {"raw_id": "01M2KQNE5C42NEZPX6V01NHH5W", "status": "resolved", "resolved_at": "2026-09-16T00:30:48Z"}}
{"incident_id": "INC-2026-OPENAI-01M2JZR5", "company": "OpenAI", "date": "2026-09-15", "title": "Ads Manager login issues", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-09-15 16:54:01 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-15 16:52:36 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery.", "breaking_config_code": "# Incident architectural state during Ads Manager login issues\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2JZR57HRQTKQGTCWG31M3AS", "metadata": {"raw_id": "01M2JZR57HRQTKQGTCWG31M3AS", "status": "resolved", "resolved_at": "2026-09-15T16:54:01Z"}}
{"incident_id": "INC-2026-OPENAI-01M2HYH6", "company": "OpenAI", "date": "2026-09-15", "title": "Elevated errors from GPT-5.6 and GPT-5.6 Instant on paid plans", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-15 07:53:36 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-15 07:24:26 UTC] OpenAI SRE (Monitoring): We have applied the mitigation and are monitoring the recovery.\n[2026-09-15 07:12:04 UTC] OpenAI SRE (Investigating): We are investigating the issue for the listed services.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied the mitigation and are monitoring the recovery. We are investigating the issue for the listed services.", "breaking_config_code": "# Incident architectural state during Elevated errors from GPT-5.6 and GPT-5.6 Instant on paid plans\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2HYH64J2CZMZ63HEV2FCQFA", "metadata": {"raw_id": "01M2HYH64J2CZMZ63HEV2FCQFA", "status": "resolved", "resolved_at": "2026-09-15T07:53:36Z"}}
{"incident_id": "INC-2026-OPENAI-01M2GA8X", "company": "OpenAI", "date": "2026-09-14", "title": "Elevated errors affecting Work Mode in ChatGPT", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-15 03:11:36 UTC] OpenAI SRE (Resolved): All impacted services have now fully recovered.\n[2026-09-14 19:42:08 UTC] OpenAI SRE (Monitoring): We have applied additional mitigations for Work Mode. We are monitoring to confirm that workspace tools and files are functioning normally for ChatGPT Plus users.\n[2026-09-14 15:58:48 UTC] OpenAI SRE (Monitoring): Earlier today, some ChatGPT Plus users using Work Mode experienced errors starting or resuming tasks, or had limited access to workspace tools and files. We have applied a mitigation and service has recovered. We are monitoring the results.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: All impacted services have now fully recovered. We have applied additional mitigations for Work Mode. We are monitoring to confirm that workspace tools and files are functioning normally for ChatGPT Plus users. Earlier today, some ChatGPT Plus users using Work Mode experienced errors starting or resuming tasks, or had limited access to workspace tools and files. We have applied a mitigation and service has recovered. We are monitoring the results", "breaking_config_code": "# Incident architectural state during Elevated errors affecting Work Mode in ChatGPT\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2GA8XTS6VB3QCDEGZ0HNAQ5", "metadata": {"raw_id": "01M2GA8XTS6VB3QCDEGZ0HNAQ5", "status": "resolved", "resolved_at": "2026-09-15T03:11:36Z"}}
{"incident_id": "INC-2026-OPENAI-01M2H3J1", "company": "OpenAI", "date": "2026-09-14", "title": "Degraded Performance affecting Agents API", "severity": "MEDIUM", "service_stack": ["OpenAI API", "ChatGPT", "GPU Inference Cluster", "Redis"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-14 23:39:21 UTC] OpenAI SRE (Resolved): The issue affecting the Agents API has been resolved. Managed sessions are now processing turns normally.\n[2026-09-14 23:28:43 UTC] OpenAI SRE (Monitoring): We have applied mitigations and are seeing recovery, but the service has not fully recovered. We are continuing to monitor recovery.\n[2026-09-14 23:20:41 UTC] OpenAI SRE (Monitoring): Since 1:30 PM Pacific Time on September 14, customers using the Agents API have experienced delays or been unable to start turns in managed sessions.", "root_cause_analysis": "Official investigation timeline recorded by OpenAI engineering: The issue affecting the Agents API has been resolved. Managed sessions are now processing turns normally. We have applied mitigations and are seeing recovery, but the service has not fully recovered. We are continuing to monitor recovery. Since 1:30 PM Pacific Time on September 14, customers using the Agents API have experienced delays or been unable to start turns in managed sessions.", "breaking_config_code": "# Incident architectural state during Degraded Performance affecting Agents API\nservice_cluster:\n  provider: \"OpenAI\"\n  impacted_components: [\"OpenAI API\", \"ChatGPT\", \"GPU Inference Cluster\", \"Redis\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by OpenAI SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on OpenAI API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.openai.com/incidents/01M2H3J1D6Y7RHAP49GRWGJAY0", "metadata": {"raw_id": "01M2H3J1D6Y7RHAP49GRWGJAY0", "status": "resolved", "resolved_at": "2026-09-14T23:39:21Z"}}
{"incident_id": "INC-2026-DATADOG-yrkfn68n", "company": "Datadog", "date": "2026-10-02", "title": "Delayed RUM sessions", "severity": "MEDIUM", "service_stack": ["RUM", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION"], "symptom_logs": "[2026-10-02 11:03:45 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-10-02 09:47:33 UTC] Datadog SRE (Monitoring): Latency has now resolved and monitors evaluation is being back to normal.  We are still monitoring the issue for now.\n[2026-10-02 09:23:41 UTC] Datadog SRE (Monitoring): The issue has been identified we're seeing signs of recovery and we are monitoring the issue.\n[2026-10-02 08:46:19 UTC] Datadog SRE (Investigating): We are investigating increased latency processing RUM sessions.\nAs a result of this issue, some users may see gaps or delays in RUM graphs as well as empty or partial query results on RUM Sessions, RUM Analytics, and RUM Application pages since Oct 2, 2026, 11:42 AM UTC\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. Latency has now resolved and monitors evaluation is being back to normal.  We are still monitoring the issue for now. The issue has been identified we're seeing signs of recovery and we are monitoring the issue. We are investigating increased latency processing RUM sessions.\nAs a result of this issue, some users may see gaps or delays in RUM graphs as well as empty or partial query results on RUM Sessions, RUM Ana", "breaking_config_code": "# Incident architectural state during Delayed RUM sessions\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"RUM\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on RUM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/gjz5frd5dyxl", "metadata": {"raw_id": "yrkfn68nnnnr", "status": "resolved", "resolved_at": "2026-10-02T11:03:45.749-04:00"}}
{"incident_id": "INC-2026-DATADOG-41hx12qt", "company": "Datadog", "date": "2026-09-30", "title": "Delayed Events", "severity": "MEDIUM", "service_stack": ["APM", "CI Visibility", "Cloud Network Monitoring", "Error Tracking"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-30 14:51:03 UTC] Datadog SRE (Resolved): The issue is now resolved.\n[2026-09-30 14:29:22 UTC] Datadog SRE (Monitoring): We have deployed a mitigation and we are monitoring the results.\n[2026-09-30 14:05:31 UTC] Datadog SRE (Identified): We have identified the issue and are working on a mitigation strategy.\n[2026-09-30 14:02:40 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Events generated by RUM, Trace Analytics, Service Checks, CI Visibility, Cloud Network Monitoring, and Error Tracking.\nAs a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards since Sep 30, 2026, 5:25 PM UTC\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: The issue is now resolved. We have deployed a mitigation and we are monitoring the results. We have identified the issue and are working on a mitigation strategy. We are investigating increased latency processing Events generated by RUM, Trace Analytics, Service Checks, CI Visibility, Cloud Network Monitoring, and Error Tracking.\nAs a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards si", "breaking_config_code": "# Incident architectural state during Delayed Events\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"CI Visibility\", \"Cloud Network Monitoring\", \"Error Tracking\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8fknzl9hmvs7", "metadata": {"raw_id": "41hx12qtkl7x", "status": "resolved", "resolved_at": "2026-09-30T14:51:03.098-04:00"}}
{"incident_id": "INC-2026-DATADOG-cqxdntdk", "company": "Datadog", "date": "2026-09-25", "title": "Users are unable to acknowledge, escalate, or resolve On-Call Pages", "severity": "MEDIUM", "service_stack": ["Incident Response", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-25 11:38:57 UTC] Datadog SRE (Resolved): The issue is now resolved.\n[2026-09-25 11:29:27 UTC] Datadog SRE (Monitoring): We are monitoring the issue.\n[2026-09-25 11:23:23 UTC] Datadog SRE (Identified): We have identified the issue with pages and are applying mitigations.\n[2026-09-25 11:17:33 UTC] Datadog SRE (Investigating): We are investigating an issue with users unable to acknowledge, escalate, or resolve On-Call Pages.\n[2026-09-25 11:11:50 UTC] Datadog SRE (Investigating): We are investigating an issue with users unable to acknowledge on call pages", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: The issue is now resolved. We are monitoring the issue. We have identified the issue with pages and are applying mitigations. We are investigating an issue with users unable to acknowledge, escalate, or resolve On-Call Pages. We are investigating an issue with users unable to acknowledge on call pages", "breaking_config_code": "# Incident architectural state during Users are unable to acknowledge, escalate, or resolve On-Call Pages\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Incident Response\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Incident Response cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/03h92q1l96z2", "metadata": {"raw_id": "cqxdntdk4c7d", "status": "resolved", "resolved_at": "2026-09-25T11:38:57.863-04:00"}}
{"incident_id": "INC-2026-DATADOG-g67lc6tm", "company": "Datadog", "date": "2026-09-21", "title": "Delayed Monitors Notifications", "severity": "MEDIUM", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-21 06:30:45 UTC] Datadog SRE (Resolved): The issue is now resolved.\n[2026-09-21 06:22:27 UTC] Datadog SRE (Monitoring): We are monitoring the issue.\n[2026-09-21 06:00:57 UTC] Datadog SRE (Identified): We identified the issue and is working on a fix.\n[2026-09-21 05:44:21 UTC] Datadog SRE (Investigating): We are investigating delayed evaluations for metric, service check, composite, and SLO monitors in US1 which began at Sep 21, 2026, 9:18 AM UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: The issue is now resolved. We are monitoring the issue. We identified the issue and is working on a fix. We are investigating delayed evaluations for metric, service check, composite, and SLO monitors in US1 which began at Sep 21, 2026, 9:18 AM UTC.", "breaking_config_code": "# Incident architectural state during Delayed Monitors Notifications\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/k1zlzpm9dfm2", "metadata": {"raw_id": "g67lc6tmjnlt", "status": "resolved", "resolved_at": "2026-09-21T06:30:45.576-04:00"}}
{"incident_id": "INC-2026-DATADOG-fsrqsbtp", "company": "Datadog", "date": "2026-09-20", "title": "Delayed events triggered by emails", "severity": "MEDIUM", "service_stack": ["Incident Response", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-20 02:53:02 UTC] Datadog SRE (Resolved): The issue is now resolved. All events from emails are being timely processed and we went through the backfill.\n[2026-09-20 01:17:14 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Events coming from inbound emails. As a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards and for events based workflows such as on-call notifications", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: The issue is now resolved. All events from emails are being timely processed and we went through the backfill. We are investigating increased latency processing Events coming from inbound emails. As a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards and for events based workflows such as on-call notifications", "breaking_config_code": "# Incident architectural state during Delayed events triggered by emails\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Incident Response\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Incident Response cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/txhsm142w1cz", "metadata": {"raw_id": "fsrqsbtpkp06", "status": "resolved", "resolved_at": "2026-09-20T02:53:02.925-04:00"}}
{"incident_id": "INC-2026-DATADOG-4zd1rbp4", "company": "Datadog", "date": "2026-09-03", "title": "Delayed CICD Optimization, Code Coverage, Code Security, and DORA data", "severity": "MEDIUM", "service_stack": ["CI Visibility", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-03 19:01:22 UTC] Datadog SRE (Resolved): The issue is now resolved.\n[2026-09-03 17:51:37 UTC] Datadog SRE (Monitoring): We have applied remediations, and recovery is in progress. We are continuing to monitor the issue.\n[2026-09-03 15:01:33 UTC] Datadog SRE (Monitoring): We are monitoring the issue.\n[2026-09-03 13:59:37 UTC] Datadog SRE (Identified): We identified the issue.\n[2026-09-03 13:45:21 UTC] Datadog SRE (Monitoring): We are monitoring the issue.\n[2026-09-03 13:27:58 UTC] Datadog SRE (Identified): We identified the issue.\n[2026-09-03 13:20:26 UTC] Datadog SRE (Investigating): We are investigating increased latency processing CICD Optimization, Code Coverage, Code Security, and DORA data.\nAs a result of this issue, some users may see delays with test runs and pipeline executions.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: The issue is now resolved. We have applied remediations, and recovery is in progress. We are continuing to monitor the issue. We are monitoring the issue. We identified the issue. We are monitoring the issue. We identified the issue. We are investigating increased latency processing CICD Optimization, Code Coverage, Code Security, and DORA data.\nAs a result of this issue, some users may see delays with test runs and pipeline executions.", "breaking_config_code": "# Incident architectural state during Delayed CICD Optimization, Code Coverage, Code Security, and DORA data\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"CI Visibility\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on CI Visibility cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/zstf1zx7hfy3", "metadata": {"raw_id": "4zd1rbp4pbt5", "status": "resolved", "resolved_at": "2026-09-03T19:01:22.899-04:00"}}
{"incident_id": "INC-2026-DATADOG-6k7fhxz0", "company": "Datadog", "date": "2026-09-01", "title": "Delayed DBM Monitor Evaluation", "severity": "MEDIUM", "service_stack": ["Database Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION"], "symptom_logs": "[2026-09-01 21:24:48 UTC] Datadog SRE (Resolved): The issue is now resolved.\n[2026-09-01 21:21:51 UTC] Datadog SRE (Monitoring): We are monitoring the issue.\n[2026-09-01 21:16:45 UTC] Datadog SRE (Identified): We identified the issue.\n[2026-09-01 21:07:32 UTC] Datadog SRE (Investigating): We are investigating delays in monitor evaluation, which began at Sep 2, 2026, 12:10 AM UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: The issue is now resolved. We are monitoring the issue. We identified the issue. We are investigating delays in monitor evaluation, which began at Sep 2, 2026, 12:10 AM UTC.", "breaking_config_code": "# Incident architectural state during Delayed DBM Monitor Evaluation\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Database Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Database Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/2lq8c212gd6p", "metadata": {"raw_id": "6k7fhxz0q7k1", "status": "resolved", "resolved_at": "2026-09-01T21:24:48.880-04:00"}}
{"incident_id": "INC-2026-DATADOG-0yvjrwkf", "company": "Datadog", "date": "2026-08-06", "title": "Delayed Processes data", "severity": "MEDIUM", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-06 15:37:32 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-08-06 15:27:17 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-08-06 15:18:03 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-08-06 14:51:32 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Processes data.\n\nAs a result of this issue, some users may see delays or gaps for data based on Live Process Monitoring.\n\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are investigating increased latency processing Processes data.\n\nAs a result of this issue, some users may see delays or gaps for data based on Live Process Monitoring.\n\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automaticall", "breaking_config_code": "# Incident architectural state during Delayed Processes data\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/g6k608nzbbtm", "metadata": {"raw_id": "0yvjrwkfc2np", "status": "resolved", "resolved_at": "2026-08-06T15:37:32.874-04:00"}}
{"incident_id": "INC-2026-DATADOG-w3w4b0cc", "company": "Datadog", "date": "2026-07-30", "title": "Delayed Evaluation of Service Check monitors", "severity": "MEDIUM", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-30 04:27:01 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-07-30 04:16:23 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-30 03:49:45 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-07-30 03:44:26 UTC] Datadog SRE (Investigating): We are investigating delays in Service Check monitors evaluation, which began at 6:35AM UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are investigating delays in Service Check monitors evaluation, which began at 6:35AM UTC.", "breaking_config_code": "# Incident architectural state during Delayed Evaluation of Service Check monitors\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/803q340l4b6k", "metadata": {"raw_id": "w3w4b0cchj1j", "status": "resolved", "resolved_at": "2026-07-30T04:27:01.231-04:00"}}
{"incident_id": "INC-2026-DATADOG-2c2287dz", "company": "Datadog", "date": "2026-07-29", "title": "Real user monitoring, distribution and custom processes metrics delayed", "severity": "MEDIUM", "service_stack": ["Metrics and Infra Monitoring", "Monitors", "RUM", "Datadog Ingestion"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-29 13:28:08 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-07-29 13:12:00 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-29 12:53:24 UTC] Datadog SRE (Identified): The RUM delays have been resolved. We're continuing to mitigate the issues on distribution metrics.\n[2026-07-29 12:35:04 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-07-29 11:42:12 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-07-29 11:41:51 UTC] Datadog SRE (Investigating): We are currently investigating an issue delaying the ingestion of Real User Monitoring (RUM) measure metrics, custom process metrics, and a subset of distribution metrics for some customers.\n\nAs a result, some users may see delays or gaps in RUM, custom process, and distribution metrics. To prevent false alerts caused by delayed data, affected monitors will not notify and will automatically resume once current data is available. All other monitors will operate normally. No data has been lost.\n\nWe will provide further updates as the situation progresses.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The RUM delays have been resolved. We're continuing to mitigate the issues on distribution metrics. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are currently investigating an issue delaying the ingestion of Real User Monitoring (RUM) measure metrics, custom process metrics, and a subset o", "breaking_config_code": "# Incident architectural state during Real user monitoring, distribution and custom processes metrics delayed\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Monitors\", \"RUM\", \"Datadog Ingestion\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0y0jgdxjp7hh", "metadata": {"raw_id": "2c2287dz638f", "status": "resolved", "resolved_at": "2026-07-29T13:28:08.443-04:00"}}
{"incident_id": "INC-2026-DATADOG-9kn7bmb2", "company": "Datadog", "date": "2026-07-27", "title": "Synthetics Test Results Delayed", "severity": "HIGH", "service_stack": ["Synthetics", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-27 15:52:05 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-07-27 15:46:34 UTC] Datadog SRE (Monitoring): A fix has been implemented and we're monitoring the results.\n[2026-07-27 15:36:40 UTC] Datadog SRE (Identified): We've identified the issue publishing Synthetic results. Synthetic tests are continuing to run with delayed results.\n[2026-07-27 15:25:49 UTC] Datadog SRE (Investigating): We're continuing to investigate an issue publishing Synthetic results. Synthetic tests are running and results are delayed.\n[2026-07-27 15:05:38 UTC] Datadog SRE (Investigating): We are currenting investigating an issue running Synthetic tests.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we're monitoring the results. We've identified the issue publishing Synthetic results. Synthetic tests are continuing to run with delayed results. We're continuing to investigate an issue publishing Synthetic results. Synthetic tests are running and results are delayed. We are currenting investigating an issue running Synthetic tests.", "breaking_config_code": "# Incident architectural state during Synthetics Test Results Delayed\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Synthetics\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Synthetics cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9trx2m1xsd4h", "metadata": {"raw_id": "9kn7bmb25jh1", "status": "resolved", "resolved_at": "2026-07-27T15:52:05.822-04:00"}}
{"incident_id": "INC-2026-DATADOG-qvphgr1l", "company": "Datadog", "date": "2026-07-23", "title": "Latency with Pages and Monitor state changes", "severity": "MEDIUM", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-23 14:13:36 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-07-23 14:02:15 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-23 13:31:18 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-07-23 13:08:39 UTC] Datadog SRE (Investigating): We are investigating increased latency with Pages and Monitor state changes. As a result of this issue, some users may see delays.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are investigating increased latency with Pages and Monitor state changes. As a result of this issue, some users may see delays.", "breaking_config_code": "# Incident architectural state during Latency with Pages and Monitor state changes\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ljpc864wlwq2", "metadata": {"raw_id": "qvphgr1lgbzh", "status": "resolved", "resolved_at": "2026-07-23T14:13:36.888-04:00"}}
{"incident_id": "INC-2026-DATADOG-9qt73ty9", "company": "Datadog", "date": "2026-07-10", "title": "Delayed data streams data", "severity": "HIGH", "service_stack": ["Data Streams Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-10 11:59:28 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-07-10 11:18:40 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results. A small percentage of data sent between 6:23 UTC and 14:43 UTC is still being backfilled.\n[2026-07-10 10:35:17 UTC] Datadog SRE (Investigating): We are continuing to investigate the issue.\n[2026-07-10 10:09:23 UTC] Datadog SRE (Investigating): We are currently investigating an issue affecting Data Streams Monitoring (DSM) in our US1 datacenter. As a result, data stream latency metrics may be delayed or not updating for some users. If you have monitors configured on those metrics, they may fail to alert as expected during this incident. We are not aware of any data loss at this time. Our engineering team is actively working on a fix, and we'll follow up with more information shortly.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. A small percentage of data sent between 6:23 UTC and 14:43 UTC is still being backfilled. We are continuing to investigate the issue. We are currently investigating an issue affecting Data Streams Monitoring (DSM) in our US1 datacenter. As a result, data stream latency metrics may be delayed or not updating for some users. If you have monitors configure", "breaking_config_code": "# Incident architectural state during Delayed data streams data\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Data Streams Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Data Streams Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/y5323mlt6x4g", "metadata": {"raw_id": "9qt73ty9p9ph", "status": "resolved", "resolved_at": "2026-07-10T11:59:28.762-04:00"}}
{"incident_id": "INC-2026-DATADOG-rpj3lwgx", "company": "Datadog", "date": "2026-07-02", "title": "Errors Pulling Container Images", "severity": "CRITICAL", "service_stack": ["Container Registry", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-02 21:29:11 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-07-02 21:21:10 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-02 20:55:53 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-07-02 20:25:57 UTC] Datadog SRE (Investigating): We are investigating errors pulling Datadog container images from registry.datadoghq.com. As a result of this issue, some users may be unable to download or deploy the Datadog Agent, Cluster Agent, and other Datadog container images. Containers that are already running are not affected.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are investigating errors pulling Datadog container images from registry.datadoghq.com. As a result of this issue, some users may be unable to download or deploy the Datadog Agent, Cluster Agent, and other Datadog container images. Containers that are already running are not affected.", "breaking_config_code": "# Incident architectural state during Errors Pulling Container Images\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Container Registry\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Container Registry cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/gs85vq0xmxcx", "metadata": {"raw_id": "rpj3lwgx1s3s", "status": "resolved", "resolved_at": "2026-07-02T21:29:11.981-04:00"}}
{"incident_id": "INC-2026-DATADOG-smc2wgcm", "company": "Datadog", "date": "2026-07-01", "title": "Elevated Error Rates", "severity": "MEDIUM", "service_stack": ["Datadog Ingestion", "APM", "Metrics Agent", "Kafka"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-07-01 16:37:08 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-07-01 15:43:48 UTC] Datadog SRE (Monitoring): We are continuing to monitor the situation and are taking additional preventive measures.\n[2026-07-01 15:19:01 UTC] Datadog SRE (Monitoring): We have deployed mitigation actions and are monitoring the recovery.\n[2026-07-01 15:10:43 UTC] Datadog SRE (Identified): We have identified the issue of elevated error rates and are working through mitigation actions\n[2026-07-01 14:57:38 UTC] Datadog SRE (Investigating): We are investigating elevated error rates across multiple products including: Fleet Automation, Security Products, Cloudcraft, Cloud Network Monitoring, Serverless, Kubernetes Autoscaling, and Database Monitoring.\n[2026-07-01 14:31:20 UTC] Datadog SRE (Investigating): We are actively investigating elevated error rates across multiple Datadog products.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We are continuing to monitor the situation and are taking additional preventive measures. We have deployed mitigation actions and are monitoring the recovery. We have identified the issue of elevated error rates and are working through mitigation actions We are investigating elevated error rates across multiple products including: Fleet Automation, Security Products, Cloudcraft, Cloud Network Monitoring, Serverles", "breaking_config_code": "# Incident architectural state during Elevated Error Rates\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Datadog Ingestion\", \"APM\", \"Metrics Agent\", \"Kafka\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Datadog Ingestion cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/h1vdjddg90hd", "metadata": {"raw_id": "smc2wgcmsx6r", "status": "resolved", "resolved_at": "2026-07-01T16:37:08.245-04:00"}}
{"incident_id": "INC-2026-DATADOG-71vvxf0r", "company": "Datadog", "date": "2026-06-30", "title": "Delayed data processing and errors in multiple products", "severity": "HIGH", "service_stack": ["APM", "CI Visibility", "Code Coverage", "Database Monitoring"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-30 16:32:44 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-06-30 15:36:04 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-30 15:06:00 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-06-30 14:57:57 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-06-30 14:36:22 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-06-30 14:28:49 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-06-30 13:54:31 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-06-30 13:51:54 UTC] Datadog SRE (Investigating): We are currently investigating an issue affecting CI Visibility, Test Optimization, Code Coverage, Software Delivery, Preemptive Alerting, Session Replay, RUM Explorer, Agent Observability, Database Monitoring, Event Correlation, Error Tracking, and all Security products in our US1 datacenter. As a result, some users may experience delays in data processing and errors when using affected products. Our engineering teams have identified the issue and are actively working on a resolution.\n\nOur engineering teams are actively working to resolve the issue, and we'll follow up with more information shortly. Please let us know if you have any questions or need anything else in the meantime.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to work on a fix for this issue. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are continuing to investigate this issue. We are continuing to investigate this issue. We are currently investigating an issue affecting CI Visibility, Test Optimization, Code Coverage, Software", "breaking_config_code": "# Incident architectural state during Delayed data processing and errors in multiple products\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"CI Visibility\", \"Code Coverage\", \"Database Monitoring\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/5snql687z9c4", "metadata": {"raw_id": "71vvxf0rxxnz", "status": "resolved", "resolved_at": "2026-06-30T16:32:44.628-04:00"}}
{"incident_id": "INC-2026-DATADOG-41jdllgc", "company": "Datadog", "date": "2026-06-30", "title": "Delayed Monitors Notifications", "severity": "HIGH", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-30 07:18:50 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-06-30 07:11:47 UTC] Datadog SRE (Monitoring): We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.\n[2026-06-30 06:53:02 UTC] Datadog SRE (Identified): We have identified the underlying issue and are working on a fix.\nIt is important to note that no data has been lost, and notifications will be caught up once the service is operational again.\n[2026-06-30 06:35:02 UTC] Datadog SRE (Investigating): We are investigating delays in Monitors Notifications, which began at 09:52 UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved. We have identified the underlying issue and are working on a fix.\nIt is important to note that no data has been lost, and notifications will be caught up once the service is operational again. We are investigating delays in Monitors Notifications, which began at 09:52 UTC.", "breaking_config_code": "# Incident architectural state during Delayed Monitors Notifications\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/hsz1r8ww26gn", "metadata": {"raw_id": "41jdllgcbk9s", "status": "resolved", "resolved_at": "2026-06-30T07:18:50.339-04:00"}}
{"incident_id": "INC-2026-DATADOG-29t1p0vx", "company": "Datadog", "date": "2026-06-26", "title": "Delayed APM Trace Metrics", "severity": "MEDIUM", "service_stack": ["Datadog Ingestion", "APM", "Metrics Agent", "Kafka"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-06-26 09:45:37 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-06-26 09:41:24 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-26 09:38:59 UTC] Datadog SRE (Identified): We have identified increased latency processing APM Trace Metrics and are working on a fix.\nAs a result of this issue, some users may see delayed APM Trace Metrics since 13:07 UTC.\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally..", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We have identified increased latency processing APM Trace Metrics and are working on a fix.\nAs a result of this issue, some users may see delayed APM Trace Metrics since 13:07 UTC.\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other mo", "breaking_config_code": "# Incident architectural state during Delayed APM Trace Metrics\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Datadog Ingestion\", \"APM\", \"Metrics Agent\", \"Kafka\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Datadog Ingestion cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/w6292y3bqkk1", "metadata": {"raw_id": "29t1p0vx8sjz", "status": "resolved", "resolved_at": "2026-06-26T09:45:37.493-04:00"}}
{"incident_id": "INC-2026-DATADOG-yx8jxssy", "company": "Datadog", "date": "2026-06-25", "title": "Delayed CI Visibility data", "severity": "MEDIUM", "service_stack": ["CI Visibility", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-25 19:32:26 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-06-25 19:24:22 UTC] Datadog SRE (Identified): We have identified the underlying issue and are working on a fix.\n\nIt is important to note that no data has been lost, and it will be backfilled and available once the service is operational again.\n[2026-06-25 19:23:01 UTC] Datadog SRE (Investigating): We are investigating increased latency processing CI Visibility data.\n\nAs a result of this issue, some users may see delays with pipeline executions.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We have identified the underlying issue and are working on a fix.\n\nIt is important to note that no data has been lost, and it will be backfilled and available once the service is operational again. We are investigating increased latency processing CI Visibility data.\n\nAs a result of this issue, some users may see delays with pipeline executions.", "breaking_config_code": "# Incident architectural state during Delayed CI Visibility data\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"CI Visibility\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on CI Visibility cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/kzsp8r6t4847", "metadata": {"raw_id": "yx8jxssylc2v", "status": "resolved", "resolved_at": "2026-06-25T19:32:26.545-04:00"}}
{"incident_id": "INC-2026-DATADOG-z9tr62bm", "company": "Datadog", "date": "2026-06-22", "title": "Metrics Queries", "severity": "HIGH", "service_stack": ["Metrics and Infra Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-06-22 18:41:36 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-06-22 18:37:25 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-22 18:28:56 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-06-22 18:09:59 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-06-22 17:43:42 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-06-22 17:27:41 UTC] Datadog SRE (Investigating): We are currently investigating elevated latency on metrics queries. We will provide an update as soon as possible.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to investigate this issue. We are continuing to investigate this issue. We are continuing to investigate this issue. We are currently investigating elevated latency on metrics queries. We will provide an update as soon as possible.", "breaking_config_code": "# Incident architectural state during Metrics Queries\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/z9s5hk7jc45c", "metadata": {"raw_id": "z9tr62bmp8v3", "status": "resolved", "resolved_at": "2026-06-22T18:41:36.494-04:00"}}
{"incident_id": "INC-2026-DATADOG-7l0kwdnv", "company": "Datadog", "date": "2026-06-18", "title": "Delayed Events", "severity": "MEDIUM", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-06-18 12:33:28 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-06-18 12:22:43 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-18 12:13:18 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Events.\nAs a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally..", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are investigating increased latency processing Events.\nAs a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors ", "breaking_config_code": "# Incident architectural state during Delayed Events\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/tdw3spf8slj1", "metadata": {"raw_id": "7l0kwdnv43j8", "status": "resolved", "resolved_at": "2026-06-18T12:33:28.910-04:00"}}
{"incident_id": "INC-2026-DATADOG-3fnvmf6k", "company": "Datadog", "date": "2026-06-12", "title": "Delayed Evaluation", "severity": "MEDIUM", "service_stack": ["APM", "Metrics and Infra Monitoring", "Monitors", "Datadog Ingestion"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-06-12 15:39:44 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-06-12 15:23:41 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-12 15:08:04 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue. During this time, the following components are affected:\n\nMonitor evaluation\nMetrics and Infra Monitoring\nAPM metrics\nEstimated usage metrics\n[2026-06-12 15:01:17 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-06-12 14:39:16 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-06-12 14:30:46 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-06-12 13:59:27 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-06-12 13:12:28 UTC] Datadog SRE (Identified): We are investigating delays in monitor evaluation, which began at 16:10 UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to work on a fix for this issue. During this time, the following components are affected:\n\nMonitor evaluation\nMetrics and Infra Monitoring\nAPM metrics\nEstimated usage metrics We are continuing to work on a fix for this issue. We are continuing to work on a fix for this issue. We are continuing to work on a fix for this issue. We are co", "breaking_config_code": "# Incident architectural state during Delayed Evaluation\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"Metrics and Infra Monitoring\", \"Monitors\", \"Datadog Ingestion\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/j0xmm8v17tmx", "metadata": {"raw_id": "3fnvmf6kckds", "status": "resolved", "resolved_at": "2026-06-12T15:39:44.126-04:00"}}
{"incident_id": "INC-2026-DATADOG-p0gz2w4n", "company": "Datadog", "date": "2026-06-08", "title": "Increased latency across multiple products", "severity": "MEDIUM", "service_stack": ["Cloud Cost Management", "Cloud Network Monitoring", "Cloud Security Management", "Database Monitoring"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-06-08 08:59:27 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-06-08 08:21:47 UTC] Datadog SRE (Monitoring): We are continuing to monitor the fix deployed earlier.\nWe will provide another update once the issue is fully resolved.\n[2026-06-08 07:21:57 UTC] Datadog SRE (Monitoring): We have deployed a fix and we are monitoring the results.\n[2026-06-08 07:05:03 UTC] Datadog SRE (Identified): We are investigating and have identified a fix for increased latency across multiple products. As a result of this issue, some users may see delays in data across the platform.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We are continuing to monitor the fix deployed earlier.\nWe will provide another update once the issue is fully resolved. We have deployed a fix and we are monitoring the results. We are investigating and have identified a fix for increased latency across multiple products. As a result of this issue, some users may see delays in data across the platform.", "breaking_config_code": "# Incident architectural state during Increased latency across multiple products\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Cloud Cost Management\", \"Cloud Network Monitoring\", \"Cloud Security Management\", \"Database Monitoring\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloud Cost Management cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/k3z1l9vwjhkp", "metadata": {"raw_id": "p0gz2w4ng7hp", "status": "resolved", "resolved_at": "2026-06-08T08:59:27.139-04:00"}}
{"incident_id": "INC-2026-DATADOG-xqyrslhj", "company": "Datadog", "date": "2026-05-15", "title": "Azure Metrics Reporting", "severity": "CRITICAL", "service_stack": ["Metrics and Infra Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-05-15 23:43:01 UTC] Datadog SRE (Resolved): This incident has been resolved and Azure metrics are reporting as expected.\n[2026-05-15 23:27:27 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-05-15 23:09:05 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-05-15 22:40:11 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-05-15 22:17:25 UTC] Datadog SRE (Investigating): We are investigating an issue submitting Azure metrics.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved and Azure metrics are reporting as expected. A fix has been implemented and we are monitoring the results. We are continuing to work on a fix for this issue. The issue has been identified and a fix is being implemented. We are investigating an issue submitting Azure metrics.", "breaking_config_code": "# Incident architectural state during Azure Metrics Reporting\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/l0b8n3g0ysky", "metadata": {"raw_id": "xqyrslhjs303", "status": "resolved", "resolved_at": "2026-05-15T23:43:01.802-04:00"}}
{"incident_id": "INC-2026-DATADOG-shjkvbwy", "company": "Datadog", "date": "2026-05-14", "title": "Delayed Metric Loading", "severity": "MEDIUM", "service_stack": ["Metrics and Infra Monitoring", "Monitors", "Datadog Ingestion", "APM"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION"], "symptom_logs": "[2026-05-14 15:48:24 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-05-14 14:48:48 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-05-14 14:24:38 UTC] Datadog SRE (Investigating): We are investigating increased latency querying Metrics. As a result of this issue, some users may experience delays loading graphs in dashboards and notebooks, and delayed monitor evaluations.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are investigating increased latency querying Metrics. As a result of this issue, some users may experience delays loading graphs in dashboards and notebooks, and delayed monitor evaluations.", "breaking_config_code": "# Incident architectural state during Delayed Metric Loading\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Monitors\", \"Datadog Ingestion\", \"APM\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/sskp2jtfd9sj", "metadata": {"raw_id": "shjkvbwy06nl", "status": "resolved", "resolved_at": "2026-05-14T15:48:24.589-04:00"}}
{"incident_id": "INC-2026-DATADOG-j4v5lc1l", "company": "Datadog", "date": "2026-05-13", "title": "Degraded Web Application Performance", "severity": "MEDIUM", "service_stack": ["APM", "Database Monitoring", "Datadog Ingestion", "Metrics Agent"], "categories": ["DATABASE_DEGRADATION", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-05-13 11:53:19 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-05-13 11:36:42 UTC] Datadog SRE (Monitoring): We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.\n[2026-05-13 11:16:27 UTC] Datadog SRE (Investigating): We are investigating degraded performance in the Database Monitoring pages and APM service pages.\n\nDuring this time, some customers may be experiencing:\n- The DBM database list page failing to load or displaying zero databases\n- 503 errors when attempting to access database instance views\n- Inability to view or interact with Database Monitoring data in our US1 datacenter\n- The APM service page failing to load", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved. We are investigating degraded performance in the Database Monitoring pages and APM service pages.\n\nDuring this time, some customers may be experiencing:\n- The DBM database list page failing to load or displaying zero databases\n- 503 errors when attempting to access database instance views\n- In", "breaking_config_code": "# Incident architectural state during Degraded Web Application Performance\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"Database Monitoring\", \"Datadog Ingestion\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/cwzjd95rnzhd", "metadata": {"raw_id": "j4v5lc1lvgf1", "status": "resolved", "resolved_at": "2026-05-13T11:53:19.730-04:00"}}
{"incident_id": "INC-2026-DATADOG-wjrkhvg9", "company": "Datadog", "date": "2026-05-07", "title": "Delayed Monitors Notifications", "severity": "CRITICAL", "service_stack": ["APM", "CI Visibility", "Error Tracking", "Log Management"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-05-08 10:07:35 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-05-08 02:21:58 UTC] Datadog SRE (Monitoring): We have identified upstream provider issues. Metrics, Logs, APM, RUM and CI visibility data are being processed normally for all customers. Alerting is also functional.\nWe are monitoring the situation.\nhttps://health.aws.amazon.com/health/status\n[2026-05-08 01:44:23 UTC] Datadog SRE (Identified): We have identified upstream provider issues. Metrics, Logs, APM and RUM data are being processed normally for all customers. Alerting is also functional. There are still processing delays for CI visibility.\nWe are monitoring the situation.\nhttps://health.aws.amazon.com/health/status\n[2026-05-08 01:30:42 UTC] Datadog SRE (Identified): We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are continuing to work on a fix.\nhttps://health.aws.amazon.com/health/status\n\nFor metrics, distribution metrics and point metrics are being processed normally for all customers.\n[2026-05-08 00:48:58 UTC] Datadog SRE (Identified): We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are continuing to work on a fix.\nhttps://health.aws.amazon.com/health/status\n\nFor metrics, distribution metrics and point metrics are being processed normally for all customers.\n[2026-05-08 00:13:10 UTC] Datadog SRE (Identified): We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are continuing to work on a fix.\nhttps://health.aws.amazon.com/health/status\n\nFor metrics, distribution metrics and point metrics are being processed normally for all customers.\n[2026-05-07 22:59:28 UTC] Datadog SRE (Identified): We have identified due to upstream provider issues, we are continuing to see unavailability of telemetry data coming from AWS into Datadog. We are continuing to work on a fix.\nhttps://health.aws.amazon.com/health/status\n\nFor metrics we are still seeing delays in distribution metrics. Counts, rates and gauge metrics are being processed normally for most customers\n[2026-05-07 22:16:54 UTC] Datadog SRE (Identified): We have identified due to upstream provider issues, we are continuing to see unavailability of telemetry data coming from AWS into Datadog. We are continuing to work on a fix.\n\nhttps://health.aws.amazon.com/health/status", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We have identified upstream provider issues. Metrics, Logs, APM, RUM and CI visibility data are being processed normally for all customers. Alerting is also functional.\nWe are monitoring the situation.\nhttps://health.aws.amazon.com/health/status We have identified upstream provider issues. Metrics, Logs, APM and RUM data are being processed normally for all customers. Alerting is also functional. There are still p", "breaking_config_code": "# Incident architectural state during Delayed Monitors Notifications\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"CI Visibility\", \"Error Tracking\", \"Log Management\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rbj54mc4nhgs", "metadata": {"raw_id": "wjrkhvg9ydc1", "status": "resolved", "resolved_at": "2026-05-08T10:07:35.466-04:00"}}
{"incident_id": "INC-2026-DATADOG-s1mcpzcx", "company": "Datadog", "date": "2026-05-05", "title": "Delays in APM-based Monitor Notifications", "severity": "MEDIUM", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-05-05 15:52:31 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-05-05 14:44:24 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-05-05 14:29:16 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-05-05 14:14:03 UTC] Datadog SRE (Investigating): We’re currently investigating an issue affecting APM monitor delays in our US1 datacenter. As a result, some users may experience delayed alert triggering or temporary inconsistencies in monitors.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We’re currently investigating an issue affecting APM monitor delays in our US1 datacenter. As a result, some users may experience delayed alert triggering or temporary inconsistencies in monitors.", "breaking_config_code": "# Incident architectural state during Delays in APM-based Monitor Notifications\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rww57bn61jkp", "metadata": {"raw_id": "s1mcpzcxhr9x", "status": "resolved", "resolved_at": "2026-05-05T15:52:31.844-04:00"}}
{"incident_id": "INC-2026-DATADOG-dw41jpjj", "company": "Datadog", "date": "2026-04-30", "title": "Elevated Error Rates for Metrics Queries", "severity": "HIGH", "service_stack": ["Metrics and Infra Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-04-30 21:19:56 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-04-30 21:09:25 UTC] Datadog SRE (Monitoring): We have deployed a fix and we are monitoring the results.\nWe will provide another update once the service is fully operational.\n[2026-04-30 20:45:48 UTC] Datadog SRE (Investigating): We are actively investigating elevated error rates for Metrics Queries.\nAs a result of this issue, some users may see errors with metrics graphs on the web application or API.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We have deployed a fix and we are monitoring the results.\nWe will provide another update once the service is fully operational. We are actively investigating elevated error rates for Metrics Queries.\nAs a result of this issue, some users may see errors with metrics graphs on the web application or API.", "breaking_config_code": "# Incident architectural state during Elevated Error Rates for Metrics Queries\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/17n4grhvbmjt", "metadata": {"raw_id": "dw41jpjjghhs", "status": "resolved", "resolved_at": "2026-04-30T21:19:56.916-04:00"}}
{"incident_id": "INC-2026-DATADOG-0p99flrd", "company": "Datadog", "date": "2026-04-24", "title": "Delays in AWS and Azure cloud integration metrics ingestion", "severity": "HIGH", "service_stack": ["Metrics and Infra Monitoring", "Monitors", "Datadog Ingestion", "APM"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-04-24 12:50:36 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-04-24 12:44:10 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-04-24 12:43:50 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-04-24 12:27:20 UTC] Datadog SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Delays in AWS and Azure cloud integration metrics ingestion\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Monitors\", \"Datadog Ingestion\", \"APM\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/xw01xpvggm3n", "metadata": {"raw_id": "0p99flrd9mln", "status": "resolved", "resolved_at": "2026-04-24T12:50:36.003-04:00"}}
{"incident_id": "INC-2026-DATADOG-7ht7d7xs", "company": "Datadog", "date": "2026-04-15", "title": "Delayed Metrics", "severity": "HIGH", "service_stack": ["Metrics and Infra Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-04-15 20:37:38 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-04-15 20:32:12 UTC] Datadog SRE (Monitoring): We have resolved the lag in distribution metrics and we are monitoring the results.\nWe will provide another update once the issue is fully resolved.\n[2026-04-15 19:54:58 UTC] Datadog SRE (Investigating): We are still investigating increased latency processing Distribution Metrics, delays have gone down but have not fully recovered.\n[2026-04-15 19:16:37 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Distribution Metrics.\nAs a result of this issue, some users may see delays or gaps for distribution metrics on graphs.\n\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally.\n[2026-04-15 18:38:22 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Metrics.\nAs a result of this issue, some users may see delays or gaps for metrics on graphs.\n\nTo prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We have resolved the lag in distribution metrics and we are monitoring the results.\nWe will provide another update once the issue is fully resolved. We are still investigating increased latency processing Distribution Metrics, delays have gone down but have not fully recovered. We are investigating increased latency processing Distribution Metrics.\nAs a result of this issue, some users may see delays or gaps for d", "breaking_config_code": "# Incident architectural state during Delayed Metrics\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/32s2j42tn8xz", "metadata": {"raw_id": "7ht7d7xsnbhy", "status": "resolved", "resolved_at": "2026-04-15T20:37:38.862-04:00"}}
{"incident_id": "INC-2026-DATADOG-q2njm9l0", "company": "Datadog", "date": "2026-04-10", "title": "Notifications to Pagerduty, VictorOps, Slack, Webhook, Microsoft Teams and OpsGenie are not delivered", "severity": "HIGH", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-04-10 16:59:49 UTC] Datadog SRE (Resolved): Between approximately 9:42 AM and 10:38 AM ET on April 10, we observed delivery failures for customers in the US1, AP1, and AP2 regions. During this window, notifications to the following integrations were delayed or temporarily undelivered:\n\n• PagerDuty\n• Slack\n• Microsoft Teams\n• Webhooks\n• Jira\n• ServiceNow\n• OpsGenie\n• VictorOps\n• BigPanda\n• Zendesk\n• Sumologic\n\nAll delayed notifications have been replayed with the following exceptions: PagerDuty pages and Slack notifications queued during the outage window were not replayed, as they were no longer actionable at the time of recovery. Webhook notifications will be reprocessed and delivered at a later date.\n\nNo monitoring data was lost during this incident. Monitor evaluations continued normally — only the delivery of triggered notifications was affected.\n\nThank you for your patience.\n[2026-04-10 16:13:41 UTC] Datadog SRE (Monitoring): Webhooks and Slack notifications are still catching up.\n[2026-04-10 15:44:24 UTC] Datadog SRE (Monitoring): Webhooks and Slack notifications are still catching up.\n[2026-04-10 15:02:16 UTC] Datadog SRE (Monitoring): Webhooks and Slack notifications are still catching up.\n[2026-04-10 14:33:12 UTC] Datadog SRE (Monitoring): Notifications for ServiceNow and Microsoft Teams are now caught up. Webhooks and Slack notifications are still catching up.\n[2026-04-10 13:37:45 UTC] Datadog SRE (Monitoring): Notifications for JIRA are now caught up.\n[2026-04-10 13:12:44 UTC] Datadog SRE (Monitoring): Notifications for Opsgenie, VictorOps, BigPanda, Zendesk, and Sumologic are caught up. Webhooks, Microsoft Teams, Slack, JIRA, and ServiceNow are still catching up.\n[2026-04-10 12:15:54 UTC] Datadog SRE (Monitoring): We are still catching-up on past notifications that may have been delayed.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: Between approximately 9:42 AM and 10:38 AM ET on April 10, we observed delivery failures for customers in the US1, AP1, and AP2 regions. During this window, notifications to the following integrations were delayed or temporarily undelivered:\n\n• PagerDuty\n• Slack\n• Microsoft Teams\n• Webhooks\n• Jira\n• ServiceNow\n• OpsGenie\n• VictorOps\n• BigPanda\n• Zendesk\n• Sumologic\n\nAll delayed notifications have been replayed with the following exceptions: Pager", "breaking_config_code": "# Incident architectural state during Notifications to Pagerduty, VictorOps, Slack, Webhook, Microsoft Teams and OpsGenie are not delivered\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/18986pkc2dgr", "metadata": {"raw_id": "q2njm9l08tjb", "status": "resolved", "resolved_at": "2026-04-10T16:59:49.000-04:00"}}
{"incident_id": "INC-2026-DATADOG-y1trpqc5", "company": "Datadog", "date": "2026-03-27", "title": "Delayed Traces in APM Trace Search", "severity": "HIGH", "service_stack": ["APM", "Datadog Ingestion", "Metrics Agent", "Kafka"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-03-27 15:30:04 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-03-27 15:21:54 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-27 15:17:56 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-03-27 14:57:08 UTC] Datadog SRE (Investigating): We are investigating increased latency in processing and storing Traces in APM.\nAs a result of this issue, some users may see missing or delayed traces in APM Trace Search since 5pm UTC. They may also experience delay in APM trace-based monitors.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are investigating increased latency in processing and storing Traces in APM.\nAs a result of this issue, some users may see missing or delayed traces in APM Trace Search since 5pm UTC. They may also experience delay in APM trace-based monitors.", "breaking_config_code": "# Incident architectural state during Delayed Traces in APM Trace Search\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"Datadog Ingestion\", \"Metrics Agent\", \"Kafka\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4qqxn4k2w7n5", "metadata": {"raw_id": "y1trpqc54210", "status": "resolved", "resolved_at": "2026-03-27T15:30:04.932-04:00"}}
{"incident_id": "INC-2026-DATADOG-1qdv7gx8", "company": "Datadog", "date": "2026-03-26", "title": "Delayed Monitors Notifications", "severity": "HIGH", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-03-26 15:56:35 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-03-26 15:42:31 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-26 15:07:44 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-03-26 14:38:40 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-03-26 13:28:57 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-03-26 12:48:29 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-03-26 12:11:46 UTC] Datadog SRE (Investigating): We are continuing to investigate delays in monitor notifications.\n[2026-03-26 11:32:11 UTC] Datadog SRE (Investigating): We are still continuing investigating delays in monitor notifications that started at 12:00 UTC. We've identified the root cause and are working on a fix.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to work on a fix for this issue. We are continuing to work on a fix for this issue. We are continuing to work on a fix for this issue. The issue has been identified and a fix is being implemented. We are continuing to investigate delays in monitor notifications. We are still continuing investigating delays in monitor notifications that", "breaking_config_code": "# Incident architectural state during Delayed Monitors Notifications\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/vl9tsrk9z2ld", "metadata": {"raw_id": "1qdv7gx89vwv", "status": "resolved", "resolved_at": "2026-03-26T15:56:35.378-04:00"}}
{"incident_id": "INC-2026-DATADOG-j5zpb9ph", "company": "Datadog", "date": "2026-03-18", "title": "Intermittent \"No Data\" Status for Monitors", "severity": "HIGH", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-03-18 22:53:46 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-03-18 22:39:52 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-18 22:04:58 UTC] Datadog SRE (Investigating): We are continuing to investigate the issue and will provide updates as available.\n[2026-03-18 21:27:45 UTC] Datadog SRE (Investigating): We are continuing to investigate the issue and will provide updates as available.\n[2026-03-18 20:54:23 UTC] Datadog SRE (Investigating): We are investigating an issue causing some metric monitors to intermittently report \"No Data\" status. This primarily affects monitors based on distribution metrics. Monitor alerting may be unreliable during this time. We are actively investigating and will provide updates as available.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to investigate the issue and will provide updates as available. We are continuing to investigate the issue and will provide updates as available. We are investigating an issue causing some metric monitors to intermittently report \"No Data\" status. This primarily affects monitors based on distribution metrics. Monitor alerting may be un", "breaking_config_code": "# Incident architectural state during Intermittent \"No Data\" Status for Monitors\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/43kkcl1tqrrk", "metadata": {"raw_id": "j5zpb9phy9m6", "status": "resolved", "resolved_at": "2026-03-18T22:53:46.258-04:00"}}
{"incident_id": "INC-2026-DATADOG-9ksfbdb5", "company": "Datadog", "date": "2026-03-13", "title": "Web Application Not Loading", "severity": "CRITICAL", "service_stack": ["Web Application", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-03-13 06:30:25 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-03-13 06:05:28 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-13 06:00:07 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-03-13 05:52:37 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-03-13 05:32:12 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-03-13 05:27:16 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-03-13 05:26:35 UTC] Datadog SRE (Investigating): We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are continuing to investigate this issue. We are continuing to investigate this issue. We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.", "breaking_config_code": "# Incident architectural state during Web Application Not Loading\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Web Application\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Web Application cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/mfp6qzq5bd51", "metadata": {"raw_id": "9ksfbdb59mtn", "status": "resolved", "resolved_at": "2026-03-13T06:30:25.499-04:00"}}
{"incident_id": "INC-2026-DATADOG-qqb6y9g8", "company": "Datadog", "date": "2026-02-23", "title": "Delayed RUM data", "severity": "MEDIUM", "service_stack": ["Cloud Cost Management", "RUM", "Datadog Ingestion", "APM"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-02-24 02:08:31 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-02-24 00:52:57 UTC] Datadog SRE (Monitoring): We have deployed a fix and we are monitoring the results.\nWe will provide another update once the issue is fully resolved.\n[2026-02-24 00:29:47 UTC] Datadog SRE (Identified): We have identified the underlying issue and are working on a fix.\nIt is important to note that no data has been lost, and it will be backfilled and available once the service is operational again.\n[2026-02-23 23:31:54 UTC] Datadog SRE (Investigating): We are investigating increased latency processing RUM data.\nAs a result of this issue, some users may see gaps or delays in RUM graphs as well as empty or partial query results on RUM Sessions, RUM Analytics, RUM Application, and Error Tracking pages.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We have deployed a fix and we are monitoring the results.\nWe will provide another update once the issue is fully resolved. We have identified the underlying issue and are working on a fix.\nIt is important to note that no data has been lost, and it will be backfilled and available once the service is operational again. We are investigating increased latency processing RUM data.\nAs a result of this issue, some users", "breaking_config_code": "# Incident architectural state during Delayed RUM data\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Cloud Cost Management\", \"RUM\", \"Datadog Ingestion\", \"APM\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloud Cost Management cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/f7nly8tc2198", "metadata": {"raw_id": "qqb6y9g81rw6", "status": "resolved", "resolved_at": "2026-02-24T02:08:31.512-05:00"}}
{"incident_id": "INC-2026-DATADOG-l3xqsgb1", "company": "Datadog", "date": "2026-02-18", "title": "Monitors - Delayed Evaluation for Multiple Products", "severity": "MEDIUM", "service_stack": ["APM", "Data Streams Monitoring", "Log Management", "Metrics and Infra Monitoring"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-02-18 15:37:18 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-02-18 14:30:23 UTC] Datadog SRE (Monitoring): We are investigating delays in a subset of Distribution Metrics and Monitor Evaluations, which began at 18:33 UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We are investigating delays in a subset of Distribution Metrics and Monitor Evaluations, which began at 18:33 UTC.", "breaking_config_code": "# Incident architectural state during Monitors - Delayed Evaluation for Multiple Products\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"Data Streams Monitoring\", \"Log Management\", \"Metrics and Infra Monitoring\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/c6d05hsplhbv", "metadata": {"raw_id": "l3xqsgb18fvy", "status": "resolved", "resolved_at": "2026-02-18T15:37:18.980-05:00"}}
{"incident_id": "INC-2026-DATADOG-vkqm21bf", "company": "Datadog", "date": "2026-02-11", "title": "Delayed Traces in APM", "severity": "MEDIUM", "service_stack": ["APM", "Metrics and Infra Monitoring", "Datadog Ingestion", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-02-11 21:08:46 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-02-11 20:49:18 UTC] Datadog SRE (Monitoring): The remaining impact is limited to AWS Streams metrics. We are continuing to monitor for any further issues.\n[2026-02-11 20:32:45 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-02-11 20:20:35 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-02-11 19:57:47 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Traces in APM Trace Search and AWS streams metrics.\nAs a result of this issue, some users may see missing or delayed traces in APM Trace Search, and delayed AWS stream metrics since 00:13 UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. The remaining impact is limited to AWS Streams metrics. We are continuing to monitor for any further issues. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are investigating increased latency processing Traces in APM Trace Search and AWS streams metrics.\nAs a result of this issue, some users may see missing or delayed traces in APM Tra", "breaking_config_code": "# Incident architectural state during Delayed Traces in APM\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/19l6tqc8m1b2", "metadata": {"raw_id": "vkqm21bfss9c", "status": "resolved", "resolved_at": "2026-02-11T21:08:46.715-05:00"}}
{"incident_id": "INC-2026-DATADOG-g5vw545y", "company": "Datadog", "date": "2026-02-11", "title": "Delayed Traces in APM Trace Search", "severity": "MEDIUM", "service_stack": ["APM", "Monitors", "Datadog Ingestion", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-02-11 18:44:55 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-02-11 18:28:55 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-02-11 17:28:31 UTC] Datadog SRE (Identified): Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed. Distribution Metrics monitors were delayed between 21:35 and 22:15 UTC\n[2026-02-11 16:51:27 UTC] Datadog SRE (Identified): Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed and Distribution Metrics monitors are delayed starting from 21:35 UTC\n[2026-02-11 16:18:40 UTC] Datadog SRE (Identified): Teams have identified the issue and are working to mitigate at this time\n[2026-02-11 15:56:50 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Traces in APM Trace Search.\nAs a result of this issue, some users may see missing or delayed traces in APM Trace Search and delayed APM Trace Monitors since 21:30 UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed. Distribution Metrics monitors were delayed between 21:35 and 22:15 UTC Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed and Distributio", "breaking_config_code": "# Incident architectural state during Delayed Traces in APM Trace Search\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"Monitors\", \"Datadog Ingestion\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4znpw24vxbbg", "metadata": {"raw_id": "g5vw545yn7vt", "status": "resolved", "resolved_at": "2026-02-11T18:44:55.420-05:00"}}
{"incident_id": "INC-2026-DATADOG-g545g04n", "company": "Datadog", "date": "2026-02-05", "title": "Delays in Monitor Evaluations", "severity": "HIGH", "service_stack": ["APM", "Application Security Management", "Cloud SIEM", "Incident Response"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-02-05 12:43:22 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-02-05 12:23:31 UTC] Datadog SRE (Monitoring): We have observed full recovery of monitors and will continue to monitor\n[2026-02-05 12:01:20 UTC] Datadog SRE (Identified): We are observing recovery for the vast majority of monitors and are continuing to work on a full fix for this issue.\n[2026-02-05 11:50:36 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-02-05 11:31:36 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-02-05 11:28:25 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-02-05 11:11:17 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-02-05 11:10:40 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We have observed full recovery of monitors and will continue to monitor We are observing recovery for the vast majority of monitors and are continuing to work on a full fix for this issue. We are continuing to work on a fix for this issue. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are continuing to investigate this issue. We are continuing to inve", "breaking_config_code": "# Incident architectural state during Delays in Monitor Evaluations\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"Application Security Management\", \"Cloud SIEM\", \"Incident Response\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/kzxxld69ftmr", "metadata": {"raw_id": "g545g04n9xkr", "status": "resolved", "resolved_at": "2026-02-05T12:43:22.857-05:00"}}
{"incident_id": "INC-2026-DATADOG-1hmvg62s", "company": "Datadog", "date": "2026-01-29", "title": "Delayed Distribution Monitors Evaluations", "severity": "CRITICAL", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-01-29 14:55:05 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-01-29 14:09:32 UTC] Datadog SRE (Monitoring): We are continuing to monitor the fix and will continue to provide regular updates.\n[2026-01-29 13:36:47 UTC] Datadog SRE (Monitoring): We have deployed a fix and we are monitoring the results. We will continue to provide regular updates.\n[2026-01-29 13:06:38 UTC] Datadog SRE (Identified): We are continuing to work on a fix for this issue. It is important to note that no data has been lost, and evaluations will be caught up once the service is operational again.\n[2026-01-29 12:46:31 UTC] Datadog SRE (Identified): We have identified the underlying issue and are working on a fix. It is important to note that no data has been lost, and evaluations will be caught up once the service is operational again.\n[2026-01-29 12:35:31 UTC] Datadog SRE (Investigating): We are investigating delays in Monitors evaluations, which began at 17:15 UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. We are continuing to monitor the fix and will continue to provide regular updates. We have deployed a fix and we are monitoring the results. We will continue to provide regular updates. We are continuing to work on a fix for this issue. It is important to note that no data has been lost, and evaluations will be caught up once the service is operational again. We have identified the underlying issue and are working", "breaking_config_code": "# Incident architectural state during Delayed Distribution Monitors Evaluations\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/kywknq2z0ht1", "metadata": {"raw_id": "1hmvg62sxmjp", "status": "resolved", "resolved_at": "2026-01-29T14:55:05.164-05:00"}}
{"incident_id": "INC-2026-DATADOG-6vndlbw8", "company": "Datadog", "date": "2026-01-28", "title": "Monitors - Delayed Evaluation", "severity": "MEDIUM", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-01-28 18:36:23 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-01-28 18:13:40 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-01-28 17:08:16 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-01-28 16:21:52 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-01-28 16:18:31 UTC] Datadog SRE (Investigating): We are investigating delays in service checks monitors evaluation, which began at 20:26 1/28/2026 UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are investigating delays in service checks monitors evaluation, which began at 20:26 1/28/2026 UTC.", "breaking_config_code": "# Incident architectural state during Monitors - Delayed Evaluation\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/55l2cqg035fj", "metadata": {"raw_id": "6vndlbw8vzqp", "status": "resolved", "resolved_at": "2026-01-28T18:36:23.179-05:00"}}
{"incident_id": "INC-2026-DATADOG-0vy6kj9t", "company": "Datadog", "date": "2026-01-22", "title": "Web Application Not Loading", "severity": "CRITICAL", "service_stack": ["APM", "App Builder", "Application Security Management", "Application Vulnerability Management"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-01-22 14:27:45 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2026-01-22 14:13:05 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-01-22 14:01:39 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2026-01-22 13:51:22 UTC] Datadog SRE (Investigating): We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.\n\nPlease note that data processing and alerts are not affected by this incident.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to investigate this issue. We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.\n\nPlease note that data processing and alerts are not affected by this incident.", "breaking_config_code": "# Incident architectural state during Web Application Not Loading\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"APM\", \"App Builder\", \"Application Security Management\", \"Application Vulnerability Management\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on APM cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/qzwqj368qbvk", "metadata": {"raw_id": "0vy6kj9tgmt6", "status": "resolved", "resolved_at": "2026-01-22T14:27:45.914-05:00"}}
{"incident_id": "INC-2026-DATADOG-476hf8wn", "company": "Datadog", "date": "2026-01-18", "title": "Delayed Events", "severity": "MEDIUM", "service_stack": ["Metrics and Infra Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-01-18 09:24:41 UTC] Datadog SRE (Resolved): This incident is resolved. There's no more delay for the processing of Events, nor impact on the event stream, event based widgets and event based monitors.\n[2026-01-18 08:26:48 UTC] Datadog SRE (Identified): Recovery is in progress and the new estimated time of recovery would be 14h30 UTC.\n[2026-01-18 07:35:23 UTC] Datadog SRE (Identified): We have identified the issue and scaled up for recovery, with a recovery estimated to be around 14h30 UTC. We'll continue to give updates as recovery progresses.\n[2026-01-18 07:33:26 UTC] Datadog SRE (Identified): We are investigating increased latency processing Events.\nAs a result of this issue, some users may see delays or gaps in the event stream or for event based widgets or event based monitors.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident is resolved. There's no more delay for the processing of Events, nor impact on the event stream, event based widgets and event based monitors. Recovery is in progress and the new estimated time of recovery would be 14h30 UTC. We have identified the issue and scaled up for recovery, with a recovery estimated to be around 14h30 UTC. We'll continue to give updates as recovery progresses. We are investigating increased latency processin", "breaking_config_code": "# Incident architectural state during Delayed Events\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/w2k14cxk8th3", "metadata": {"raw_id": "476hf8wnc4l0", "status": "resolved", "resolved_at": "2026-01-18T09:24:41.174-05:00"}}
{"incident_id": "INC-2025-DATADOG-rxrmt186", "company": "Datadog", "date": "2025-12-12", "title": "Delayed Processes data", "severity": "HIGH", "service_stack": ["Metrics and Infra Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2025-12-12 18:43:52 UTC] Datadog SRE (Resolved): This incident has been resolved.\n[2025-12-12 18:31:07 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-12-12 17:41:03 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2025-12-12 16:53:21 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2025-12-12 16:49:44 UTC] Datadog SRE (Investigating): We are investigating increased latency processing Processes data.\nAs a result of this issue, some users may see delays or gaps for data based on Process Monitoring.\nTo prevent spurious alerts, we have temporarily disabled monitors based on this data.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are investigating increased latency processing Processes data.\nAs a result of this issue, some users may see delays or gaps for data based on Process Monitoring.\nTo prevent spurious alerts, we have temporarily disabled monitors based on this dat", "breaking_config_code": "# Incident architectural state during Delayed Processes data\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ppc0471xzd9w", "metadata": {"raw_id": "rxrmt186707r", "status": "resolved", "resolved_at": "2025-12-12T18:43:52.417-05:00"}}
{"incident_id": "INC-2025-DATADOG-c4gh438m", "company": "Datadog", "date": "2025-12-12", "title": "Delayed APM metric ingestion", "severity": "HIGH", "service_stack": ["Metrics and Infra Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2025-12-12 16:52:51 UTC] Datadog SRE (Resolved): All impact related to APM metrics has been resolved.  A separate incident has been created to track the remaining impact in live process data.\n[2025-12-12 15:53:22 UTC] Datadog SRE (Identified): We have identified the issue affecting ingestion delays in apm and process metrics and are working on recovery\n[2025-12-12 14:26:26 UTC] Datadog SRE (Investigating): We are currently investigating lag in ingesting apm and process metrics, which affects monitor evaluation and in some cases led to incorrect monitor alerts.\n[2025-12-12 13:55:53 UTC] Datadog SRE (Investigating): We are continuing to investigate this issue.\n[2025-12-12 13:37:34 UTC] Datadog SRE (Investigating): We are currently investigating lag in ingesting apm metrics, which affects monitor evaluation.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: All impact related to APM metrics has been resolved.  A separate incident has been created to track the remaining impact in live process data. We have identified the issue affecting ingestion delays in apm and process metrics and are working on recovery We are currently investigating lag in ingesting apm and process metrics, which affects monitor evaluation and in some cases led to incorrect monitor alerts. We are continuing to investigate this i", "breaking_config_code": "# Incident architectural state during Delayed APM metric ingestion\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/qwpxql6b48pl", "metadata": {"raw_id": "c4gh438m6pp3", "status": "resolved", "resolved_at": "2025-12-12T16:52:51.132-05:00"}}
{"incident_id": "INC-2025-DATADOG-xj87f6z9", "company": "Datadog", "date": "2025-12-09", "title": "Metrics data ingestion delayed and monitor evaluations degraded", "severity": "MEDIUM", "service_stack": ["Metrics and Infra Monitoring", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2025-12-09 16:08:28 UTC] Datadog SRE (Resolved): This incident has been resolved. Live data is being processed normally and gaps in distribution metrics on graphs will be backfilled within the next hour.\n[2025-12-09 16:00:18 UTC] Datadog SRE (Monitoring): Live distribution metrics are available and being evaluated for all monitors. Gaps in graphs from the beginning of the incident are in the process of being backfilled.\n[2025-12-09 15:36:13 UTC] Datadog SRE (Identified): The issue has been identified and a fix is being implemented.\n[2025-12-09 15:16:17 UTC] Datadog SRE (Investigating): We’re currently monitoring an issue causing delays in distribution metric processing in our US1 region.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. Live data is being processed normally and gaps in distribution metrics on graphs will be backfilled within the next hour. Live distribution metrics are available and being evaluated for all monitors. Gaps in graphs from the beginning of the incident are in the process of being backfilled. The issue has been identified and a fix is being implemented. We’re currently monitoring an issue causing delays in distributio", "breaking_config_code": "# Incident architectural state during Metrics data ingestion delayed and monitor evaluations degraded\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Metrics and Infra Monitoring\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Metrics and Infra Monitoring cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/5hqhsx3549dz", "metadata": {"raw_id": "xj87f6z9mm3w", "status": "resolved", "resolved_at": "2025-12-09T16:08:28.161-05:00"}}
{"incident_id": "INC-2025-DATADOG-cvdjtf81", "company": "Datadog", "date": "2025-11-19", "title": "Web Application Not Loading", "severity": "CRITICAL", "service_stack": ["Web Application", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-11-19 14:44:17 UTC] Datadog SRE (Resolved): This incident has been resolved as of 2:32PM ET.\n[2025-11-19 14:37:56 UTC] Datadog SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-11-19 14:28:03 UTC] Datadog SRE (Investigating): We continue investigating the issue with web application. Data processing and alerting remain operational.\n[2025-11-19 14:08:07 UTC] Datadog SRE (Investigating): We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved as of 2:32PM ET. A fix has been implemented and we are monitoring the results. We continue investigating the issue with web application. Data processing and alerting remain operational. We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.", "breaking_config_code": "# Incident architectural state during Web Application Not Loading\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Web Application\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Web Application cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/h30gbqqk6wgl", "metadata": {"raw_id": "cvdjtf81756n", "status": "resolved", "resolved_at": "2025-11-19T14:44:17.410-05:00"}}
{"incident_id": "INC-2025-DATADOG-29fsc4rh", "company": "Datadog", "date": "2025-11-18", "title": "Delayed Monitors Notifications", "severity": "MEDIUM", "service_stack": ["Monitors", "Datadog Ingestion", "APM", "Metrics Agent"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2025-11-18 08:53:58 UTC] Datadog SRE (Resolved): This incident has been resolved. Notification delays were only affecting our internal monitoring and were due to the ongoing Cloudflare incident: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7/.\n[2025-11-18 08:17:44 UTC] Datadog SRE (Investigating): We are investigating delays in RUM-based Monitors Notifications, which began at 11:30am UTC.", "root_cause_analysis": "Official investigation timeline recorded by Datadog engineering: This incident has been resolved. Notification delays were only affecting our internal monitoring and were due to the ongoing Cloudflare incident: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7/. We are investigating delays in RUM-based Monitors Notifications, which began at 11:30am UTC.", "breaking_config_code": "# Incident architectural state during Delayed Monitors Notifications\nservice_cluster:\n  provider: \"Datadog\"\n  impacted_components: [\"Monitors\", \"Datadog Ingestion\", \"APM\", \"Metrics Agent\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Datadog SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Monitors cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0r75b5ng1fc2", "metadata": {"raw_id": "29fsc4rhsscg", "status": "resolved", "resolved_at": "2025-11-18T08:53:58.019-05:00"}}
{"incident_id": "INC-2026-VERCEL-yy1sm6x5", "company": "Vercel", "date": "2026-09-28", "title": "Build failures and 500 errors for functions using Edge runtime", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-28 14:11:29 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-09-28 13:44:30 UTC] Vercel SRE (Monitoring): A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation.", "breaking_config_code": "# Incident architectural state during Build failures and 500 errors for functions using Edge runtime\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/p633qkgvpdsy", "metadata": {"raw_id": "yy1sm6x5l83q", "status": "resolved", "resolved_at": "2026-09-28T14:11:29.951Z"}}
{"incident_id": "INC-2026-VERCEL-5c1lswm6", "company": "Vercel", "date": "2026-09-18", "title": "Deployment stuck in initializing state", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-18 22:31:22 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-09-18 22:14:37 UTC] Vercel SRE (Monitoring): We have identified an issue causing deployments to get stuck in an initialized state, applied a fix, and are seeing signs of recovery for new deployments. We are continuing to monitor.\n[2026-09-18 21:36:09 UTC] Vercel SRE (Investigating): We are currently investigating an issue causing an elevated rate of deployments getting stuck in an initializing state. We will provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. We have identified an issue causing deployments to get stuck in an initialized state, applied a fix, and are seeing signs of recovery for new deployments. We are continuing to monitor. We are currently investigating an issue causing an elevated rate of deployments getting stuck in an initializing state. We will provide additional updates as they become available.", "breaking_config_code": "# Incident architectural state during Deployment stuck in initializing state\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/fx0fjwcpvdqr", "metadata": {"raw_id": "5c1lswm68bkg", "status": "resolved", "resolved_at": "2026-09-18T22:31:22.760Z"}}
{"incident_id": "INC-2026-VERCEL-bwkmw4hm", "company": "Vercel", "date": "2026-09-18", "title": "Elevated Errors Triggering Deployments", "severity": "HIGH", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-18 21:22:27 UTC] Vercel SRE (Resolved): The issue causing elevated errors triggering deployments has been resolved. \n\nExisting deployments and traffic are unaffected and no action is required.\n[2026-09-18 21:13:28 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-18 21:07:13 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-18 20:56:18 UTC] Vercel SRE (Investigating): We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available.\n[2026-09-18 20:32:37 UTC] Vercel SRE (Investigating): We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: The issue causing elevated errors triggering deployments has been resolved. \n\nExisting deployments and traffic are unaffected and no action is required. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are continuing to investigate an issue causing elevated errors triggering deployments. We'll provide additional updates as they become available. We are currently investi", "breaking_config_code": "# Incident architectural state during Elevated Errors Triggering Deployments\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6c79t86c2xrr", "metadata": {"raw_id": "bwkmw4hmrgmk", "status": "resolved", "resolved_at": "2026-09-18T21:22:27.000Z"}}
{"incident_id": "INC-2026-VERCEL-j6cdljvm", "company": "Vercel", "date": "2026-09-18", "title": "Elevated Vercel KMS and Connect Errors", "severity": "MEDIUM", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-18 15:14:45 UTC] Vercel SRE (Resolved): Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.", "breaking_config_code": "# Incident architectural state during Elevated Vercel KMS and Connect Errors\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/fzs89dpp3ghz", "metadata": {"raw_id": "j6cdljvmf2wf", "status": "resolved", "resolved_at": "2026-09-18T12:00:00.000Z"}}
{"incident_id": "INC-2026-VERCEL-ttqhd2v8", "company": "Vercel", "date": "2026-09-17", "title": "Failures delivering Logs to Drains", "severity": "MEDIUM", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-17 08:20:17 UTC] Vercel SRE (Resolved): Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries.\n\nAn update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries.\n\nAn update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.", "breaking_config_code": "# Incident architectural state during Failures delivering Logs to Drains\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/167k97c1j9d8", "metadata": {"raw_id": "ttqhd2v8dq3p", "status": "resolved", "resolved_at": "2026-09-17T07:11:00.000Z"}}
{"incident_id": "INC-2026-VERCEL-w1jqw8bw", "company": "Vercel", "date": "2026-09-16", "title": "Missing Web Analytics and Speed Insights data", "severity": "MEDIUM", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-16 16:58:36 UTC] Vercel SRE (Resolved): Between 14:00 UTC and 15:40 UTC, Web Analytics and Speed Insights were degraded, resulting in some missing data in the dashboard during the affected time period.\n\nWe identified the issue and landed a fix, and Web Analytics and Speed Insights have recovered. No additional actions are required.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Between 14:00 UTC and 15:40 UTC, Web Analytics and Speed Insights were degraded, resulting in some missing data in the dashboard during the affected time period.\n\nWe identified the issue and landed a fix, and Web Analytics and Speed Insights have recovered. No additional actions are required.", "breaking_config_code": "# Incident architectural state during Missing Web Analytics and Speed Insights data\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rm6qtt65w0x2", "metadata": {"raw_id": "w1jqw8bwk6xc", "status": "resolved", "resolved_at": "2026-09-16T14:00:00.000Z"}}
{"incident_id": "INC-2026-VERCEL-k6ykmr68", "company": "Vercel", "date": "2026-09-16", "title": "Invoice Generation Paused", "severity": "MEDIUM", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-16 23:15:40 UTC] Vercel SRE (Resolved): Invoice generation has been re-enabled.\n\n---\n\nWe've identified the issue and expect to resolve by end-of-day today. \n\n---\n\nWe've temporarily paused invoice generation. Invoices may arrive later than usual. Product availability and usage are unaffected, and no further action is required.\n\nWe're working on an update to re-enable invoice generation and we'll provide another update when invoicing resumes.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Invoice generation has been re-enabled.\n\n---\n\nWe've identified the issue and expect to resolve by end-of-day today. \n\n---\n\nWe've temporarily paused invoice generation. Invoices may arrive later than usual. Product availability and usage are unaffected, and no further action is required.\n\nWe're working on an update to re-enable invoice generation and we'll provide another update when invoicing resumes.", "breaking_config_code": "# Incident architectural state during Invoice Generation Paused\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rx2hvkmrstg7", "metadata": {"raw_id": "k6ykmr68s0b1", "status": "resolved", "resolved_at": "2026-09-16T03:21:00.000Z"}}
{"incident_id": "INC-2026-VERCEL-mf04gp4l", "company": "Vercel", "date": "2026-09-10", "title": "Elevated error rate on Connect and Passport", "severity": "HIGH", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-10 19:16:06 UTC] Vercel SRE (Resolved): Connect and Passport have fully recovered. This incident has been resolved.\n[2026-09-10 18:13:20 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-10 17:42:15 UTC] Vercel SRE (Investigating): We've identified an issue where some customers may experience increased errors from Connect and Passport. We are currently investigating this issue. We will provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Connect and Passport have fully recovered. This incident has been resolved. The issue has been identified and a fix is being implemented. We've identified an issue where some customers may experience increased errors from Connect and Passport. We are currently investigating this issue. We will provide additional updates as they become available.", "breaking_config_code": "# Incident architectural state during Elevated error rate on Connect and Passport\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/zbs4ktd26fb0", "metadata": {"raw_id": "mf04gp4lrfz0", "status": "resolved", "resolved_at": "2026-09-10T19:16:06.440Z"}}
{"incident_id": "INC-2026-VERCEL-b6s5qz7t", "company": "Vercel", "date": "2026-09-04", "title": "Elevated latency in VCR, Blob, and Sandbox API", "severity": "MEDIUM", "service_stack": ["Blob", "Sandbox", "Vercel Edge Network", "Serverless Functions"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-09-04 20:27:26 UTC] Vercel SRE (Resolved): Blob has fully recovered. This incident has been resolved.\n[2026-09-04 20:19:02 UTC] Vercel SRE (Monitoring): Elevated latency has recovered for VCR and Sandbox. We are continuing to investigate elevated latency affecting Blob and will provide another update shortly.\n[2026-09-04 20:05:43 UTC] Vercel SRE (Monitoring): The fix has been rolled out and we are seeing signs of recovery.\n[2026-09-04 19:55:37 UTC] Vercel SRE (Identified): The fix is currently being rolled out. We'll provide another update once the rollout is complete and we're beginning to see signs of recovery.\n[2026-09-04 19:33:18 UTC] Vercel SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-09-04 19:33:06 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-04 19:11:44 UTC] Vercel SRE (Investigating): We've identified an issue where some customers may experience increased latency for API requests to VCR, Blob, and Sandbox. We are currently investigating this issue. We will provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Blob has fully recovered. This incident has been resolved. Elevated latency has recovered for VCR and Sandbox. We are continuing to investigate elevated latency affecting Blob and will provide another update shortly. The fix has been rolled out and we are seeing signs of recovery. The fix is currently being rolled out. We'll provide another update once the rollout is complete and we're beginning to see signs of recovery. We are continuing to work", "breaking_config_code": "# Incident architectural state during Elevated latency in VCR, Blob, and Sandbox API\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Blob\", \"Sandbox\", \"Vercel Edge Network\", \"Serverless Functions\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Blob cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/qjy1j78m6ssc", "metadata": {"raw_id": "b6s5qz7tj35w", "status": "resolved", "resolved_at": "2026-09-04T20:27:26.000Z"}}
{"incident_id": "INC-2026-VERCEL-1z2qkcjg", "company": "Vercel", "date": "2026-09-01", "title": "Increased deployment failures", "severity": "HIGH", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-09-01 20:58:43 UTC] Vercel SRE (Resolved): This incident has been resolved. Builds have recovered.\n[2026-09-01 20:49:34 UTC] Vercel SRE (Monitoring): We are continuing to monitor for any further issues.\n[2026-09-01 20:45:56 UTC] Vercel SRE (Monitoring): We are seeing recovery in Builds and are continuing to monitor.\n[2026-09-01 20:37:48 UTC] Vercel SRE (Identified): We have identified the issue and are working on a fix. We are seeing recovery as the fix is deployed. We will provide additional updates as they become available.\n[2026-09-01 20:27:38 UTC] Vercel SRE (Investigating): We are actively working to fix an issue causing some deployments that use IAD1 Function regions or Routing Middleware to fail. We will provide additional updates as they become available.\n[2026-09-01 19:59:37 UTC] Vercel SRE (Investigating): We've identified an issue where some deployments that use IAD1 Function regions or Routing Middleware are failing. We are investigating and will provide more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. Builds have recovered. We are continuing to monitor for any further issues. We are seeing recovery in Builds and are continuing to monitor. We have identified the issue and are working on a fix. We are seeing recovery as the fix is deployed. We will provide additional updates as they become available. We are actively working to fix an issue causing some deployments that use IAD1 Function regions or Routing Middlew", "breaking_config_code": "# Incident architectural state during Increased deployment failures\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/01mntryqfgdj", "metadata": {"raw_id": "1z2qkcjgfx3y", "status": "resolved", "resolved_at": "2026-09-01T20:58:43.889Z"}}
{"incident_id": "INC-2026-VERCEL-75b4vyf7", "company": "Vercel", "date": "2026-08-26", "title": "Failures logging in with Vercel CLI", "severity": "HIGH", "service_stack": ["Dashboard", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-08-26 04:28:31 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-08-26 04:28:01 UTC] Vercel SRE (Identified): The team has identified the source of the issue and is testing a fix.\n[2026-08-26 03:15:37 UTC] Vercel SRE (Investigating): We are investigating errors logging in with Vercel CLI (vc login).\n[2026-08-26 03:06:11 UTC] Vercel SRE (Investigating): We are investigating errors logging in with Vercel CLI (vc login).", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. The team has identified the source of the issue and is testing a fix. We are investigating errors logging in with Vercel CLI (vc login). We are investigating errors logging in with Vercel CLI (vc login).", "breaking_config_code": "# Incident architectural state during Failures logging in with Vercel CLI\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/119clbk6991s", "metadata": {"raw_id": "75b4vyf7cm69", "status": "resolved", "resolved_at": "2026-08-26T04:28:31.132Z"}}
{"incident_id": "INC-2026-VERCEL-s6hljjh3", "company": "Vercel", "date": "2026-08-25", "title": "Elevated build initialization times", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-25 20:05:18 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-08-25 19:57:11 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-08-25 19:37:36 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-08-25 19:27:23 UTC] Vercel SRE (Investigating): We're investigating elevated initialization times for some builds. We will provide updates as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We're investigating elevated initialization times for some builds. We will provide updates as we learn more.", "breaking_config_code": "# Incident architectural state during Elevated build initialization times\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/xd3cnhctqkw3", "metadata": {"raw_id": "s6hljjh3n822", "status": "resolved", "resolved_at": "2026-08-25T20:05:18.309Z"}}
{"incident_id": "INC-2026-VERCEL-w8r0qkm9", "company": "Vercel", "date": "2026-08-20", "title": "New container functions are failing", "severity": "HIGH", "service_stack": ["Functions", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-20 18:34:00 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-08-20 18:23:05 UTC] Vercel SRE (Monitoring): We have deployed a fix. Newly deployed container functions are working as expected.\n[2026-08-20 17:46:33 UTC] Vercel SRE (Identified): We've identified an issue where newly deployed container functions may return 5XX errors.\n\nCustomers can use a previously working container function deployment as a temporary mitigation. We are working on a fix and will provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. We have deployed a fix. Newly deployed container functions are working as expected. We've identified an issue where newly deployed container functions may return 5XX errors.\n\nCustomers can use a previously working container function deployment as a temporary mitigation. We are working on a fix and will provide additional updates as they become available.", "breaking_config_code": "# Incident architectural state during New container functions are failing\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Functions\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Functions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/shj8f589lgh9", "metadata": {"raw_id": "w8r0qkm97p1c", "status": "resolved", "resolved_at": "2026-08-20T18:34:00.715Z"}}
{"incident_id": "INC-2026-VERCEL-g5svdyg4", "company": "Vercel", "date": "2026-08-20", "title": "Logs unavailable to query in Dashboard", "severity": "HIGH", "service_stack": ["Logs", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["DATABASE_DEGRADATION", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-20 11:25:37 UTC] Vercel SRE (Resolved): The system is operating normally and fully recovered.\n[2026-08-20 11:21:23 UTC] Vercel SRE (Monitoring): We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor.\n[2026-08-20 11:14:32 UTC] Vercel SRE (Investigating): We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: The system is operating normally and fully recovered. We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor. We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.", "breaking_config_code": "# Incident architectural state during Logs unavailable to query in Dashboard\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Logs\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Logs cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/fhw5075cj82r", "metadata": {"raw_id": "g5svdyg45c5b", "status": "resolved", "resolved_at": "2026-08-20T11:25:37.472Z"}}
{"incident_id": "INC-2026-VERCEL-ybx6km0j", "company": "Vercel", "date": "2026-08-18", "title": "Elevated errors for Workflow streams", "severity": "MEDIUM", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-19 00:28:30 UTC] Vercel SRE (Resolved): From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.", "breaking_config_code": "# Incident architectural state during Elevated errors for Workflow streams\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/2szns4x5lfs2", "metadata": {"raw_id": "ybx6km0j1gwk", "status": "resolved", "resolved_at": "2026-08-18T23:00:00.000Z"}}
{"incident_id": "INC-2026-VERCEL-nxvrk1jk", "company": "Vercel", "date": "2026-08-17", "title": "Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard", "severity": "MEDIUM", "service_stack": ["Dashboard", "Observability", "Speed Insights", "Web Analytics"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-08-17 21:25:26 UTC] Vercel SRE (Resolved): Services have recovered. We are still working to ingest missing observability data during this period.\n[2026-08-17 20:13:29 UTC] Vercel SRE (Monitoring): Services have recovered. We are still working to ingest missing observability data during this period.\n[2026-08-17 17:51:57 UTC] Vercel SRE (Monitoring): Login with TOTP has completely recovered. We are still working to ingest missing observability data during this period. We will share more information as it becomes available.\n[2026-08-17 16:46:03 UTC] Vercel SRE (Monitoring): We are continuing to monitor for any further issues.\n[2026-08-17 16:44:55 UTC] Vercel SRE (Monitoring): We have implemented a fix for the disruption, and services have started to recover. We will share more information as it becomes available.\n[2026-08-17 16:06:23 UTC] Vercel SRE (Investigating): We are also investigating an issue where some customers may be unable to sign in to Dashboard with time-based one-time passwords (TOTP). We will share updates as they become available.\n[2026-08-17 15:09:49 UTC] Vercel SRE (Investigating): We are continuing to investigate this issue. We will share updates as they become available.\n[2026-08-17 14:30:28 UTC] Vercel SRE (Investigating): We are investigating a partial disruption to Observability, Web Analytics, Speed Insights, Firewall, and Usage in Dashboard. We will share updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Services have recovered. We are still working to ingest missing observability data during this period. Services have recovered. We are still working to ingest missing observability data during this period. Login with TOTP has completely recovered. We are still working to ingest missing observability data during this period. We will share more information as it becomes available. We are continuing to monitor for any further issues. We have impleme", "breaking_config_code": "# Incident architectural state during Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"Observability\", \"Speed Insights\", \"Web Analytics\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/sqztsdm8bq4d", "metadata": {"raw_id": "nxvrk1jk0zyb", "status": "resolved", "resolved_at": "2026-08-17T21:25:26.163Z"}}
{"incident_id": "INC-2026-VERCEL-ysczd6rx", "company": "Vercel", "date": "2026-08-14", "title": "Dynamic API routes returned 404 errors for some deployments", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-14 13:08:12 UTC] Vercel SRE (Resolved): This incident has been resolved. Between August 12, 17:12 UTC and August 13, 20:33 UTC, some Vercel deployments could return 404 errors from dynamic API routes.\n\nDeployments built on Vercel during this period were affected only if they met all three conditions: used Next.js 16.2 or earlier, used the Pages Router with internationalization (i18n configured in next.config.js), and used dynamic API routes, such as pages/api/[slug].ts or pages/api/[...path].ts.\n\nDeployments built outside Vercel (with vercel deploy --prebuilt) were not affected, and existing deployments not rebuilt during this period were not affected.\n\nIf your project matches the conditions above and you deployed during the impact window, redeploy your project. Affected deployments are not fixed automatically; a new deployment is required to restore the affected routes.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. Between August 12, 17:12 UTC and August 13, 20:33 UTC, some Vercel deployments could return 404 errors from dynamic API routes.\n\nDeployments built on Vercel during this period were affected only if they met all three conditions: used Next.js 16.2 or earlier, used the Pages Router with internationalization (i18n configured in next.config.js), and used dynamic API routes, such as pages/api/[slug].ts or pages/api/[..", "breaking_config_code": "# Incident architectural state during Dynamic API routes returned 404 errors for some deployments\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/s34qc7lrx9db", "metadata": {"raw_id": "ysczd6rxyl7z", "status": "resolved", "resolved_at": "2026-08-14T13:08:12.887Z"}}
{"incident_id": "INC-2026-VERCEL-vbxl834x", "company": "Vercel", "date": "2026-08-06", "title": "Delays delivering log drains", "severity": "MEDIUM", "service_stack": ["Drains", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-06 18:29:45 UTC] Vercel SRE (Resolved): This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.\n[2026-08-06 18:19:33 UTC] Vercel SRE (Monitoring): Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed.\n[2026-08-06 17:48:17 UTC] Vercel SRE (Identified): We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available.\n[2026-08-06 17:06:01 UTC] Vercel SRE (Identified): We've identified the issue and are working on a fix. We will provide updates as they become available.\n[2026-08-06 16:58:35 UTC] Vercel SRE (Investigating): We continue to investigate this issue and will provide updates as they become available.\n[2026-08-06 16:37:10 UTC] Vercel SRE (Investigating): We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed. Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed. We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available. We've identified the issue and are working on a fix. We will provide updates as they become available. We cont", "breaking_config_code": "# Incident architectural state during Delays delivering log drains\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Drains\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Drains cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/jygyd62lmmdx", "metadata": {"raw_id": "vbxl834x9l7q", "status": "resolved", "resolved_at": "2026-08-06T18:29:45.219Z"}}
{"incident_id": "INC-2026-VERCEL-yh45fsy7", "company": "Vercel", "date": "2026-07-25", "title": "Vercel Community temporarily unavailable", "severity": "MEDIUM", "service_stack": ["Community", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-26 17:46:26 UTC] Vercel SRE (Resolved): Maintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience.\n[2026-07-25 18:57:40 UTC] Vercel SRE (Investigating): The Vercel Community forums are currently undergoing maintenance. We are working to restore access as soon as possible.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Maintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience. The Vercel Community forums are currently undergoing maintenance. We are working to restore access as soon as possible.", "breaking_config_code": "# Incident architectural state during Vercel Community temporarily unavailable\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Community\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Community cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/nc6n7dnn8nz7", "metadata": {"raw_id": "yh45fsy7h0l8", "status": "resolved", "resolved_at": "2026-07-26T17:46:26.147Z"}}
{"incident_id": "INC-2026-VERCEL-1s8rqbsw", "company": "Vercel", "date": "2026-07-23", "title": "Telemetry data loss for Drains", "severity": "HIGH", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-24 17:26:56 UTC] Vercel SRE (Resolved): Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported.\n\nWe have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from happening in the future.\n\nWe know how much you rely on this data, and we sincerely apologize for the disruption.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported.\n\nWe have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from", "breaking_config_code": "# Incident architectural state during Telemetry data loss for Drains\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/b2wb9x4qkqwq", "metadata": {"raw_id": "1s8rqbswvwqc", "status": "resolved", "resolved_at": "2026-07-23T19:00:00.000Z"}}
{"incident_id": "INC-2026-VERCEL-bwyq88fx", "company": "Vercel", "date": "2026-07-23", "title": "Timeouts loading charts and observability data in Dashboard", "severity": "HIGH", "service_stack": ["Observability", "Speed Insights", "Web Analytics", "Firewall"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-23 08:18:49 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-07-23 07:55:33 UTC] Vercel SRE (Monitoring): The team identified the source of the issue and a fix has been implemented. We are starting to see recovery. Charts and observability data should be loading again for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. We continue to monitor.\n[2026-07-23 07:33:48 UTC] Vercel SRE (Investigating): We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. This impacts charts in the Dashboard.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. The team identified the source of the issue and a fix has been implemented. We are starting to see recovery. Charts and observability data should be loading again for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Workflows. We continue to monitor. We are currently investigating timeouts loading observability data for Firewall, Observability, Sandboxes, Speed Insights, Web Analytics, and Wo", "breaking_config_code": "# Incident architectural state during Timeouts loading charts and observability data in Dashboard\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Observability\", \"Speed Insights\", \"Web Analytics\", \"Firewall\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Observability cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/pcy9pldzdfqw", "metadata": {"raw_id": "bwyq88fxt57g", "status": "resolved", "resolved_at": "2026-07-23T08:18:49.984Z"}}
{"incident_id": "INC-2026-VERCEL-zxb1gkbx", "company": "Vercel", "date": "2026-07-23", "title": "Dashboard authentication errors", "severity": "CRITICAL", "service_stack": ["Dashboard", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-07-23 07:41:57 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-07-23 07:08:53 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-23 06:47:01 UTC] Vercel SRE (Investigating): We are investigating an issue causing the dashboard to be inaccessible for some users.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are investigating an issue causing the dashboard to be inaccessible for some users.", "breaking_config_code": "# Incident architectural state during Dashboard authentication errors\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/k5mrp1pc2l00", "metadata": {"raw_id": "zxb1gkbxnktp", "status": "resolved", "resolved_at": "2026-07-23T07:41:57.950Z"}}
{"incident_id": "INC-2026-VERCEL-mskkl0ry", "company": "Vercel", "date": "2026-07-17", "title": "Increased invocation failures for Hobby Team functions", "severity": "MEDIUM", "service_stack": ["Functions", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-17 15:19:53 UTC] Vercel SRE (Resolved): This incident has been resolved.\n\nA subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected.\n[2026-07-17 14:27:39 UTC] Vercel SRE (Monitoring): We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment.\n[2026-07-17 14:19:52 UTC] Vercel SRE (Identified): We have identified the source of errors and are implementing a fix.\n[2026-07-17 14:12:58 UTC] Vercel SRE (Investigating): There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved.\n\nA subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected. We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous de", "breaking_config_code": "# Incident architectural state during Increased invocation failures for Hobby Team functions\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Functions\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Functions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/qcpsy7kj6dlc", "metadata": {"raw_id": "mskkl0ryk3zn", "status": "resolved", "resolved_at": "2026-07-17T15:19:53.000Z"}}
{"incident_id": "INC-2026-VERCEL-vqndbxzg", "company": "Vercel", "date": "2026-07-16", "title": "GitHub-linked deployments and authentication affected", "severity": "MEDIUM", "service_stack": ["Dashboard", "Builds", "Git Integrations", "Vercel Edge Network"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-07-17 00:42:10 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-07-17 00:07:15 UTC] Vercel SRE (Monitoring): Deployments for projects linked to GitHub repositories are recovering. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. GitHub login, signup, and account connections are recovered.\n[2026-07-16 23:39:29 UTC] Vercel SRE (Identified): We've identified an issue affecting deployments for projects linked to GitHub repositories, as well as GitHub login, signup, and account connections. CLI deployments and other sign-in methods are unaffected. We will share updates as they become available.\n[2026-07-16 23:09:29 UTC] Vercel SRE (Investigating): We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. Deployments for projects linked to GitHub repositories are recovering. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available. GitHub login, signup, and account connections are recovered. We've identified an issue affecting deployments for projects linked to GitHub repositories, as", "breaking_config_code": "# Incident architectural state during GitHub-linked deployments and authentication affected\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"Builds\", \"Git Integrations\", \"Vercel Edge Network\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/yht3lc3nr2g8", "metadata": {"raw_id": "vqndbxzgzhx9", "status": "resolved", "resolved_at": "2026-07-17T00:42:10.596Z"}}
{"incident_id": "INC-2026-VERCEL-nw8xv7yp", "company": "Vercel", "date": "2026-07-16", "title": "SAML Single Sign-On (SSO) errors", "severity": "HIGH", "service_stack": ["SAML Single Sign-On", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-07-16 10:45:23 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-07-16 10:23:48 UTC] Vercel SRE (Monitoring): The root cause of the SAML Single Sign-On (SSO) errors has been identified and a fix has been implemented. We are seeing error rates decrease. Users should be able to login with SAML/SSO or access their SSO-protected teams through the Vercel dashboard and CLI again. We are continuing to monitor.\n[2026-07-16 08:39:35 UTC] Vercel SRE (Investigating): We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protected teams through the Vercel dashboard and CLI.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. The root cause of the SAML Single Sign-On (SSO) errors has been identified and a fix has been implemented. We are seeing error rates decrease. Users should be able to login with SAML/SSO or access their SSO-protected teams through the Vercel dashboard and CLI again. We are continuing to monitor. We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protec", "breaking_config_code": "# Incident architectural state during SAML Single Sign-On (SSO) errors\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"SAML Single Sign-On\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on SAML Single Sign-On cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/yzqkkrl8lw0m", "metadata": {"raw_id": "nw8xv7ypn7y0", "status": "resolved", "resolved_at": "2026-07-16T10:45:23.782Z"}}
{"incident_id": "INC-2026-VERCEL-xfkn71bb", "company": "Vercel", "date": "2026-07-16", "title": "Missing Build CPU Minutes Usage Data", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-16 09:27:19 UTC] Vercel SRE (Resolved): The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard.\n[2026-07-16 06:07:15 UTC] Vercel SRE (Monitoring): We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: The missing Build CPU Minutes data has been backfilled. Users with missing Build CPU Minutes data will be able to see it on Usage pages in the Vercel Dashboard. We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.", "breaking_config_code": "# Incident architectural state during Missing Build CPU Minutes Usage Data\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/v9m67w60bdjk", "metadata": {"raw_id": "xfkn71bbvc99", "status": "resolved", "resolved_at": "2026-07-16T09:27:19.495Z"}}
{"incident_id": "INC-2026-VERCEL-ydqg5447", "company": "Vercel", "date": "2026-07-15", "title": "Errors accessing teams that require 2FA", "severity": "MEDIUM", "service_stack": ["Dashboard", "AI Gateway", "API", "Vercel Edge Network"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-07-15 23:34:54 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-07-15 23:16:23 UTC] Vercel SRE (Monitoring): A fix has been implemented and services have recovered. We are continuing to monitor to ensure that the services remain stable. We will provide additional updates as they become available.\n[2026-07-15 23:04:43 UTC] Vercel SRE (Identified): We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we have it.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and services have recovered. We are continuing to monitor to ensure that the services remain stable. We will provide additional updates as they become available. We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we h", "breaking_config_code": "# Incident architectural state during Errors accessing teams that require 2FA\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"AI Gateway\", \"API\", \"Vercel Edge Network\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/dz3d8c79b47j", "metadata": {"raw_id": "ydqg5447j7j0", "status": "resolved", "resolved_at": "2026-07-15T23:34:54.097Z"}}
{"incident_id": "INC-2026-VERCEL-j0ll7yc1", "company": "Vercel", "date": "2026-07-10", "title": "Increased Build failure rates", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-10 23:28:43 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-07-10 21:25:09 UTC] Vercel SRE (Monitoring): We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC.\n\nA rollback is in progress to mitigate this issue. We will provide additional updates as they become available.\n\nFailed deployments can be retried and should succeed.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. We've identified an issue where some customers may experience failed Builds beginning at 21:05 UTC.\n\nA rollback is in progress to mitigate this issue. We will provide additional updates as they become available.\n\nFailed deployments can be retried and should succeed.", "breaking_config_code": "# Incident architectural state during Increased Build failure rates\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/7r7v7fr4bhbp", "metadata": {"raw_id": "j0ll7yc1jscj", "status": "resolved", "resolved_at": "2026-07-10T23:28:43.839Z"}}
{"incident_id": "INC-2026-VERCEL-458cy54l", "company": "Vercel", "date": "2026-07-10", "title": "Erroneous budget notifications", "severity": "MEDIUM", "service_stack": ["Dashboard", "Builds", "Vercel Edge Network", "Serverless Functions"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-10 22:36:10 UTC] Vercel SRE (Resolved): We have unpaused all impacted deployments. We will continue to monitor the situation.\n[2026-07-10 21:32:58 UTC] Vercel SRE (Identified): We are still working to unpause affected teams that were erroneously paused due to the spend management budget miscalculation.\n\nWe will provide additional updates as they become available.\n[2026-07-10 20:50:35 UTC] Vercel SRE (Identified): We've compiled a list of deployments that were paused due to this incident and are now unpausing them in batches. If your deployment was paused, you can also navigate to the Vercel dashboard and click the unpause button in the banner.\n[2026-07-10 19:53:44 UTC] Vercel SRE (Identified): We've identified and fixed the underlying issue. Our team is now unpausing deployments that were inadvertently paused as a result.\n[2026-07-10 19:15:53 UTC] Vercel SRE (Investigating): We've identified an issue where some customers may receive erroneous spend management budget notifications due to a spend management budget miscalculation. Affected teams with spend management budgets configured to pause projects may also experience paused deployments. We are currently investigating this issue. We will provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: We have unpaused all impacted deployments. We will continue to monitor the situation. We are still working to unpause affected teams that were erroneously paused due to the spend management budget miscalculation.\n\nWe will provide additional updates as they become available. We've compiled a list of deployments that were paused due to this incident and are now unpausing them in batches. If your deployment was paused, you can also navigate to the V", "breaking_config_code": "# Incident architectural state during Erroneous budget notifications\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"Builds\", \"Vercel Edge Network\", \"Serverless Functions\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/274dc78rzc6q", "metadata": {"raw_id": "458cy54l4d6d", "status": "resolved", "resolved_at": "2026-07-10T22:36:10.373Z"}}
{"incident_id": "INC-2026-VERCEL-gk45lsnm", "company": "Vercel", "date": "2026-07-09", "title": "Delays loading Build Logs", "severity": "MEDIUM", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-10 17:44:16 UTC] Vercel SRE (Resolved): The issue affecting Build Logs has been resolved. Between Jul 8 19:05 UTC and Jul 9 13:16 UTC, some Pro customers using standard machine types may have experienced missing Build Logs.\n\nNew builds after the impact period are unaffected.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: The issue affecting Build Logs has been resolved. Between Jul 8 19:05 UTC and Jul 9 13:16 UTC, some Pro customers using standard machine types may have experienced missing Build Logs.\n\nNew builds after the impact period are unaffected.", "breaking_config_code": "# Incident architectural state during Delays loading Build Logs\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/lwv762xftprn", "metadata": {"raw_id": "gk45lsnmx35m", "status": "resolved", "resolved_at": "2026-07-09T13:16:00.000Z"}}
{"incident_id": "INC-2026-VERCEL-lf0pm7sc", "company": "Vercel", "date": "2026-07-08", "title": "Delays Processing Builds", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-08 22:23:52 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-07-08 21:35:42 UTC] Vercel SRE (Monitoring): The issue affecting build queue processing has been resolved, and build queues have returned to normal. Builds are now processing as expected.\n\nWe are continuing our internal root cause analysis.\n[2026-07-08 19:13:18 UTC] Vercel SRE (Monitoring): Build queues have returned to normal levels, and build processing should be restored.\n\nWe are monitoring to ensure the service remains stable. We will provide additional updates as they become available.\n[2026-07-08 18:40:41 UTC] Vercel SRE (Investigating): We are seeing signs of recovery and the affected build queue has started to drain.\n\nSome customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available.\n[2026-07-08 18:05:09 UTC] Vercel SRE (Investigating): We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are currently investigating this issue and will provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. The issue affecting build queue processing has been resolved, and build queues have returned to normal. Builds are now processing as expected.\n\nWe are continuing our internal root cause analysis. Build queues have returned to normal levels, and build processing should be restored.\n\nWe are monitoring to ensure the service remains stable. We will provide additional updates as they become available. We are seeing sig", "breaking_config_code": "# Incident architectural state during Delays Processing Builds\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6p93bsts8r9y", "metadata": {"raw_id": "lf0pm7scd74x", "status": "resolved", "resolved_at": "2026-07-08T19:13:52.000Z"}}
{"incident_id": "INC-2026-VERCEL-bgmdgj7m", "company": "Vercel", "date": "2026-07-02", "title": "Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)", "severity": "MEDIUM", "service_stack": ["Dashboard", "CLE1 - Cleveland, East US", "IAD1 - Washington DC, USA", "Functions"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-02 16:46:33 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-07-02 16:39:55 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor.\n[2026-07-02 16:33:07 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-07-02 16:31:55 UTC] Vercel SRE (Investigating): We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are observing recovery across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We are continuing to monitor. The issue has been identified and a fix is being implemented. We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.", "breaking_config_code": "# Incident architectural state during Degraded performance on CDN, Dashboard, Functions in Washington, Cleveland (iad1, cle1)\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"CLE1 - Cleveland, East US\", \"IAD1 - Washington DC, USA\", \"Functions\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/k50rhwbpqxwq", "metadata": {"raw_id": "bgmdgj7m7bgm", "status": "resolved", "resolved_at": "2026-07-02T16:46:33.807Z"}}
{"incident_id": "INC-2026-VERCEL-kndhly1h", "company": "Vercel", "date": "2026-07-01", "title": "Increase in Workflow runs stuck in pending, failed", "severity": "MEDIUM", "service_stack": ["Workflow", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-01 18:30:29 UTC] Vercel SRE (Resolved): The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected.\n\nAffected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state.\n[2026-07-01 17:49:13 UTC] Vercel SRE (Identified): We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have reached a failed state. \n\nNew workflow runs are not impacted.\n[2026-07-01 16:57:03 UTC] Vercel SRE (Identified): We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. \n\nNew workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: The issue affecting workflow runs getting stuck in a pending or failed state has been resolved. New workflow runs after the impact period are unaffected.\n\nAffected workflow runs have been recovered where possible. Runs that could be resumed safely were resumed and runs that could not be resumed safely were transitioned to a cancelled state. We are continuing to work on recovering affected workflow runs that may be stuck in a pending state or have", "breaking_config_code": "# Incident architectural state during Increase in Workflow runs stuck in pending, failed\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Workflow\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Workflow cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/q6nb60k20jgd", "metadata": {"raw_id": "kndhly1hl696", "status": "resolved", "resolved_at": "2026-07-01T18:30:29.000Z"}}
{"incident_id": "INC-2026-VERCEL-9mwnzxkn", "company": "Vercel", "date": "2026-06-26", "title": "Intermittent Login Failures on Vercel Dashboard", "severity": "HIGH", "service_stack": ["Dashboard", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-06-26 15:14:03 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-06-26 15:03:01 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-26 14:29:14 UTC] Vercel SRE (Identified): Login is recovering for most users. We're monitoring to ensure stability.\n[2026-06-26 14:11:59 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-06-26 14:08:10 UTC] Vercel SRE (Investigating): We are continuing to investigate this issue and will provide an update as soon as we have more information.\n[2026-06-26 13:23:02 UTC] Vercel SRE (Investigating): We are continuing to investigate this issue.\n[2026-06-26 13:08:09 UTC] Vercel SRE (Investigating): We are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. Login is recovering for most users. We're monitoring to ensure stability. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue and will provide an update as soon as we have more information. We are continuing to investigate this issue. We are currently investigating the issue. Some users are experienc", "breaking_config_code": "# Incident architectural state during Intermittent Login Failures on Vercel Dashboard\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/mv7d6s5y2w5q", "metadata": {"raw_id": "9mwnzxknwysy", "status": "resolved", "resolved_at": "2026-06-26T15:14:03.417Z"}}
{"incident_id": "INC-2026-VERCEL-x4ngbgzy", "company": "Vercel", "date": "2026-06-25", "title": "Increase in Workflow runs stuck as pending", "severity": "HIGH", "service_stack": ["Workflow", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-25 13:43:22 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-06-25 13:30:43 UTC] Vercel SRE (Monitoring): The fix has been fully rolled out and we are monitoring the results.\n[2026-06-25 12:15:05 UTC] Vercel SRE (Identified): We are currently rolling a fix for the issue. We are monitoring the results.\n[2026-06-25 10:42:09 UTC] Vercel SRE (Identified): We are still working on a fix for this issue. While we fix the issue, users experiencing pending Workflow runs can trigger an instant rollback to a working deployment created before Jun 24 21:00 UTC to resume operation on new runs.\n[2026-06-25 09:25:34 UTC] Vercel SRE (Identified): The issue has been identified. We are continuing to work on a fix for this issue.\n[2026-06-25 08:27:40 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-06-25 07:45:00 UTC] Vercel SRE (Investigating): We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. The fix has been fully rolled out and we are monitoring the results. We are currently rolling a fix for the issue. We are monitoring the results. We are still working on a fix for this issue. While we fix the issue, users experiencing pending Workflow runs can trigger an instant rollback to a working deployment created before Jun 24 21:00 UTC to resume operation on new runs. The issue has been identified. We are c", "breaking_config_code": "# Incident architectural state during Increase in Workflow runs stuck as pending\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Workflow\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Workflow cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6rjcs694wc3s", "metadata": {"raw_id": "x4ngbgzymq4h", "status": "resolved", "resolved_at": "2026-06-25T13:43:22.720Z"}}
{"incident_id": "INC-2026-VERCEL-bc8kw6cj", "company": "Vercel", "date": "2026-06-23", "title": "Degraded Domain Search in Vercel Dashboard", "severity": "MEDIUM", "service_stack": ["Domain Registration", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-23 23:34:35 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-06-23 23:28:31 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-23 23:26:31 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-06-23 23:24:24 UTC] Vercel SRE (Investigating): We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.", "breaking_config_code": "# Incident architectural state during Degraded Domain Search in Vercel Dashboard\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Domain Registration\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Domain Registration cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4wq1dnwtkzfg", "metadata": {"raw_id": "bc8kw6cjklny", "status": "resolved", "resolved_at": "2026-06-23T23:34:35.849Z"}}
{"incident_id": "INC-2026-VERCEL-3h7jsmmr", "company": "Vercel", "date": "2026-06-19", "title": "Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions", "severity": "MEDIUM", "service_stack": ["Functions", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-19 17:54:16 UTC] Vercel SRE (Resolved): Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE.\n\nAs part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989\n\nWe have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE.\n\nAs part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989\n\nWe have resol", "breaking_config_code": "# Incident architectural state during Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Functions\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Functions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/clqq0f551l8m", "metadata": {"raw_id": "3h7jsmmrljwt", "status": "resolved", "resolved_at": "2026-06-19T17:54:16.000Z"}}
{"incident_id": "INC-2026-VERCEL-fyjmwj5q", "company": "Vercel", "date": "2026-06-16", "title": "Partial disruption of Observability, Analytics, Firewall, and Usage in dashboard", "severity": "MEDIUM", "service_stack": ["Dashboard", "Observability", "Speed Insights", "Web Analytics"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-16 15:39:55 UTC] Vercel SRE (Resolved): The incident has been resolved.\n[2026-06-16 15:26:26 UTC] Vercel SRE (Monitoring): The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor.\n[2026-06-16 15:16:05 UTC] Vercel SRE (Identified): The team has identified the source of the issue and is preparing a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard.\n[2026-06-16 14:45:23 UTC] Vercel SRE (Investigating): We are continuing to investigate partial disruption to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are also investigating delayed usage alerts.\n[2026-06-16 13:39:02 UTC] Vercel SRE (Investigating): We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: The incident has been resolved. The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor. The team has identified the source of the issue and is preparing a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to investigate partia", "breaking_config_code": "# Incident architectural state during Partial disruption of Observability, Analytics, Firewall, and Usage in dashboard\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"Observability\", \"Speed Insights\", \"Web Analytics\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/00m5l68d3w2m", "metadata": {"raw_id": "fyjmwj5qy4vz", "status": "resolved", "resolved_at": "2026-06-16T15:39:55.447Z"}}
{"incident_id": "INC-2026-VERCEL-2f4kf430", "company": "Vercel", "date": "2026-06-14", "title": "Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)", "severity": "HIGH", "service_stack": ["FRA1 - Frankfurt, Germany, Europe", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-06-15 01:24:24 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-06-15 00:25:30 UTC] Vercel SRE (Monitoring): All traffic has been restored to the FRA1 Vercel Region.\n[2026-06-14 23:15:26 UTC] Vercel SRE (Identified): The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.\n[2026-06-14 21:26:03 UTC] Vercel SRE (Identified): The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.\n[2026-06-14 21:07:51 UTC] Vercel SRE (Identified): We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.\n[2026-06-14 21:03:53 UTC] Vercel SRE (Investigating): We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. All traffic has been restored to the FRA1 Vercel Region. The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished. The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently re-routing traffic from the FR", "breaking_config_code": "# Incident architectural state during Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"FRA1 - Frankfurt, Germany, Europe\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on FRA1 - Frankfurt, Germany, Europe cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/v33c687sl3l8", "metadata": {"raw_id": "2f4kf430rmlz", "status": "resolved", "resolved_at": "2026-06-15T01:24:24.954Z"}}
{"incident_id": "INC-2026-VERCEL-l7m81jfv", "company": "Vercel", "date": "2026-06-09", "title": "Elevated Build Errors for Secure Compute/Static IPs Projects", "severity": "HIGH", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-09 14:46:02 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-06-09 14:39:11 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-09 14:33:30 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-06-09 14:09:36 UTC] Vercel SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Elevated Build Errors for Secure Compute/Static IPs Projects\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/w4mmm60615kp", "metadata": {"raw_id": "l7m81jfvmv0v", "status": "resolved", "resolved_at": "2026-06-09T14:46:02.014Z"}}
{"incident_id": "INC-2026-VERCEL-yzhdk6nh", "company": "Vercel", "date": "2026-06-08", "title": "Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region", "severity": "MEDIUM", "service_stack": ["Functions", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-08 20:00:11 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-06-08 19:36:44 UTC] Vercel SRE (Monitoring): We are continuing to monitor for any further issues.\n[2026-06-08 19:36:38 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-08 19:04:25 UTC] Vercel SRE (Identified): We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region.\n\nIf your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue.\n[2026-06-08 18:57:47 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n\nA small number of requests may have seen elevated error rates in function invocations during this period.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. We are continuing to monitor for any further issues. A fix has been implemented and we are monitoring the results. We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region.\n\nIf your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue. The ", "breaking_config_code": "# Incident architectural state during Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Functions\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Functions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/y4pp4nyhm4g6", "metadata": {"raw_id": "yzhdk6nhy1kx", "status": "resolved", "resolved_at": "2026-06-08T20:00:11.807Z"}}
{"incident_id": "INC-2026-VERCEL-s3625k1f", "company": "Vercel", "date": "2026-06-01", "title": "Elevated Errors Creating New Deployments", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-01 20:02:11 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-06-01 19:55:06 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-01 19:50:07 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-06-01 19:21:13 UTC] Vercel SRE (Investigating): We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.", "breaking_config_code": "# Incident architectural state during Elevated Errors Creating New Deployments\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/1bk3tqkfm0xj", "metadata": {"raw_id": "s3625k1ftc1b", "status": "resolved", "resolved_at": "2026-06-01T20:02:11.550Z"}}
{"incident_id": "INC-2026-VERCEL-yqvf53mh", "company": "Vercel", "date": "2026-05-28", "title": "Elevated Function Invocation Errors in Stockholm region (ARN1)", "severity": "MEDIUM", "service_stack": ["Functions", "Routing Middleware", "Vercel Edge Network", "Serverless Functions"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-05-28 16:59:49 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-05-28 16:37:04 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-05-28 16:18:09 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-05-28 16:00:14 UTC] Vercel SRE (Investigating): We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Elevated Function Invocation Errors in Stockholm region (ARN1)\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Functions\", \"Routing Middleware\", \"Vercel Edge Network\", \"Serverless Functions\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Functions cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/bmzvr8067f2s", "metadata": {"raw_id": "yqvf53mhyb78", "status": "resolved", "resolved_at": "2026-05-28T16:59:49.272Z"}}
{"incident_id": "INC-2026-VERCEL-rqs9fn6t", "company": "Vercel", "date": "2026-05-27", "title": "Elevated Errors on Vercel Dashboard (Project Overview Page)", "severity": "MEDIUM", "service_stack": ["Dashboard", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-05-27 05:02:13 UTC] Vercel SRE (Resolved): This incident has been resolved.\n\nWe've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC.\n[2026-05-27 04:50:59 UTC] Vercel SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved.\n\nWe've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Elevated Errors on Vercel Dashboard (Project Overview Page)\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Dashboard\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8w25lg7k4qdw", "metadata": {"raw_id": "rqs9fn6trp82", "status": "resolved", "resolved_at": "2026-05-27T05:02:13.000Z"}}
{"incident_id": "INC-2026-VERCEL-xxfj4qsz", "company": "Vercel", "date": "2026-05-25", "title": "Delays Loading Runtime Logs", "severity": "MEDIUM", "service_stack": ["Logs", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-05-25 16:22:39 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-05-25 16:05:38 UTC] Vercel SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-05-25 15:25:10 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-05-25 14:58:41 UTC] Vercel SRE (Investigating): We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.", "breaking_config_code": "# Incident architectural state during Delays Loading Runtime Logs\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Logs\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Logs cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/gp73wd5plwt9", "metadata": {"raw_id": "xxfj4qsz4qk6", "status": "resolved", "resolved_at": "2026-05-25T16:22:39.461Z"}}
{"incident_id": "INC-2026-VERCEL-jmrsg4wc", "company": "Vercel", "date": "2026-05-23", "title": "Elevated Build Failures (GitHub connected projects)", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-05-23 18:44:30 UTC] Vercel SRE (Resolved): This incident has been resolved.\n\nPlease refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt\n[2026-05-23 18:21:29 UTC] Vercel SRE (Monitoring): GitHub has implemented a fix, and we are monitoring the results.\n[2026-05-23 15:46:55 UTC] Vercel SRE (Identified): We have identified the issue and are working closely with GitHub to resolve it.\n[2026-05-23 14:30:01 UTC] Vercel SRE (Investigating): We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates as the situation develops.\n[2026-05-23 12:15:39 UTC] Vercel SRE (Investigating): We are continuing to investigate this issue.\n[2026-05-23 11:09:23 UTC] Vercel SRE (Investigating): We've been observing increased failures of git operations with GitHub since around 06:00 UTC. Some deployments triggered by GitHub commits might have seen git-related errors in failed build logs.\n\nCLI deployments are unaffected at this time.\n[2026-05-23 10:43:45 UTC] Vercel SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved.\n\nPlease refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt GitHub has implemented a fix, and we are monitoring the results. We have identified the issue and are working closely with GitHub to resolve it. We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. ", "breaking_config_code": "# Incident architectural state during Elevated Build Failures (GitHub connected projects)\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/gck741vpfk2k", "metadata": {"raw_id": "jmrsg4wcbtnn", "status": "resolved", "resolved_at": "2026-05-23T18:44:30.000Z"}}
{"incident_id": "INC-2026-VERCEL-mq7wpz9m", "company": "Vercel", "date": "2026-05-22", "title": "Build Failures for Some Next.js Deployments", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-05-22 17:11:29 UTC] Vercel SRE (Resolved): Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.", "breaking_config_code": "# Incident architectural state during Build Failures for Some Next.js Deployments\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9gpm992vwn60", "metadata": {"raw_id": "mq7wpz9mf8yl", "status": "resolved", "resolved_at": "2026-05-22T17:11:29.466Z"}}
{"incident_id": "INC-2026-VERCEL-4pv662qv", "company": "Vercel", "date": "2026-05-21", "title": "Elevated Build Errors", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-05-21 21:31:15 UTC] Vercel SRE (Resolved): This incident has been resolved.\n[2026-05-21 21:20:56 UTC] Vercel SRE (Monitoring): The mitigation was successfully rolled out, and builds are stable.\n[2026-05-21 19:55:08 UTC] Vercel SRE (Identified): The root cause has been identified and we are rolling out a mitigation.\n[2026-05-21 15:01:57 UTC] Vercel SRE (Identified): We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved. The mitigation was successfully rolled out, and builds are stable. The root cause has been identified and we are rolling out a mitigation. We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.", "breaking_config_code": "# Incident architectural state during Elevated Build Errors\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9xd8yb4qzw4p", "metadata": {"raw_id": "4pv662qvyqhv", "status": "resolved", "resolved_at": "2026-05-21T21:31:15.064Z"}}
{"incident_id": "INC-2026-VERCEL-0qjk7n73", "company": "Vercel", "date": "2026-05-20", "title": "Missing Build CPU Minutes Usage Data", "severity": "MEDIUM", "service_stack": ["Builds", "Vercel Edge Network", "Serverless Functions", "Build Pipeline"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-05-21 06:08:03 UTC] Vercel SRE (Resolved): This incident has been resolved.\n\nUsage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up as we backfill the data for the affected window.\n[2026-05-20 20:07:17 UTC] Vercel SRE (Monitoring): We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved.\n\nUsage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up as we backfill the data for the affected window. We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usag", "breaking_config_code": "# Incident architectural state during Missing Build CPU Minutes Usage Data\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Builds\", \"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Builds cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/xt6sl3hp53c5", "metadata": {"raw_id": "0qjk7n7347h8", "status": "resolved", "resolved_at": "2026-05-21T06:08:03.000Z"}}
{"incident_id": "INC-2026-VERCEL-0pl74z9t", "company": "Vercel", "date": "2026-05-18", "title": "Increased Function Invocation Errors - ERR_MODULE_NOT_FOUND", "severity": "MEDIUM", "service_stack": ["Vercel Edge Network", "Serverless Functions", "Build Pipeline", "AWS Lambda"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-05-18 23:52:05 UTC] Vercel SRE (Resolved): This incident has been resolved.\n\nSome deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments created outside of this window are unaffected.\n\nThe fix is being rolled out to existing deployments retrospectively and is expected to finish in the next few hours.\n[2026-05-18 22:19:32 UTC] Vercel SRE (Monitoring): We are continuing to monitor for any further issues.\n[2026-05-18 22:16:40 UTC] Vercel SRE (Monitoring): A fix is rolled out for the function invocation errors affecting React Router 7 deployments. To recover, redeploy your application or use Instant Rollback to a previous deployment from the dashboard. We're continuing to monitor.\n[2026-05-18 22:11:52 UTC] Vercel SRE (Identified): We're continuing to work on rolling out a fix. In the mean time, customers may use Instant Rollback to a previous deployment version as an immediate workaround in order to recover.\n[2026-05-18 21:53:29 UTC] Vercel SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-05-18 21:42:09 UTC] Vercel SRE (Investigating): We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.", "root_cause_analysis": "Official investigation timeline recorded by Vercel engineering: This incident has been resolved.\n\nSome deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments created outside of this window are unaffected.\n\nThe fix is being rolled out to existing deployments retrospectively and is expected to finish in the next few hours. We are continuing to monitor for any further issues. A fix is rolle", "breaking_config_code": "# Incident architectural state during Increased Function Invocation Errors - ERR_MODULE_NOT_FOUND\nservice_cluster:\n  provider: \"Vercel\"\n  impacted_components: [\"Vercel Edge Network\", \"Serverless Functions\", \"Build Pipeline\", \"AWS Lambda\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Vercel SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Vercel Edge Network cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6knpl12q53h5", "metadata": {"raw_id": "0pl74z9tcpmk", "status": "resolved", "resolved_at": "2026-05-18T23:52:05.000Z"}}
{"incident_id": "INC-2026-DISCORD-yb8bzhp6", "company": "Discord", "date": "2026-10-01", "title": "Elevated API error rate", "severity": "MEDIUM", "service_stack": ["API", "Media Proxy", "Discord Gateway", "Elixir"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-10-01 13:52:47 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-10-01 12:48:10 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Engineering telemetry at Discord detected service interruption across API, Media Proxy, Discord Gateway, Elixir. The incident resulted from capacity saturation and upstream dependency latency. Engineers identified degraded nodes and isolated traffic to restore nominal operations.", "breaking_config_code": "# Incident architectural state during Elevated API error rate\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Media Proxy\", \"Discord Gateway\", \"Elixir\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/d34fn55r326n", "metadata": {"raw_id": "yb8bzhp6nd87", "status": "resolved", "resolved_at": "2026-10-01T13:52:47.181-07:00"}}
{"incident_id": "INC-2026-DISCORD-t00495fy", "company": "Discord", "date": "2026-09-23", "title": "Age group status mismatch across devices", "severity": "HIGH", "service_stack": ["Android", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-23 20:32:10 UTC] Discord SRE (Resolved): This incident has been resolved.\nhttps://x.com/discord/status/2102964092189475028?s=20\n[2026-09-23 20:05:18 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring results.\nPlease close and refresh your app to get the fix for adult status.\n[2026-09-23 19:10:16 UTC] Discord SRE (Identified): We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but \"adult\" on web/desktop. We’re aware of the issue and actively working on a fix.\n[2026-09-23 19:08:27 UTC] Discord SRE (Investigating): We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but \"adult\" on web/desktop. We’re aware of the issue and actively working on a fix.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved.\nhttps://x.com/discord/status/2102964092189475028?s=20 A fix has been implemented and we are monitoring results.\nPlease close and refresh your app to get the fix for adult status. We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but \"adult\" on web/desktop. We’re aware of the issue and actively working", "breaking_config_code": "# Incident architectural state during Age group status mismatch across devices\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Android\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Android cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4pqvfhkn61px", "metadata": {"raw_id": "t00495fymyd6", "status": "resolved", "resolved_at": "2026-09-23T20:32:10.659-07:00"}}
{"incident_id": "INC-2026-DISCORD-610vfhw9", "company": "Discord", "date": "2026-09-17", "title": "Issue / Delay in establishing call connection", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-17 13:39:23 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-17 13:17:58 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-17 13:00:53 UTC] Discord SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-17 11:18:09 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue / Delay in establishing call connection\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/pf0pn82rjd7q", "metadata": {"raw_id": "610vfhw9wjcj", "status": "resolved", "resolved_at": "2026-09-17T13:39:23.299-07:00"}}
{"incident_id": "INC-2026-DISCORD-c9vn3xql", "company": "Discord", "date": "2026-09-16", "title": "Issue establishing voice call", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-16 15:35:09 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-16 15:15:36 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-16 14:45:27 UTC] Discord SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-16 14:32:50 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue establishing voice call\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/7qgn414rhr5z", "metadata": {"raw_id": "c9vn3xqlhzyl", "status": "resolved", "resolved_at": "2026-09-16T15:35:09.325-07:00"}}
{"incident_id": "INC-2026-DISCORD-chpjjdyk", "company": "Discord", "date": "2026-09-16", "title": "API Errors", "severity": "MEDIUM", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-16 12:28:01 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-16 12:20:14 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-16 12:03:28 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during API Errors\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/b8prjyxdvwf7", "metadata": {"raw_id": "chpjjdyk63yt", "status": "resolved", "resolved_at": "2026-09-16T12:28:01.381-07:00"}}
{"incident_id": "INC-2026-DISCORD-1z5kbv8r", "company": "Discord", "date": "2026-09-16", "title": "Google Pay Outage", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-16 09:43:18 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-16 09:15:33 UTC] Discord SRE (Identified): We're currently experiencing an issue that prevents users from completing purchases (including Nitro subscriptions and Shop items) through the Android app. This is caused by an ongoing outage with Google Play.\n\nPurchases on other platforms (iOS, web, and desktop) are unaffected, and existing subscriptions remain active.\n\nWe're monitoring Google's status and will post an update as soon as service is restored. No action is needed on your part — please try again later.\nhttps://pay.google.com/status/incidents/gQJsjf662F7KwPyiNqav", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We're currently experiencing an issue that prevents users from completing purchases (including Nitro subscriptions and Shop items) through the Android app. This is caused by an ongoing outage with Google Play.\n\nPurchases on other platforms (iOS, web, and desktop) are unaffected, and existing subscriptions remain active.\n\nWe're monitoring Google's status and will post an update as soon as service is restored. No ac", "breaking_config_code": "# Incident architectural state during Google Pay Outage\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9qdnzmhbn0pk", "metadata": {"raw_id": "1z5kbv8r5pkv", "status": "resolved", "resolved_at": "2026-09-16T09:43:18.930-07:00"}}
{"incident_id": "INC-2026-DISCORD-btdsd2y4", "company": "Discord", "date": "2026-09-15", "title": "Session Unavailability", "severity": "MEDIUM", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-15 08:16:18 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-15 07:58:33 UTC] Discord SRE (Monitoring): A fix has been implemented and we are currently monitoring recovery of services.\n[2026-09-15 07:42:45 UTC] Discord SRE (Identified): The issue has been identified and we are working to restore service.\n[2026-09-15 07:26:02 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are currently monitoring recovery of services. The issue has been identified and we are working to restore service. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Session Unavailability\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/d5h0d8347s4l", "metadata": {"raw_id": "btdsd2y407t5", "status": "resolved", "resolved_at": "2026-09-15T08:16:18.172-07:00"}}
{"incident_id": "INC-2026-DISCORD-5sp34swn", "company": "Discord", "date": "2026-09-11", "title": "Media Proxy Latency High", "severity": "MEDIUM", "service_stack": ["Media Proxy", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-11 10:46:19 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-11 10:39:12 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-11 09:27:41 UTC] Discord SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-11 09:24:46 UTC] Discord SRE (Investigating): We are currently investigating an issue involving high error-rates for image downloads.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating an issue involving high error-rates for image downloads.", "breaking_config_code": "# Incident architectural state during Media Proxy Latency High\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Media Proxy\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Media Proxy cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/mpwbwtx3wm5q", "metadata": {"raw_id": "5sp34swnxkh0", "status": "resolved", "resolved_at": "2026-09-11T10:46:19.597-07:00"}}
{"incident_id": "INC-2026-DISCORD-d82z44sn", "company": "Discord", "date": "2026-09-10", "title": "Issue with establishing voice calls", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-10 23:42:28 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-10 23:20:46 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-10 21:21:35 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue with establishing voice calls\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6kw0tkg5sg53", "metadata": {"raw_id": "d82z44sn4fpx", "status": "resolved", "resolved_at": "2026-09-10T23:42:28.928-07:00"}}
{"incident_id": "INC-2026-DISCORD-nt3d1xvk", "company": "Discord", "date": "2026-09-03", "title": "Some Servers Unavailable", "severity": "MEDIUM", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-03 15:27:33 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-03 15:06:28 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-03 14:31:27 UTC] Discord SRE (Identified): We've identified an issue causing some servers to appear unavailable in the client", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We've identified an issue causing some servers to appear unavailable in the client", "breaking_config_code": "# Incident architectural state during Some Servers Unavailable\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/3628f7vbg5p8", "metadata": {"raw_id": "nt3d1xvkb9q8", "status": "resolved", "resolved_at": "2026-09-03T15:27:33.274-07:00"}}
{"incident_id": "INC-2026-DISCORD-lf84xp6q", "company": "Discord", "date": "2026-09-03", "title": "Some servers unavailable", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-03 08:37:47 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-03 08:01:44 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-03 07:56:36 UTC] Discord SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-03 07:35:27 UTC] Discord SRE (Investigating): Some servers may appear unavailable in the client. We are investigating", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. Some servers may appear unavailable in the client. We are investigating", "breaking_config_code": "# Incident architectural state during Some servers unavailable\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/c16w1zbh6v2x", "metadata": {"raw_id": "lf84xp6q5qjc", "status": "resolved", "resolved_at": "2026-09-03T08:37:47.454-07:00"}}
{"incident_id": "INC-2026-DISCORD-h3xfmqrq", "company": "Discord", "date": "2026-09-02", "title": "Voice endpoint selection issues", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-02 16:42:44 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-02 16:35:19 UTC] Discord SRE (Identified): We've identified an issue with our endpoint selection service and are applying a mitigation now. We are seeing recovery to endpoint selection now.\n[2026-09-02 16:26:42 UTC] Discord SRE (Investigating): We are investigating problems with voice endpoint selection. Your calls may fail to start or may fail to get an endpoint.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We've identified an issue with our endpoint selection service and are applying a mitigation now. We are seeing recovery to endpoint selection now. We are investigating problems with voice endpoint selection. Your calls may fail to start or may fail to get an endpoint.", "breaking_config_code": "# Incident architectural state during Voice endpoint selection issues\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ys9tgzwhjxtk", "metadata": {"raw_id": "h3xfmqrqhqw3", "status": "resolved", "resolved_at": "2026-09-02T16:42:44.301-07:00"}}
{"incident_id": "INC-2026-DISCORD-ty5bs3l7", "company": "Discord", "date": "2026-09-02", "title": "Server Unavailability", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-02 11:26:50 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-09-02 11:18:14 UTC] Discord SRE (Monitoring): We have recovered. We are still investigating the root cause and will post an update once we have more information\n[2026-09-02 10:51:02 UTC] Discord SRE (Investigating): We are still investigating the issue, some servers are continuing to have a degraded experience\n[2026-09-02 10:04:15 UTC] Discord SRE (Investigating): We are continuing to investigate this issue\n[2026-09-02 09:12:20 UTC] Discord SRE (Investigating): We're investigating an issue where some servers are offline.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We have recovered. We are still investigating the root cause and will post an update once we have more information We are still investigating the issue, some servers are continuing to have a degraded experience We are continuing to investigate this issue We're investigating an issue where some servers are offline.", "breaking_config_code": "# Incident architectural state during Server Unavailability\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/1msh0252j36w", "metadata": {"raw_id": "ty5bs3l7xgcf", "status": "resolved", "resolved_at": "2026-09-02T11:26:50.199-07:00"}}
{"incident_id": "INC-2026-DISCORD-xpz8zbrd", "company": "Discord", "date": "2026-08-31", "title": "Some servers and other services (voice calls, activities) not available for some users", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-08-31 17:49:17 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-08-31 16:56:45 UTC] Discord SRE (Identified): We are taking steps to remediate the issue\n[2026-08-31 16:38:47 UTC] Discord SRE (Investigating): We are taking steps to remediate the issue\n[2026-08-31 16:26:49 UTC] Discord SRE (Investigating): some servers will appear unavailable for some users, and some other services may also be impacted (voice calls, activities)\n[2026-08-31 15:54:05 UTC] Discord SRE (Investigating): Some users may not be able to connect to some of their servers", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We are taking steps to remediate the issue We are taking steps to remediate the issue some servers will appear unavailable for some users, and some other services may also be impacted (voice calls, activities) Some users may not be able to connect to some of their servers", "breaking_config_code": "# Incident architectural state during Some servers and other services (voice calls, activities) not available for some users\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/11m73f3r9hhd", "metadata": {"raw_id": "xpz8zbrdkgs2", "status": "resolved", "resolved_at": "2026-08-31T17:49:17.176-07:00"}}
{"incident_id": "INC-2026-DISCORD-xtbm1jcf", "company": "Discord", "date": "2026-08-13", "title": "Issue with establishing a call", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-08-13 23:24:04 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-08-13 23:14:34 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-08-13 23:09:38 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue with establishing a call\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/kg7n5686hk7n", "metadata": {"raw_id": "xtbm1jcfkbcs", "status": "resolved", "resolved_at": "2026-08-13T23:24:04.508-07:00"}}
{"incident_id": "INC-2026-DISCORD-pcg3nsfq", "company": "Discord", "date": "2026-08-07", "title": "Issues sending messages for bots and users", "severity": "CRITICAL", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-07 16:02:18 UTC] Discord SRE (Resolved): This issue has been fully resolved\n[2026-08-07 15:42:09 UTC] Discord SRE (Monitoring): We've recovered service and are continuing to monitor for recovery.\n[2026-08-07 15:26:32 UTC] Discord SRE (Identified): This issue has expanded and is now affecting all Discord interactions. We're continuing to work towards mitigating the issue.\n[2026-08-07 15:21:42 UTC] Discord SRE (Identified): We're aware of an issue preventing users and bots from sending messages, we're working on fully restoring service", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This issue has been fully resolved We've recovered service and are continuing to monitor for recovery. This issue has expanded and is now affecting all Discord interactions. We're continuing to work towards mitigating the issue. We're aware of an issue preventing users and bots from sending messages, we're working on fully restoring service", "breaking_config_code": "# Incident architectural state during Issues sending messages for bots and users\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9y6394dfz8kw", "metadata": {"raw_id": "pcg3nsfq6l2y", "status": "resolved", "resolved_at": "2026-08-07T16:02:18.715-07:00"}}
{"incident_id": "INC-2026-DISCORD-73wgk29d", "company": "Discord", "date": "2026-08-04", "title": "Messaging failures", "severity": "CRITICAL", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-04 13:17:15 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-08-04 12:59:24 UTC] Discord SRE (Monitoring): We're seeing significant positive impact from our earlier fix; nearly all users should be recovered at this point. We are monitoring closely.\n[2026-08-04 12:53:43 UTC] Discord SRE (Monitoring): We have a fix in place are seeing recovery, although some users may still be seeing impact.\n[2026-08-04 12:36:19 UTC] Discord SRE (Identified): We are actively working toward system recovery and will post another update in 10 minutes.\n[2026-08-04 11:50:03 UTC] Discord SRE (Identified): We are continuing to work on a fix for this issue.\n[2026-08-04 11:49:50 UTC] Discord SRE (Identified): We are currently investigating an issue that is impacting users' ability to send direct messages. Other functionality including interactions, shop, and SDK integrations are also affected.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We're seeing significant positive impact from our earlier fix; nearly all users should be recovered at this point. We are monitoring closely. We have a fix in place are seeing recovery, although some users may still be seeing impact. We are actively working toward system recovery and will post another update in 10 minutes. We are continuing to work on a fix for this issue. We are currently investigating an issue t", "breaking_config_code": "# Incident architectural state during Messaging failures\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/wlryy8d8r7wf", "metadata": {"raw_id": "73wgk29dznv4", "status": "resolved", "resolved_at": "2026-08-04T13:17:15.330-07:00"}}
{"incident_id": "INC-2026-DISCORD-0gz6pdq1", "company": "Discord", "date": "2026-07-27", "title": "session starts, DM message delivery down", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-07-27 11:05:48 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-07-27 10:48:46 UTC] Discord SRE (Investigating): You may have issues logging in or not receiving DM messages live", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. You may have issues logging in or not receiving DM messages live", "breaking_config_code": "# Incident architectural state during session starts, DM message delivery down\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/m3f8f3hwc75m", "metadata": {"raw_id": "0gz6pdq1c141", "status": "resolved", "resolved_at": "2026-07-27T11:05:48.565-07:00"}}
{"incident_id": "INC-2026-DISCORD-g196lnx3", "company": "Discord", "date": "2026-07-22", "title": "unable to establish voice connection", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-07-22 16:57:46 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-07-22 16:49:20 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-22 16:32:44 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during unable to establish voice connection\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/b029r8spc5j3", "metadata": {"raw_id": "g196lnx3h2cz", "status": "resolved", "resolved_at": "2026-07-22T16:57:46.890-07:00"}}
{"incident_id": "INC-2026-DISCORD-vwmnnymc", "company": "Discord", "date": "2026-07-16", "title": "API Errors", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-07-16 20:48:44 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-07-16 18:51:51 UTC] Discord SRE (Identified): We've identified an upstream latency issue, and we're working to mitigate its impacts.\n[2026-07-16 17:49:10 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We've identified an upstream latency issue, and we're working to mitigate its impacts. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during API Errors\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/dn6zshm4sygl", "metadata": {"raw_id": "vwmnnymc48b9", "status": "resolved", "resolved_at": "2026-07-16T20:48:44.191-07:00"}}
{"incident_id": "INC-2026-DISCORD-yj1xklr7", "company": "Discord", "date": "2026-07-10", "title": "Issues with billing operations", "severity": "HIGH", "service_stack": ["API", "Payments", "Discord Gateway", "Elixir"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-07-10 12:33:31 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-07-10 10:11:02 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-10 09:49:34 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issues with billing operations\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Payments\", \"Discord Gateway\", \"Elixir\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0j2xlzm53hb2", "metadata": {"raw_id": "yj1xklr7ynwg", "status": "resolved", "resolved_at": "2026-07-10T12:33:31.569-07:00"}}
{"incident_id": "INC-2026-DISCORD-9kp14l66", "company": "Discord", "date": "2026-06-29", "title": "Intermittent chat functionality issues", "severity": "MEDIUM", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-06-29 13:24:21 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-06-29 11:46:22 UTC] Discord SRE (Investigating): We are currently investigating the issue.", "root_cause_analysis": "Engineering telemetry at Discord detected service interruption across API, Discord Gateway, Elixir, ScyllaDB. The incident resulted from capacity saturation and upstream dependency latency. Engineers identified degraded nodes and isolated traffic to restore nominal operations.", "breaking_config_code": "# Incident architectural state during Intermittent chat functionality issues\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/kkdbyktwf42v", "metadata": {"raw_id": "9kp14l66ty8s", "status": "resolved", "resolved_at": "2026-06-29T13:24:21.260-07:00"}}
{"incident_id": "INC-2026-DISCORD-rtskh59j", "company": "Discord", "date": "2026-06-10", "title": "Activities cannot be launched", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-06-10 11:35:12 UTC] Discord SRE (Resolved): This incident has been resolved\n[2026-06-10 11:21:09 UTC] Discord SRE (Monitoring): We are ramping up traffic for activities\n[2026-06-10 10:15:38 UTC] Discord SRE (Identified): We have currently disabled activities and are working towards a resolution", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved We are ramping up traffic for activities We have currently disabled activities and are working towards a resolution", "breaking_config_code": "# Incident architectural state during Activities cannot be launched\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/sxth7s567by1", "metadata": {"raw_id": "rtskh59jhdp2", "status": "resolved", "resolved_at": "2026-06-10T11:35:12.294-07:00"}}
{"incident_id": "INC-2026-DISCORD-w13pp3bc", "company": "Discord", "date": "2026-06-09", "title": "All clients may see issues connecting to Discord", "severity": "HIGH", "service_stack": ["Gateway", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-06-09 14:44:14 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-06-09 14:37:09 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-09 14:30:41 UTC] Discord SRE (Identified): We are letting in more connections as capacity allows\n[2026-06-09 14:24:31 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are letting in more connections as capacity allows We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during All clients may see issues connecting to Discord\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Gateway\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/2nt2792k0yg8", "metadata": {"raw_id": "w13pp3bc12v3", "status": "resolved", "resolved_at": "2026-06-09T14:44:14.070-07:00"}}
{"incident_id": "INC-2026-DISCORD-vrdywypm", "company": "Discord", "date": "2026-05-21", "title": "API errors affecting message sends, session starts, and billing operations", "severity": "HIGH", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-05-21 20:39:59 UTC] Discord SRE (Resolved): We have applied a fix and are seeing recovery across our systems\n[2026-05-21 18:55:44 UTC] Discord SRE (Identified): We're aware of an issue that is affecting a subset of users trying to interact with our services. We are working on  a fix to address the issues.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: We have applied a fix and are seeing recovery across our systems We're aware of an issue that is affecting a subset of users trying to interact with our services. We are working on  a fix to address the issues.", "breaking_config_code": "# Incident architectural state during API errors affecting message sends, session starts, and billing operations\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/5xc5drn5x1p8", "metadata": {"raw_id": "vrdywypml5lf", "status": "resolved", "resolved_at": "2026-05-21T20:39:59.372-07:00"}}
{"incident_id": "INC-2026-DISCORD-7p0t57dd", "company": "Discord", "date": "2026-05-08", "title": "Guild + Session Availability", "severity": "MEDIUM", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-05-09 00:01:44 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-05-08 23:54:07 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-05-08 23:25:52 UTC] Discord SRE (Investigating): We're investigating an availability where some users may be unable to start a session or some guilds may be unable to connect.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We're investigating an availability where some users may be unable to start a session or some guilds may be unable to connect.", "breaking_config_code": "# Incident architectural state during Guild + Session Availability\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/p9zy8727d9w0", "metadata": {"raw_id": "7p0t57ddsbgk", "status": "resolved", "resolved_at": "2026-05-09T00:01:44.236-07:00"}}
{"incident_id": "INC-2026-DISCORD-4hpm4454", "company": "Discord", "date": "2026-05-08", "title": "Increased API Errors", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-05-08 15:38:17 UTC] Discord SRE (Resolved): All critical functionalities have recovered for all users.\n[2026-05-08 14:47:02 UTC] Discord SRE (Identified): Users are able to connect to the platform, and we are working on recovering some features\n[2026-05-08 14:08:03 UTC] Discord SRE (Identified): We are continuing to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state\n[2026-05-08 13:19:48 UTC] Discord SRE (Identified): We are beginning to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state\n[2026-05-08 13:16:52 UTC] Discord SRE (Monitoring): We are seeing significant recovery at this time. We are continue to restore ancillary services and we are metering in traffic as users reconnect.\n[2026-05-08 12:56:03 UTC] Discord SRE (Identified): We are continuing to work to remediate the issues impacting availability for some Discord users. This is causing impact across our service, including logging in and sending messages.\n[2026-05-08 12:24:48 UTC] Discord SRE (Identified): We have identified the issue. Many users are unable to start their sessions at this time\n[2026-05-08 12:08:32 UTC] Discord SRE (Investigating): We're investgating errors in our API systems.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: All critical functionalities have recovered for all users. Users are able to connect to the platform, and we are working on recovering some features We are continuing to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state We are beginning to see recovery on our systems and are continuing recovery operations to get the service into a fully healthy state We are seeing significant recovery", "breaking_config_code": "# Incident architectural state during Increased API Errors\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/yj8w3fd3p7jn", "metadata": {"raw_id": "4hpm4454hxtx", "status": "resolved", "resolved_at": "2026-05-08T15:38:17.335-07:00"}}
{"incident_id": "INC-2026-DISCORD-k42p6rqy", "company": "Discord", "date": "2026-05-02", "title": "Message Sends affected on certain channels", "severity": "HIGH", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-05-02 10:29:17 UTC] Discord SRE (Resolved): We've resolved the issue and messaging should be functional\n[2026-05-02 10:03:31 UTC] Discord SRE (Investigating): We are currently investigating the issue", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: We've resolved the issue and messaging should be functional We are currently investigating the issue", "breaking_config_code": "# Incident architectural state during Message Sends affected on certain channels\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/p6fddpk44db0", "metadata": {"raw_id": "k42p6rqypf7v", "status": "resolved", "resolved_at": "2026-05-02T10:29:17.660-07:00"}}
{"incident_id": "INC-2026-DISCORD-mjj0126t", "company": "Discord", "date": "2026-04-28", "title": "Connection Delays", "severity": "MEDIUM", "service_stack": ["Gateway", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-04-28 14:12:03 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-04-28 14:02:50 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-04-28 12:29:39 UTC] Discord SRE (Investigating): We are investigating issues with large guilds being unavailable\n[2026-04-28 12:20:14 UTC] Discord SRE (Investigating): Users are experiencing delays connecting to the platform. We are investigating", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are investigating issues with large guilds being unavailable Users are experiencing delays connecting to the platform. We are investigating", "breaking_config_code": "# Incident architectural state during Connection Delays\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Gateway\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/xmt90d9bj9fm", "metadata": {"raw_id": "mjj0126tzs2r", "status": "resolved", "resolved_at": "2026-04-28T14:12:03.026-07:00"}}
{"incident_id": "INC-2026-DISCORD-g904ygw2", "company": "Discord", "date": "2026-04-18", "title": "User Profile Errors", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-04-18 20:52:20 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-04-18 20:41:33 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-04-18 19:37:27 UTC] Discord SRE (Investigating): We're investigating an issue where some users may be unable to update their user profile.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We're investigating an issue where some users may be unable to update their user profile.", "breaking_config_code": "# Incident architectural state during User Profile Errors\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/jvy2q3ghtcyn", "metadata": {"raw_id": "g904ygw2n408", "status": "resolved", "resolved_at": "2026-04-18T20:52:20.329-07:00"}}
{"incident_id": "INC-2026-DISCORD-947scltt", "company": "Discord", "date": "2026-04-16", "title": "Issues with invites", "severity": "MEDIUM", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-04-16 13:30:06 UTC] Discord SRE (Resolved): The issue has been resolved.\n[2026-04-16 13:05:42 UTC] Discord SRE (Monitoring): The rollback is progressing and we are monitoring recovery.\n[2026-04-16 12:49:08 UTC] Discord SRE (Identified): The issue has been identified and changes are being rolled back.\n[2026-04-16 12:47:09 UTC] Discord SRE (Investigating): We are currently investigating issues interacting with invites.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: The issue has been resolved. The rollback is progressing and we are monitoring recovery. The issue has been identified and changes are being rolled back. We are currently investigating issues interacting with invites.", "breaking_config_code": "# Incident architectural state during Issues with invites\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ktpv1rcvk1dr", "metadata": {"raw_id": "947scltt0c6j", "status": "resolved", "resolved_at": "2026-04-16T13:30:06.453-07:00"}}
{"incident_id": "INC-2026-DISCORD-44jrtg7v", "company": "Discord", "date": "2026-04-06", "title": "Embeds not working", "severity": "MEDIUM", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-04-06 19:52:03 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-04-06 19:46:05 UTC] Discord SRE (Monitoring): A fix has been deployed and we're monitoring the results.\n[2026-04-06 19:28:12 UTC] Discord SRE (Identified): The issue has been identified and a fix is being deployed.\n[2026-04-06 18:48:05 UTC] Discord SRE (Investigating): We are currently investigating an issue with embeds.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been deployed and we're monitoring the results. The issue has been identified and a fix is being deployed. We are currently investigating an issue with embeds.", "breaking_config_code": "# Incident architectural state during Embeds not working\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ll3l61zny6dp", "metadata": {"raw_id": "44jrtg7vmnzx", "status": "resolved", "resolved_at": "2026-04-06T19:52:03.247-07:00"}}
{"incident_id": "INC-2026-DISCORD-zsm67cmj", "company": "Discord", "date": "2026-03-30", "title": "Captchas Not Showing", "severity": "MEDIUM", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-03-30 22:36:51 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-30 22:30:11 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-30 22:11:48 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Captchas Not Showing\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0lg0s3rbj1cp", "metadata": {"raw_id": "zsm67cmjp81g", "status": "resolved", "resolved_at": "2026-03-30T22:36:51.800-07:00"}}
{"incident_id": "INC-2026-DISCORD-jt67pjfb", "company": "Discord", "date": "2026-03-28", "title": "General API errors", "severity": "HIGH", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-03-28 14:44:16 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-28 14:43:17 UTC] Discord SRE (Monitoring): We are continuing to monitor for any further issues.\n[2026-03-28 14:40:00 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-28 14:31:52 UTC] Discord SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-03-28 14:23:50 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We are continuing to monitor for any further issues. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during General API errors\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ydgzkcnrmmxx", "metadata": {"raw_id": "jt67pjfbbs3q", "status": "resolved", "resolved_at": "2026-03-28T14:44:16.991-07:00"}}
{"incident_id": "INC-2026-DISCORD-9sng5r2j", "company": "Discord", "date": "2026-03-25", "title": "Issues connecting to Discord", "severity": "CRITICAL", "service_stack": ["API", "Gateway", "Discord Gateway", "Elixir"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-03-25 15:38:17 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-25 14:26:33 UTC] Discord SRE (Monitoring): Voice and video should have recovered and users should be able to connect to voice calls. \nWe are still tracking down issues with our API.\n[2026-03-25 13:07:21 UTC] Discord SRE (Identified): We believe we have identified the issue and are taking action to try and restore voice traffic\n[2026-03-25 12:46:21 UTC] Discord SRE (Investigating): We're continuing to investigate impacts to voice connectivity. There may be some temporary impacts to other features as we work to accelerate recovery.\n[2026-03-25 12:21:47 UTC] Discord SRE (Investigating): We're aware of an issue that is preventing people from connecting to Discord - we're actively investigating", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. Voice and video should have recovered and users should be able to connect to voice calls. \nWe are still tracking down issues with our API. We believe we have identified the issue and are taking action to try and restore voice traffic We're continuing to investigate impacts to voice connectivity. There may be some temporary impacts to other features as we work to accelerate recovery. We're aware of an issue that is", "breaking_config_code": "# Incident architectural state during Issues connecting to Discord\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Gateway\", \"Discord Gateway\", \"Elixir\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/61fw0d5ddysp", "metadata": {"raw_id": "9sng5r2j71sq", "status": "resolved", "resolved_at": "2026-03-25T15:38:17.907-07:00"}}
{"incident_id": "INC-2026-DISCORD-hm33xk31", "company": "Discord", "date": "2026-03-25", "title": "Elevated errors for streaming and messaging", "severity": "MEDIUM", "service_stack": ["API", "Push Notifications", "Discord Gateway", "Elixir"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-03-25 08:51:12 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-25 08:43:58 UTC] Discord SRE (Monitoring): We have identified the source of the issues and are monitoring recovery.\n[2026-03-25 08:18:46 UTC] Discord SRE (Investigating): We are investigating degraded performance affecting some Discord features, including streaming and messaging, due to a networking issue beginning at approximately 7:53 AM PT; our team is actively engaged with our cloud provider to resolve the issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We have identified the source of the issues and are monitoring recovery. We are investigating degraded performance affecting some Discord features, including streaming and messaging, due to a networking issue beginning at approximately 7:53 AM PT; our team is actively engaged with our cloud provider to resolve the issue.", "breaking_config_code": "# Incident architectural state during Elevated errors for streaming and messaging\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Push Notifications\", \"Discord Gateway\", \"Elixir\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/fdnrlv6w4jkw", "metadata": {"raw_id": "hm33xk31dk46", "status": "resolved", "resolved_at": "2026-03-25T08:51:12.759-07:00"}}
{"incident_id": "INC-2026-DISCORD-2vw56wyz", "company": "Discord", "date": "2026-03-19", "title": "Failure to start new voice calls", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-03-19 22:56:47 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-19 22:43:58 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-19 19:47:07 UTC] Discord SRE (Investigating): New voice calls are failing to be created. We are currently investigating.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. New voice calls are failing to be created. We are currently investigating.", "breaking_config_code": "# Incident architectural state during Failure to start new voice calls\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4lq25k7pwl99", "metadata": {"raw_id": "2vw56wyzvjqn", "status": "resolved", "resolved_at": "2026-03-19T22:56:47.669-07:00"}}
{"incident_id": "INC-2026-DISCORD-dsv750sj", "company": "Discord", "date": "2026-03-12", "title": "Applications experiencing 503 errors", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-03-12 14:06:00 UTC] Discord SRE (Resolved): We believe the 503s have been resolved.\n[2026-03-12 13:50:26 UTC] Discord SRE (Investigating): We are aware that bot traffic may be hitting 503 errors and are investigating the issue.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: We believe the 503s have been resolved. We are aware that bot traffic may be hitting 503 errors and are investigating the issue.", "breaking_config_code": "# Incident architectural state during Applications experiencing 503 errors\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/lyp50tfbf531", "metadata": {"raw_id": "dsv750sj44fn", "status": "resolved", "resolved_at": "2026-03-12T14:06:00.560-07:00"}}
{"incident_id": "INC-2026-DISCORD-jxpmdts2", "company": "Discord", "date": "2026-03-12", "title": "Applications experiencing 503 errors", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-03-12 14:04:13 UTC] Discord SRE (Resolved): We believe that the 503s have been resolved.", "root_cause_analysis": "Engineering telemetry at Discord detected service interruption across Discord Gateway, Elixir, ScyllaDB, WebSockets. The incident resulted from capacity saturation and upstream dependency latency. Engineers identified degraded nodes and isolated traffic to restore nominal operations.", "breaking_config_code": "# Incident architectural state during Applications experiencing 503 errors\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/mznzwkb63ghw", "metadata": {"raw_id": "jxpmdts24t6d", "status": "resolved", "resolved_at": "2026-03-12T14:04:13.386-07:00"}}
{"incident_id": "INC-2026-DISCORD-nhs3zcp3", "company": "Discord", "date": "2026-03-11", "title": "Some servers unavailable", "severity": "HIGH", "service_stack": ["Gateway", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-03-11 16:33:11 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-11 16:11:26 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-11 16:07:08 UTC] Discord SRE (Identified): They should be back shortly", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. They should be back shortly", "breaking_config_code": "# Incident architectural state during Some servers unavailable\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Gateway\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/x89wjkrxkyvx", "metadata": {"raw_id": "nhs3zcp3g3j7", "status": "resolved", "resolved_at": "2026-03-11T16:33:11.258-07:00"}}
{"incident_id": "INC-2026-DISCORD-k22tny62", "company": "Discord", "date": "2026-03-02", "title": "A/V E2EE Enforcement for Non-stage Voice Calls", "severity": "MEDIUM", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-03-11 10:25:06 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-02 12:02:15 UTC] Discord SRE (Monitoring): Updated clients which support the DAVE (Audio & Video End-to-End Encryption) Protocol are now required to connect to non-stages voice calls across the Discord Platform. If you attempt to connect with an out of date client, the voice gateway will reject your connection with close code 4017.\n\nSee https://support.discord.com/hc/en-us/articles/38025123604631-Minimum-Client-Version-Requirements-for-Voice-Chat for minimum client version requirements and https://support.discord.com/hc/en-us/articles/25968222946071-End-to-End-Encryption-for-Audio-and-Video for further details.\n\nChromeOS devices should now be able to connect voice channels after refreshing the Discord application.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. Updated clients which support the DAVE (Audio & Video End-to-End Encryption) Protocol are now required to connect to non-stages voice calls across the Discord Platform. If you attempt to connect with an out of date client, the voice gateway will reject your connection with close code 4017.\n\nSee https://support.discord.com/hc/en-us/articles/38025123604631-Minimum-Client-Version-Requirements-for-Voice-Chat for minim", "breaking_config_code": "# Incident architectural state during A/V E2EE Enforcement for Non-stage Voice Calls\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/vwcdsf0ngghc", "metadata": {"raw_id": "k22tny62jcw3", "status": "resolved", "resolved_at": "2026-03-11T10:25:06.008-07:00"}}
{"incident_id": "INC-2026-DISCORD-clqzb7y8", "company": "Discord", "date": "2026-03-09", "title": "Issues sending and loading messages", "severity": "HIGH", "service_stack": ["API", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-03-09 10:58:48 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-09 10:29:18 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-09 10:22:03 UTC] Discord SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-03-09 10:08:03 UTC] Discord SRE (Investigating): Users may experience issues sending and receiving messages.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. Users may experience issues sending and receiving messages.", "breaking_config_code": "# Incident architectural state during Issues sending and loading messages\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/y5d4s8y4g5nw", "metadata": {"raw_id": "clqzb7y8t0r8", "status": "resolved", "resolved_at": "2026-03-09T10:58:48.107-07:00"}}
{"incident_id": "INC-2026-DISCORD-jvqsklfd", "company": "Discord", "date": "2026-03-05", "title": "UK/AU: Issues Completing Age Verification via k-ID", "severity": "MEDIUM", "service_stack": ["Desktop", "iOS", "Android", "Web"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-03-05 19:49:19 UTC] Discord SRE (Resolved): k-ID age verification is operating normally again in the UK and Australia. Previously age verified users were not impacted.\n[2026-03-05 19:38:36 UTC] Discord SRE (Monitoring): k-ID has deployed a fix for UK/AU age verification issues. We’re monitoring to ensure age verification is working normally. Previously age verified users should not be impacted.\n[2026-03-05 19:26:36 UTC] Discord SRE (Investigating): Some users in the UK and Australia may be unable to complete new age verification via k-ID. Users who have already completed age verification should not be impacted. We’re actively working with k-ID on a resolution and will share updates here as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: k-ID age verification is operating normally again in the UK and Australia. Previously age verified users were not impacted. k-ID has deployed a fix for UK/AU age verification issues. We’re monitoring to ensure age verification is working normally. Previously age verified users should not be impacted. Some users in the UK and Australia may be unable to complete new age verification via k-ID. Users who have already completed age verification should", "breaking_config_code": "# Incident architectural state during UK/AU: Issues Completing Age Verification via k-ID\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Desktop\", \"iOS\", \"Android\", \"Web\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Desktop cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0zdtdpxmmxgl", "metadata": {"raw_id": "jvqsklfdcvt8", "status": "resolved", "resolved_at": "2026-03-05T19:49:19.990-08:00"}}
{"incident_id": "INC-2026-DISCORD-f3dxbcrc", "company": "Discord", "date": "2026-03-04", "title": "Guild Unavailability", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-03-04 17:58:07 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-03-04 17:49:28 UTC] Discord SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-03-04 17:37:11 UTC] Discord SRE (Investigating): We're investigating an issue where some guilds are unavailable.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. The issue has been identified and a fix is being implemented. We're investigating an issue where some guilds are unavailable.", "breaking_config_code": "# Incident architectural state during Guild Unavailability\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/k9sdr00kz7sl", "metadata": {"raw_id": "f3dxbcrcsysw", "status": "resolved", "resolved_at": "2026-03-04T17:58:07.567-08:00"}}
{"incident_id": "INC-2026-DISCORD-nm7zsjzv", "company": "Discord", "date": "2026-02-28", "title": "Continued issues with presence and DM delivery", "severity": "HIGH", "service_stack": ["Gateway", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-02-28 14:54:27 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-02-28 14:51:20 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-02-28 14:42:41 UTC] Discord SRE (Identified): This is actually a continuation of the incident from earlier today, which we marked \"resolved\" in error. We have now identified and are remediating the issue\n[2026-02-28 14:28:06 UTC] Discord SRE (Identified): We are currently investigating this issue. Restarting your sessions *should* fix it but existing sessions may have not be seeing new DMs\n[2026-02-28 13:54:29 UTC] Discord SRE (Investigating): We are currently investigating this issue. Restarting your sessions *should* fix it but existing sessions may have not be seeing new DMs", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. This is actually a continuation of the incident from earlier today, which we marked \"resolved\" in error. We have now identified and are remediating the issue We are currently investigating this issue. Restarting your sessions *should* fix it but existing sessions may have not be seeing new DMs We are currently investigating this issue. Restarting your s", "breaking_config_code": "# Incident architectural state during Continued issues with presence and DM delivery\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Gateway\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0ddnmh6vwg2y", "metadata": {"raw_id": "nm7zsjzv8kd2", "status": "resolved", "resolved_at": "2026-02-28T14:54:27.900-08:00"}}
{"incident_id": "INC-2026-DISCORD-fvb0y6yp", "company": "Discord", "date": "2026-02-28", "title": "possible issues with presence and DM delivery", "severity": "MEDIUM", "service_stack": ["Gateway", "Discord Gateway", "Elixir", "ScyllaDB"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-02-28 08:37:54 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-02-28 06:53:57 UTC] Discord SRE (Monitoring): Some users were unable to start sessions, but should be able to now. Some servers were also not available\n[2026-02-28 06:39:39 UTC] Discord SRE (Investigating): you may need to refresh your client to see new DM messages. We are working on identifying the extent of the issue", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. Some users were unable to start sessions, but should be able to now. Some servers were also not available you may need to refresh your client to see new DM messages. We are working on identifying the extent of the issue", "breaking_config_code": "# Incident architectural state during possible issues with presence and DM delivery\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Gateway\", \"Discord Gateway\", \"Elixir\", \"ScyllaDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/x2wy1l9ntk92", "metadata": {"raw_id": "fvb0y6yp00sn", "status": "resolved", "resolved_at": "2026-02-28T08:37:54.888-08:00"}}
{"incident_id": "INC-2026-DISCORD-ptxvtqh0", "company": "Discord", "date": "2026-02-28", "title": "presence briefly dropped, some DM messages not delivered (refresh to receive them)", "severity": "MEDIUM", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-02-28 06:23:53 UTC] Discord SRE (Resolved): We are currently investigating this issue.", "root_cause_analysis": "Engineering telemetry at Discord detected service interruption across Discord Gateway, Elixir, ScyllaDB, WebSockets. The incident resulted from capacity saturation and upstream dependency latency. Engineers identified degraded nodes and isolated traffic to restore nominal operations.", "breaking_config_code": "# Incident architectural state during presence briefly dropped, some DM messages not delivered (refresh to receive them)\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/yd22g77jf1zp", "metadata": {"raw_id": "ptxvtqh0kb24", "status": "resolved", "resolved_at": "2026-02-28T06:00:00.000-08:00"}}
{"incident_id": "INC-2026-DISCORD-3269g35l", "company": "Discord", "date": "2026-02-27", "title": "Unavailable Servers and Voice Calls", "severity": "MEDIUM", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-02-27 14:26:41 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-02-27 13:52:42 UTC] Discord SRE (Investigating): We are investigating an issue where some servers may show up as unavailable and some voice calls may not be able to start.", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. We are investigating an issue where some servers may show up as unavailable and some voice calls may not be able to start.", "breaking_config_code": "# Incident architectural state during Unavailable Servers and Voice Calls\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/sf8s45bxfxvx", "metadata": {"raw_id": "3269g35l9mls", "status": "resolved", "resolved_at": "2026-02-27T14:26:41.734-08:00"}}
{"incident_id": "INC-2026-DISCORD-vh11np1z", "company": "Discord", "date": "2026-01-27", "title": "Voice and video errors", "severity": "HIGH", "service_stack": ["Discord Gateway", "Elixir", "ScyllaDB", "WebSockets"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-01-27 15:03:12 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-01-27 14:56:09 UTC] Discord SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-01-27 13:23:56 UTC] Discord SRE (Investigating): We're investigating an issue that is causing errors joining voice channels or watching streams", "root_cause_analysis": "Official investigation timeline recorded by Discord engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We're investigating an issue that is causing errors joining voice channels or watching streams", "breaking_config_code": "# Incident architectural state during Voice and video errors\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"Discord Gateway\", \"Elixir\", \"ScyllaDB\", \"WebSockets\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Discord Gateway cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/87ly25wnrmsr", "metadata": {"raw_id": "vh11np1zhfbp", "status": "resolved", "resolved_at": "2026-01-27T15:03:12.620-08:00"}}
{"incident_id": "INC-2026-DISCORD-r7nw212j", "company": "Discord", "date": "2026-01-24", "title": "Failing message sends on some channels", "severity": "HIGH", "service_stack": ["API", "Search", "Discord Gateway", "Elixir"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-01-24 22:04:31 UTC] Discord SRE (Resolved): This incident has been resolved.\n[2026-01-24 16:35:08 UTC] Discord SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Engineering telemetry at Discord detected service interruption across API, Search, Discord Gateway, Elixir. The incident resulted from capacity saturation and upstream dependency latency. Engineers identified degraded nodes and isolated traffic to restore nominal operations.", "breaking_config_code": "# Incident architectural state during Failing message sends on some channels\nservice_cluster:\n  provider: \"Discord\"\n  impacted_components: [\"API\", \"Search\", \"Discord Gateway\", \"Elixir\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Discord SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/5gcjghv153m0", "metadata": {"raw_id": "r7nw212j7k2m", "status": "resolved", "resolved_at": "2026-01-24T22:04:31.034-08:00"}}
{"incident_id": "INC-2026-NPM-zff9xpz8", "company": "npm", "date": "2026-09-27", "title": "Issues with npm package publish and private install", "severity": "MEDIUM", "service_stack": ["Package installation", "Package publishing", "Replication Feed", "npm Registry"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-27 06:47:55 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-09-27 01:30:21 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-27 00:50:53 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issues with npm package publish and private install\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"Package publishing\", \"Replication Feed\", \"npm Registry\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6vpfpf4dmrnh", "metadata": {"raw_id": "zff9xpz80gwf", "status": "resolved", "resolved_at": "2026-09-27T06:47:55.027Z"}}
{"incident_id": "INC-2026-NPM-y5yr5z8g", "company": "npm", "date": "2026-09-15", "title": "Package Publish Degradation", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-15 18:19:35 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-09-15 18:18:47 UTC] npm SRE (Identified): Stable\n[2026-09-15 17:20:13 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-09-15 17:20:05 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. Stable The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Package Publish Degradation\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/vqff57fc76z8", "metadata": {"raw_id": "y5yr5z8grj7q", "status": "resolved", "resolved_at": "2026-09-15T18:19:35.922Z"}}
{"incident_id": "INC-2026-NPM-s219g6z1", "company": "npm", "date": "2026-09-15", "title": "Publishing Packages Degraded Performance", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-15 16:35:22 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-09-15 16:13:46 UTC] npm SRE (Investigating): We are investigating delays affecting npm package publishing. Some newly published package versions may take longer than expected to become available.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. We are investigating delays affecting npm package publishing. Some newly published package versions may take longer than expected to become available.", "breaking_config_code": "# Incident architectural state during Publishing Packages Degraded Performance\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6qm87tplptny", "metadata": {"raw_id": "s219g6z13p2n", "status": "resolved", "resolved_at": "2026-09-15T16:35:22.642Z"}}
{"incident_id": "INC-2026-NPM-l4f53bbr", "company": "npm", "date": "2026-09-04", "title": "npm audits endpoint is having issues", "severity": "MEDIUM", "service_stack": ["Security Audit", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-04 13:48:36 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-09-04 13:27:00 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-04 11:29:00 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during npm audits endpoint is having issues\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Security Audit\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Security Audit cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/hv9b8g0tycq7", "metadata": {"raw_id": "l4f53bbr9200", "status": "resolved", "resolved_at": "2026-09-04T13:48:36.503Z"}}
{"incident_id": "INC-2026-NPM-b6958bgj", "company": "npm", "date": "2026-09-03", "title": "Intermittent Failures Impacting npm Publish", "severity": "MEDIUM", "service_stack": ["Package installation", "Package publishing", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-03 23:21:04 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-09-03 22:41:21 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-09-03 22:17:43 UTC] npm SRE (Investigating): We are continuing to investigate this issue.\n[2026-09-03 21:42:03 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to investigate this issue. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Intermittent Failures Impacting npm Publish\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"Package publishing\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/n9gnn5fgb3x0", "metadata": {"raw_id": "b6958bgj1sm3", "status": "resolved", "resolved_at": "2026-09-03T23:21:04.999Z"}}
{"incident_id": "INC-2026-NPM-r3v0vxwk", "company": "npm", "date": "2026-07-30", "title": "intermittent Publish Failures", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-30 16:30:37 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-07-30 15:21:51 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-30 12:06:39 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during intermittent Publish Failures\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/dd7tgr1zktrd", "metadata": {"raw_id": "r3v0vxwksk7s", "status": "resolved", "resolved_at": "2026-07-30T16:30:37.632Z"}}
{"incident_id": "INC-2026-NPM-nwz55wql", "company": "npm", "date": "2026-07-24", "title": "Publish and Install failures", "severity": "HIGH", "service_stack": ["Package installation", "Package publishing", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-24 11:38:53 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-07-24 11:36:03 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-24 11:32:00 UTC] npm SRE (Investigating): We are continuing to investigate this issue.\n[2026-07-24 11:08:16 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to investigate this issue. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Publish and Install failures\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"Package publishing\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/gmsqtxv0pw4t", "metadata": {"raw_id": "nwz55wql2vlc", "status": "resolved", "resolved_at": "2026-07-24T11:38:53.142Z"}}
{"incident_id": "INC-2026-NPM-w5jftzvf", "company": "npm", "date": "2026-07-23", "title": "intermittent Publish and Install Failures", "severity": "MEDIUM", "service_stack": ["Package installation", "Package publishing", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-23 19:52:13 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-07-23 18:04:22 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-07-23 16:09:33 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during intermittent Publish and Install Failures\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"Package publishing\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/83zl9bxq2zjv", "metadata": {"raw_id": "w5jftzvfc8dr", "status": "resolved", "resolved_at": "2026-07-23T19:52:13.048Z"}}
{"incident_id": "INC-2026-NPM-7574lvmf", "company": "npm", "date": "2026-06-12", "title": "intermittent Publish Failures", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-12 12:57:11 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-06-12 12:44:28 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-06-12 12:33:08 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-06-12 12:08:45 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during intermittent Publish Failures\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/nfrqyp1lqxm1", "metadata": {"raw_id": "7574lvmfqxg4", "status": "resolved", "resolved_at": "2026-06-12T12:57:11.898Z"}}
{"incident_id": "INC-2026-NPM-h2yc0jb1", "company": "npm", "date": "2026-04-29", "title": "npm website issues", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-04-29 20:49:19 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-04-29 20:49:10 UTC] npm SRE (Investigating): We are continuing to investigate this issue.\n[2026-04-29 20:07:03 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. We are continuing to investigate this issue. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during npm website issues\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/hjbyk95wj0lm", "metadata": {"raw_id": "h2yc0jb1h4hr", "status": "resolved", "resolved_at": "2026-04-29T20:49:19.445Z"}}
{"incident_id": "INC-2026-NPM-5d5wyzgs", "company": "npm", "date": "2026-04-29", "title": "Degraded Performance in View Package and Login on npmjs.com", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-04-29 19:35:36 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-04-29 18:47:09 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-04-29 16:48:33 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Degraded Performance in View Package and Login on npmjs.com\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/l7v8c09r84v3", "metadata": {"raw_id": "5d5wyzgs0yvg", "status": "resolved", "resolved_at": "2026-04-29T19:35:36.995Z"}}
{"incident_id": "INC-2026-NPM-blv1c65x", "company": "npm", "date": "2026-04-28", "title": "npm website degraded service", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-04-28 22:24:35 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-04-28 21:04:30 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-04-28 19:55:01 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during npm website degraded service\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/7ztl7g3pp518", "metadata": {"raw_id": "blv1c65xmwwd", "status": "resolved", "resolved_at": "2026-04-28T22:24:35.441Z"}}
{"incident_id": "INC-2026-NPM-7q86pc3q", "company": "npm", "date": "2026-04-27", "title": "npm Website is unavailable", "severity": "CRITICAL", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-04-27 22:30:40 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-04-27 22:28:38 UTC] npm SRE (Investigating): We are continuing to investigate this issue.\n[2026-04-27 21:06:13 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. We are continuing to investigate this issue. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during npm Website is unavailable\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/hzv35p2qrz32", "metadata": {"raw_id": "7q86pc3q1zgv", "status": "resolved", "resolved_at": "2026-04-27T22:30:40.261Z"}}
{"incident_id": "INC-2026-NPM-y715hyy1", "company": "npm", "date": "2026-04-01", "title": "Increased errors in viewing packages and authentication on npmjs.com", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-04-01 13:12:14 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-04-01 12:20:44 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-04-01 10:05:18 UTC] npm SRE (Investigating): We are observing increased errors in viewing packages and authentication on npmjs website. We are investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are observing increased errors in viewing packages and authentication on npmjs website. We are investigating this issue.", "breaking_config_code": "# Incident architectural state during Increased errors in viewing packages and authentication on npmjs.com\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ck61p1vklx7l", "metadata": {"raw_id": "y715hyy146p2", "status": "resolved", "resolved_at": "2026-04-01T13:12:14.540Z"}}
{"incident_id": "INC-2026-NPM-71xrzlv2", "company": "npm", "date": "2026-03-31", "title": "Degraded Performance in View Package and Login on npmjs.com", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-03-31 21:49:23 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-03-31 21:12:30 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-31 20:42:13 UTC] npm SRE (Investigating): We have implemented initial fixes and are continuing to investigate this issue\n[2026-03-31 19:12:32 UTC] npm SRE (Investigating): We are seeing degraded performance in package viewing and authentication on npmjs website. We are currently investigating the issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We have implemented initial fixes and are continuing to investigate this issue We are seeing degraded performance in package viewing and authentication on npmjs website. We are currently investigating the issue.", "breaking_config_code": "# Incident architectural state during Degraded Performance in View Package and Login on npmjs.com\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ksspyfc8tm1q", "metadata": {"raw_id": "71xrzlv2ddvz", "status": "resolved", "resolved_at": "2026-03-31T21:49:23.294Z"}}
{"incident_id": "INC-2026-NPM-4c9s71vs", "company": "npm", "date": "2026-03-30", "title": "delay and errors viewing packages and submitting web based authentication", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["QUEUE_DELAY", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-03-30 19:17:37 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-03-30 18:19:27 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-30 17:56:30 UTC] npm SRE (Investigating): We have implemented some initial fixes. We are continuing to investigate the issue.\n[2026-03-30 16:41:25 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We have implemented some initial fixes. We are continuing to investigate the issue. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during delay and errors viewing packages and submitting web based authentication\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9h3zy61kv19h", "metadata": {"raw_id": "4c9s71vs4rs6", "status": "resolved", "resolved_at": "2026-03-30T19:17:37.458Z"}}
{"incident_id": "INC-2026-NPM-tnd276td", "company": "npm", "date": "2026-03-30", "title": "delay and errors viewing packages and submitting web based authentication", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["QUEUE_DELAY", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-03-30 15:59:17 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-03-30 15:30:21 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-30 15:17:32 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-03-30 14:54:58 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during delay and errors viewing packages and submitting web based authentication\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/yp6c3lqqsfk5", "metadata": {"raw_id": "tnd276tdmbby", "status": "resolved", "resolved_at": "2026-03-30T15:59:17.415Z"}}
{"incident_id": "INC-2026-NPM-wjpr7d1k", "company": "npm", "date": "2026-03-25", "title": "Issue with npm website and login.", "severity": "HIGH", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-03-25 23:26:04 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-03-25 23:10:48 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-25 22:39:14 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue with npm website and login.\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/64sps5l1qm0t", "metadata": {"raw_id": "wjpr7d1kq5s1", "status": "resolved", "resolved_at": "2026-03-25T23:26:04.736Z"}}
{"incident_id": "INC-2026-NPM-2cfxmzw4", "company": "npm", "date": "2026-03-05", "title": "Degraded performance for package publish", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-03-05 17:35:57 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-03-05 13:01:30 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-03-05 11:41:18 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Degraded performance for package publish\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9sb1ykc8ln68", "metadata": {"raw_id": "2cfxmzw4mqt6", "status": "resolved", "resolved_at": "2026-03-05T17:35:57.112Z"}}
{"incident_id": "INC-2026-NPM-9jrddvx1", "company": "npm", "date": "2026-02-25", "title": "Degraded performance with package installation", "severity": "MEDIUM", "service_stack": ["Package installation", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-02-25 20:03:47 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-02-25 19:28:14 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-02-25 19:24:08 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-02-25 18:43:34 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Degraded performance with package installation\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/2ztpmtcf69vb", "metadata": {"raw_id": "9jrddvx1b89p", "status": "resolved", "resolved_at": "2026-02-25T20:03:47.282Z"}}
{"incident_id": "INC-2026-NPM-gtqg0zs1", "company": "npm", "date": "2026-02-17", "title": "npm publishing impacted", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-02-17 22:28:57 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-02-17 21:17:51 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-02-17 20:01:39 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during npm publishing impacted\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0xz4k5jqmtsp", "metadata": {"raw_id": "gtqg0zs1yvm3", "status": "resolved", "resolved_at": "2026-02-17T22:28:57.831Z"}}
{"incident_id": "INC-2026-NPM-13qztnk1", "company": "npm", "date": "2026-01-29", "title": "Degraded Experience Installing and Viewing Packages", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "Package installation", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-01-29 20:49:34 UTC] npm SRE (Resolved): This incident has been resolved.\n[2026-01-29 20:18:26 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-01-29 20:04:33 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Degraded Experience Installing and Viewing Packages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"Package installation\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/5hlwdsj47fqp", "metadata": {"raw_id": "13qztnk1l4dh", "status": "resolved", "resolved_at": "2026-01-29T20:49:34.667Z"}}
{"incident_id": "INC-2025-NPM-bptmjs4r", "company": "npm", "date": "2025-12-05", "title": "Issue connecting to website and registry", "severity": "HIGH", "service_stack": ["www.npmjs.com website", "Package installation", "Package publishing", "Package search"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-12-05 09:42:42 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-12-05 09:17:50 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-12-05 09:02:54 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue connecting to website and registry\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"Package installation\", \"Package publishing\", \"Package search\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/t0nl12lpj8g6", "metadata": {"raw_id": "bptmjs4rmx8q", "status": "resolved", "resolved_at": "2025-12-05T09:42:42.215Z"}}
{"incident_id": "INC-2025-NPM-67q3d5th", "company": "npm", "date": "2025-11-18", "title": "npmjs.com - Service Disruption", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2025-11-18 19:11:15 UTC] npm SRE (Resolved): We have confirmed that all systems are now fully operational and the connectivity issues have been completely resolved.\n[2025-11-18 19:09:42 UTC] npm SRE (Monitoring): This incident has been resolved. All services are now operating normally. We apologize for the disruption and appreciate your patience.\n[2025-11-18 15:23:07 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-11-18 13:34:33 UTC] npm SRE (Investigating): We are currently investigating intermittent connectivity issues affecting npmjs.com. Our team is actively working to restore full service. We apologize for any inconvenience and will provide updates as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: We have confirmed that all systems are now fully operational and the connectivity issues have been completely resolved. This incident has been resolved. All services are now operating normally. We apologize for the disruption and appreciate your patience. A fix has been implemented and we are monitoring the results. We are currently investigating intermittent connectivity issues affecting npmjs.com. Our team is actively working to restore full se", "breaking_config_code": "# Incident architectural state during npmjs.com - Service Disruption\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rjrg4cyb2nqg", "metadata": {"raw_id": "67q3d5th9kcc", "status": "resolved", "resolved_at": "2025-11-18T19:11:15.245Z"}}
{"incident_id": "INC-2025-NPM-8c94rgnh", "company": "npm", "date": "2025-11-06", "title": "Issue with npm website and login", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2025-11-06 14:28:51 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-11-06 14:08:10 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-11-06 13:58:59 UTC] npm SRE (Investigating): We are continuing to investigate this issue.\n[2025-11-06 13:56:25 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are continuing to investigate this issue. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue with npm website and login\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/lfw28vvn3p24", "metadata": {"raw_id": "8c94rgnhqx9k", "status": "resolved", "resolved_at": "2025-11-06T14:28:51.288Z"}}
{"incident_id": "INC-2025-NPM-7h414wqt", "company": "npm", "date": "2025-10-20", "title": "Issue with package publishing", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-10-20 20:15:20 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-10-20 19:20:08 UTC] npm SRE (Monitoring): We are seeing recovery in package publishing. We will continue to monitor the results.\n[2025-10-20 17:20:06 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. We are seeing recovery in package publishing. We will continue to monitor the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue with package publishing\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/94jlm5t2vx5m", "metadata": {"raw_id": "7h414wqttky8", "status": "resolved", "resolved_at": "2025-10-20T20:15:20.709Z"}}
{"incident_id": "INC-2025-NPM-m3wkdj3c", "company": "npm", "date": "2025-10-20", "title": "Degraded performance of package publish and install", "severity": "MEDIUM", "service_stack": ["Package installation", "Package publishing", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-10-20 13:32:47 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-10-20 10:50:19 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-10-20 09:31:58 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Degraded performance of package publish and install\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"Package publishing\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/60f8ts02gg26", "metadata": {"raw_id": "m3wkdj3c1q57", "status": "resolved", "resolved_at": "2025-10-20T13:32:47.165Z"}}
{"incident_id": "INC-2025-NPM-40dnjfbc", "company": "npm", "date": "2025-10-03", "title": "Degraded performance on npmjs.com", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-10-04 01:42:55 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-10-03 18:07:58 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Engineering telemetry at npm detected service interruption across www.npmjs.com website, npm Registry, CouchDB, Fastly CDN. The incident resulted from capacity saturation and upstream dependency latency. Engineers identified degraded nodes and isolated traffic to restore nominal operations.", "breaking_config_code": "# Incident architectural state during Degraded performance on npmjs.com\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/k4wqlg2ky5dp", "metadata": {"raw_id": "40dnjfbcxj9v", "status": "resolved", "resolved_at": "2025-10-04T01:42:55.683Z"}}
{"incident_id": "INC-2025-NPM-njwnds2v", "company": "npm", "date": "2025-08-26", "title": "Degraded Package Install Experience", "severity": "MEDIUM", "service_stack": ["Package installation", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-08-26 15:49:55 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-08-26 15:16:10 UTC] npm SRE (Monitoring): We are continuing to monitor for any further issues.\n[2025-08-26 15:15:52 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-08-26 14:27:00 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2025-08-26 12:41:00 UTC] npm SRE (Investigating): We are continuing to investigate this issue.\n[2025-08-26 12:40:43 UTC] npm SRE (Investigating): We are investigating an issue where users are experiencing failures during npm install. Errors observed include 429 Too Many Requests and 403 Forbidden  for GitHub Actions.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. We are continuing to monitor for any further issues. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are investigating an issue where users are experiencing failures during npm install. Errors observed include 429 Too Many Requests and 403 Forbidden  for GitHub Actions.", "breaking_config_code": "# Incident architectural state during Degraded Package Install Experience\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9jz91ylgppfp", "metadata": {"raw_id": "njwnds2vmdhz", "status": "resolved", "resolved_at": "2025-08-26T15:49:55.169Z"}}
{"incident_id": "INC-2025-NPM-b0f9jxcs", "company": "npm", "date": "2025-08-07", "title": "Incident with npm registry and website affecting logins and publishing", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "Package installation", "Package publishing", "Security Audit"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2025-08-07 23:05:56 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-08-07 22:46:02 UTC] npm SRE (Monitoring): The issue has been identified and a remediation is being put into place.\n[2025-08-07 22:31:38 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. The issue has been identified and a remediation is being put into place. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Incident with npm registry and website affecting logins and publishing\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"Package installation\", \"Package publishing\", \"Security Audit\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4c99sgtb2c2p", "metadata": {"raw_id": "b0f9jxcs1b67", "status": "resolved", "resolved_at": "2025-08-07T23:05:56.214Z"}}
{"incident_id": "INC-2025-NPM-z95xc4yt", "company": "npm", "date": "2025-06-12", "title": "Issue with package publish with provenance", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-06-12 22:25:08 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-06-12 21:00:22 UTC] npm SRE (Investigating): We are seeing issues with package publish with provenance due to an outage of a key third party dependency.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. We are seeing issues with package publish with provenance due to an outage of a key third party dependency.", "breaking_config_code": "# Incident architectural state during Issue with package publish with provenance\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rtzh6flfmljd", "metadata": {"raw_id": "z95xc4ythnnn", "status": "resolved", "resolved_at": "2025-06-12T22:25:08.695Z"}}
{"incident_id": "INC-2025-NPM-dn5mcp85", "company": "npm", "date": "2025-06-12", "title": "Issues with package install, package publish, and login.", "severity": "HIGH", "service_stack": ["www.npmjs.com website", "Package installation", "Package publishing", "npm Registry"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2025-06-12 20:58:59 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-06-12 20:13:36 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-06-12 19:15:04 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2025-06-12 19:14:46 UTC] npm SRE (Investigating): We are continuing to investigate this issue.\n[2025-06-12 18:14:31 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issues with package install, package publish, and login.\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"Package installation\", \"Package publishing\", \"npm Registry\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/pw7dp1kt5frp", "metadata": {"raw_id": "dn5mcp85737y", "status": "resolved", "resolved_at": "2025-06-12T20:58:59.490Z"}}
{"incident_id": "INC-2025-NPM-bndr0gf8", "company": "npm", "date": "2025-04-11", "title": "Issues publishing and installing packages", "severity": "MEDIUM", "service_stack": ["Package installation", "Package publishing", "npm Registry", "CouchDB"], "categories": ["DATABASE_DEGRADATION", "AUTHENTICATION_FAILURE"], "symptom_logs": "[2025-04-11 14:51:12 UTC] npm SRE (Resolved): This incident was caused due to an internal bug during regular database maintenance, its resolved now.\n[2025-04-11 12:52:59 UTC] npm SRE (Monitoring): We are monitoring results\n[2025-04-11 08:32:45 UTC] npm SRE (Identified): We are continuing to work on a fix to restore older access tokens.\n[2025-04-11 05:37:44 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2025-04-11 02:46:35 UTC] npm SRE (Investigating): We are investigating issues with access tokens, in the meantime user can recreate new tokens to unblock themselves.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident was caused due to an internal bug during regular database maintenance, its resolved now. We are monitoring results We are continuing to work on a fix to restore older access tokens. The issue has been identified and a fix is being implemented. We are investigating issues with access tokens, in the meantime user can recreate new tokens to unblock themselves.", "breaking_config_code": "# Incident architectural state during Issues publishing and installing packages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"Package publishing\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/wk3g29hzj4g2", "metadata": {"raw_id": "bndr0gf8nnsq", "status": "resolved", "resolved_at": "2025-04-11T14:51:12.236Z"}}
{"incident_id": "INC-2025-NPM-j17xz3yd", "company": "npm", "date": "2025-04-05", "title": "Issues publishing and installing packages", "severity": "HIGH", "service_stack": ["Package installation", "Package publishing", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-04-05 15:15:57 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-04-05 13:34:13 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-04-05 12:00:50 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2025-04-05 10:53:51 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issues publishing and installing packages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"Package publishing\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ykq2pwnxgvhp", "metadata": {"raw_id": "j17xz3yd9pd9", "status": "resolved", "resolved_at": "2025-04-05T15:15:57.403Z"}}
{"incident_id": "INC-2025-NPM-hdtkrsqp", "company": "npm", "date": "2025-04-01", "title": "Intermittent issue with viewing and installing packages", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "Package installation", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-04-01 19:40:59 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-04-01 17:37:32 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2025-04-01 17:11:41 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2025-04-01 16:40:26 UTC] npm SRE (Investigating): We are currently investigating reports of intermittent failures when viewing and installing packages scoped to certain keywords.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating reports of intermittent failures when viewing and installing packages scoped to certain keywords.", "breaking_config_code": "# Incident architectural state during Intermittent issue with viewing and installing packages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"Package installation\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/lxzsjgplvs8j", "metadata": {"raw_id": "hdtkrsqp134s", "status": "resolved", "resolved_at": "2025-04-01T19:40:59.032Z"}}
{"incident_id": "INC-2025-NPM-jlqm624k", "company": "npm", "date": "2025-01-08", "title": "npm is experiencing intermittent degraded installs", "severity": "MEDIUM", "service_stack": ["Package installation", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2025-01-09 00:50:20 UTC] npm SRE (Resolved): This incident has been resolved.\n[2025-01-08 23:12:47 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2025-01-08 22:05:06 UTC] npm SRE (Investigating): We are currently investigating this issue", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. The issue has been identified and a fix is being implemented. We are currently investigating this issue", "breaking_config_code": "# Incident architectural state during npm is experiencing intermittent degraded installs\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rf127d7f68xy", "metadata": {"raw_id": "jlqm624klvs2", "status": "resolved", "resolved_at": "2025-01-09T00:50:20.222Z"}}
{"incident_id": "INC-2024-NPM-bxvmmvlq", "company": "npm", "date": "2024-12-17", "title": "Package Install failures due to \"304 Not Modified\" responses in Mumbai, India region", "severity": "HIGH", "service_stack": ["Package installation", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-12-17 16:19:11 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-12-17 15:43:00 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-12-17 14:37:18 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-12-17 12:50:31 UTC] npm SRE (Investigating): We are currently investigating failures to install packages due to TAR_BAD_ARCHIVE or 304 Not Modified responses for clients in Mumbai, India.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating failures to install packages due to TAR_BAD_ARCHIVE or 304 Not Modified responses for clients in Mumbai, India.", "breaking_config_code": "# Incident architectural state during Package Install failures due to \"304 Not Modified\" responses in Mumbai, India region\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6v8d2fkbdgbg", "metadata": {"raw_id": "bxvmmvlqzfds", "status": "resolved", "resolved_at": "2024-12-17T16:19:11.695Z"}}
{"incident_id": "INC-2024-NPM-psj9zh3l", "company": "npm", "date": "2024-11-16", "title": "Intermittent issues with package install", "severity": "MEDIUM", "service_stack": ["Package installation", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-11-16 14:58:05 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-11-16 13:39:18 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-11-16 13:32:44 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-11-16 13:31:40 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Intermittent issues with package install\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/392r757wl17p", "metadata": {"raw_id": "psj9zh3lb9md", "status": "resolved", "resolved_at": "2024-11-16T14:58:05.560Z"}}
{"incident_id": "INC-2024-NPM-s9fstrc9", "company": "npm", "date": "2024-10-10", "title": "Failures to publish packlages", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-10-10 21:40:46 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-10-10 21:01:53 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-10-10 20:25:27 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented.", "breaking_config_code": "# Incident architectural state during Failures to publish packlages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ymg5s4hyfnc9", "metadata": {"raw_id": "s9fstrc9sfgq", "status": "resolved", "resolved_at": "2024-10-10T21:40:46.572Z"}}
{"incident_id": "INC-2024-NPM-zvpm95sg", "company": "npm", "date": "2024-09-24", "title": "Issue with publishing packages", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-09-25 00:37:01 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-09-25 00:12:19 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-09-25 00:12:06 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-09-24 22:49:44 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issue with publishing packages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/xc3tnvvlyn6h", "metadata": {"raw_id": "zvpm95sgl89p", "status": "resolved", "resolved_at": "2024-09-25T00:37:01.298Z"}}
{"incident_id": "INC-2024-NPM-qfmzhxz3", "company": "npm", "date": "2024-08-09", "title": "README files not rendering on npmjs.com website", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-08-09 11:47:03 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-08-09 11:23:28 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-08-09 11:18:09 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during README files not rendering on npmjs.com website\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/m4txrkhfdntk", "metadata": {"raw_id": "qfmzhxz3frwb", "status": "resolved", "resolved_at": "2024-08-09T11:47:03.766Z"}}
{"incident_id": "INC-2024-NPM-dscg27mz", "company": "npm", "date": "2024-06-20", "title": "Intermittent Issues with View Package", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-06-20 21:15:22 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-06-20 20:27:51 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-06-20 20:10:17 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-06-20 19:37:11 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Intermittent Issues with View Package\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/2vyznqszrgw6", "metadata": {"raw_id": "dscg27mzph3d", "status": "resolved", "resolved_at": "2024-06-20T21:15:22.984Z"}}
{"incident_id": "INC-2024-NPM-25b12z1q", "company": "npm", "date": "2024-06-17", "title": "Issue with search and replication feed", "severity": "MEDIUM", "service_stack": ["Package search", "Replication Feed", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-06-17 21:36:35 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-06-17 21:14:53 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-06-17 20:08:31 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-06-17 19:59:51 UTC] npm SRE (Investigating): We are currently investigating an issue related to search and replication feed.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating an issue related to search and replication feed.", "breaking_config_code": "# Incident architectural state during Issue with search and replication feed\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package search\", \"Replication Feed\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package search cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/lgm1kl733q30", "metadata": {"raw_id": "25b12z1q22nq", "status": "resolved", "resolved_at": "2024-06-17T21:36:35.692Z"}}
{"incident_id": "INC-2024-NPM-2v41lbhc", "company": "npm", "date": "2024-06-11", "title": "Failures publishing, deprecating, and installing packages", "severity": "HIGH", "service_stack": ["Package installation", "Package publishing", "npm Registry", "CouchDB"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-06-11 16:44:09 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-06-11 16:02:43 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-06-11 15:28:18 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-06-11 15:09:19 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Failures publishing, deprecating, and installing packages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"Package publishing\", \"npm Registry\", \"CouchDB\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/5shjsh314bfw", "metadata": {"raw_id": "2v41lbhcj771", "status": "resolved", "resolved_at": "2024-06-11T16:44:09.301Z"}}
{"incident_id": "INC-2024-NPM-qj1sgg13", "company": "npm", "date": "2024-06-03", "title": "Intermittent failures installing scoped packages", "severity": "HIGH", "service_stack": ["Package installation", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-06-03 19:38:02 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-06-03 19:08:58 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-06-03 18:21:04 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-06-03 17:55:19 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Intermittent failures installing scoped packages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/vgq59rtw7jlg", "metadata": {"raw_id": "qj1sgg136lbr", "status": "resolved", "resolved_at": "2024-06-03T19:38:02.504Z"}}
{"incident_id": "INC-2024-NPM-jq0pj3dc", "company": "npm", "date": "2024-05-03", "title": "Issue with Private Package Installs", "severity": "MEDIUM", "service_stack": ["Package installation", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-05-03 03:36:08 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-05-03 02:57:50 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-05-03 00:26:25 UTC] npm SRE (Investigating): We are currently investigating an issue with private package installations.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating an issue with private package installations.", "breaking_config_code": "# Incident architectural state during Issue with Private Package Installs\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package installation\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package installation cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/z1r46l81tgzx", "metadata": {"raw_id": "jq0pj3dcq3vm", "status": "resolved", "resolved_at": "2024-05-03T03:36:08.949Z"}}
{"incident_id": "INC-2024-NPM-lbkwcyh9", "company": "npm", "date": "2024-04-09", "title": "Issues publishing packages", "severity": "MEDIUM", "service_stack": ["Package publishing", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-04-10 00:44:34 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-04-09 21:36:23 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-04-09 21:16:41 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-04-09 21:01:49 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Issues publishing packages\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"Package publishing\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Package publishing cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/86clb3x2c54p", "metadata": {"raw_id": "lbkwcyh9xywh", "status": "resolved", "resolved_at": "2024-04-10T00:44:34.418Z"}}
{"incident_id": "INC-2024-NPM-hv0gwqg8", "company": "npm", "date": "2024-01-24", "title": "npm support is down", "severity": "MEDIUM", "service_stack": ["www.npmjs.com website", "npm Registry", "CouchDB", "Fastly CDN"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2024-01-24 19:37:00 UTC] npm SRE (Resolved): This incident has been resolved.\n[2024-01-24 18:34:45 UTC] npm SRE (Monitoring): We are continuing to monitor for any further issues.\n[2024-01-24 18:33:57 UTC] npm SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2024-01-24 18:03:53 UTC] npm SRE (Identified): The issue has been identified and a fix is being implemented.\n[2024-01-24 17:56:53 UTC] npm SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by npm engineering: This incident has been resolved. We are continuing to monitor for any further issues. A fix has been implemented and we are monitoring the results. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during npm support is down\nservice_cluster:\n  provider: \"npm\"\n  impacted_components: [\"www.npmjs.com website\", \"npm Registry\", \"CouchDB\", \"Fastly CDN\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by npm SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on www.npmjs.com website cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/17jcf80p5j9s", "metadata": {"raw_id": "hv0gwqg8w4g2", "status": "resolved", "resolved_at": "2024-01-24T19:37:00.339Z"}}
{"incident_id": "INC-2026-SENTRY-bjysgyqq", "company": "Sentry", "date": "2026-09-18", "title": "Delayed ingestion of errors in EU", "severity": "CRITICAL", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-18 11:57:16 UTC] Sentry SRE (Resolved): We are processing real-time data for all data types again.\n[2026-09-18 11:45:52 UTC] Sentry SRE (Identified): Error ingestion is fully operational. We are currently working on recovering real-time processing of spans.\n[2026-09-18 10:58:36 UTC] Sentry SRE (Identified): We have identified a networking issue with an upstream provider and are working on mitigations.\n[2026-09-18 10:56:54 UTC] Sentry SRE (Monitoring): We have identified a networking issue with an upstream provider and are working on mitigations.\n[2026-09-18 09:54:39 UTC] Sentry SRE (Monitoring): We are processing real-time data again and are working on burning our backlog.\n[2026-09-18 09:53:28 UTC] Sentry SRE (Investigating): We are processing real-time data again and are working on burning our backlog.\n[2026-09-18 09:00:44 UTC] Sentry SRE (Investigating): We have implemented a mitigation and are starting to recover.\n[2026-09-18 08:36:46 UTC] Sentry SRE (Investigating): We are currently investigating an issue that causes new errors to be delayed in the EU region.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: We are processing real-time data for all data types again. Error ingestion is fully operational. We are currently working on recovering real-time processing of spans. We have identified a networking issue with an upstream provider and are working on mitigations. We have identified a networking issue with an upstream provider and are working on mitigations. We are processing real-time data again and are working on burning our backlog. We are proce", "breaking_config_code": "# Incident architectural state during Delayed ingestion of errors in EU\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/518318wxv2f8", "metadata": {"raw_id": "bjysgyqq93gn", "status": "resolved", "resolved_at": "2026-09-18T11:57:16.126Z"}}
{"incident_id": "INC-2026-SENTRY-v0d8qvrg", "company": "Sentry", "date": "2026-09-18", "title": "Delays in spans ingestion", "severity": "HIGH", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-18 10:58:05 UTC] Sentry SRE (Resolved): We have identified a networking issue with an upstream provider and are working on mitigations.\n[2026-09-18 10:56:38 UTC] Sentry SRE (Investigating): We have identified a networking issue with an upstream provider and are working on mitigations.\n[2026-09-18 10:17:01 UTC] Sentry SRE (Investigating): We are currently investigating an issue affecting spans ingestion in the EU region", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: We have identified a networking issue with an upstream provider and are working on mitigations. We have identified a networking issue with an upstream provider and are working on mitigations. We are currently investigating an issue affecting spans ingestion in the EU region", "breaking_config_code": "# Incident architectural state during Delays in spans ingestion\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/7tjcn7m11qh3", "metadata": {"raw_id": "v0d8qvrgsf25", "status": "resolved", "resolved_at": "2026-09-18T10:58:05.057Z"}}
{"incident_id": "INC-2026-SENTRY-ldszczyf", "company": "Sentry", "date": "2026-09-10", "title": "Ingestion is delayed in US", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-10 17:10:11 UTC] Sentry SRE (Resolved): Ingestion is now operating normally.\n[2026-09-10 16:52:29 UTC] Sentry SRE (Investigating): We are continuing to monitor delayed ingestion.\n[2026-09-10 16:13:34 UTC] Sentry SRE (Investigating): We are investigating degraded ingestion in US.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Ingestion is now operating normally. We are continuing to monitor delayed ingestion. We are investigating degraded ingestion in US.", "breaking_config_code": "# Incident architectural state during Ingestion is delayed in US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/gdjjp911yksz", "metadata": {"raw_id": "ldszczyfykgc", "status": "resolved", "resolved_at": "2026-09-10T17:10:11.063Z"}}
{"incident_id": "INC-2026-SENTRY-pkyrdl15", "company": "Sentry", "date": "2026-09-10", "title": "Sentry.io elevated number of 500 errors", "severity": "HIGH", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-10 16:26:18 UTC] Sentry SRE (Resolved): Issue fully resolved\n[2026-09-10 16:07:59 UTC] Sentry SRE (Monitoring): Issue were identified and fixes were applied. We continue to monitor situation\n[2026-09-10 15:25:10 UTC] Sentry SRE (Identified): During migration to new control silo region we started to observe increased number of 500 errors. \nMigration procedure was rolled back.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Issue fully resolved Issue were identified and fixes were applied. We continue to monitor situation During migration to new control silo region we started to observe increased number of 500 errors. \nMigration procedure was rolled back.", "breaking_config_code": "# Incident architectural state during Sentry.io elevated number of 500 errors\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/10yb4b5w2szj", "metadata": {"raw_id": "pkyrdl15szrp", "status": "resolved", "resolved_at": "2026-09-10T16:26:18.230Z"}}
{"incident_id": "INC-2026-SENTRY-zr5tdz4t", "company": "Sentry", "date": "2026-09-01", "title": "Span ingestion is degraded in US", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-01 20:29:43 UTC] Sentry SRE (Resolved): Spans ingestion is now operating normally.\n[2026-09-01 19:31:54 UTC] Sentry SRE (Monitoring): Latency is almost fully recovered.\n[2026-09-01 18:30:02 UTC] Sentry SRE (Monitoring): A fix has been implemented, and latency is coming down.\n[2026-09-01 17:50:29 UTC] Sentry SRE (Investigating): We are continuing to investigate an issue that affects spans ingestion latency\n[2026-09-01 16:41:02 UTC] Sentry SRE (Investigating): We are continuing to investigate an issue that affects spans ingestion latency\n[2026-09-01 15:40:59 UTC] Sentry SRE (Investigating): We are continuing to investigate an issue that affects spans ingestion latency\n[2026-09-01 14:16:13 UTC] Sentry SRE (Investigating): We are experiencing slow ingestion for spans in US", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Spans ingestion is now operating normally. Latency is almost fully recovered. A fix has been implemented, and latency is coming down. We are continuing to investigate an issue that affects spans ingestion latency We are continuing to investigate an issue that affects spans ingestion latency We are continuing to investigate an issue that affects spans ingestion latency We are experiencing slow ingestion for spans in US", "breaking_config_code": "# Incident architectural state during Span ingestion is degraded in US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/nc8v40xh55zt", "metadata": {"raw_id": "zr5tdz4t85p8", "status": "resolved", "resolved_at": "2026-09-01T20:29:43.934Z"}}
{"incident_id": "INC-2026-SENTRY-tx3clz6t", "company": "Sentry", "date": "2026-09-01", "title": "Sentry requests timing out / 504's", "severity": "HIGH", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-01 11:21:24 UTC] Sentry SRE (Resolved): This incident has been resolved.\n[2026-09-01 09:03:51 UTC] Sentry SRE (Monitoring): We're monitoring the implemented fix\n[2026-09-01 08:57:58 UTC] Sentry SRE (Monitoring): We identified the issue and rolled out a configuration change\n[2026-09-01 08:01:21 UTC] Sentry SRE (Investigating): We are currently investigating what's going on and why requests timing out", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: This incident has been resolved. We're monitoring the implemented fix We identified the issue and rolled out a configuration change We are currently investigating what's going on and why requests timing out", "breaking_config_code": "# Incident architectural state during Sentry requests timing out / 504's\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/hks9pdczmhhv", "metadata": {"raw_id": "tx3clz6t8f77", "status": "resolved", "resolved_at": "2026-09-01T11:21:24.711Z"}}
{"incident_id": "INC-2026-SENTRY-9ydqgcwy", "company": "Sentry", "date": "2026-08-31", "title": "Ingestion backlog", "severity": "MEDIUM", "service_stack": ["US Error Ingestion", "US Errors Alerting", "API", "US Transaction Ingestion"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-31 22:43:21 UTC] Sentry SRE (Resolved): This incident has been resolved.\n[2026-08-31 21:26:09 UTC] Sentry SRE (Monitoring): Our systems are recovering from an ingestion backlog, webhooks are currently delayed\n[2026-08-31 21:16:29 UTC] Sentry SRE (Monitoring): Our systems are recovering from an ingestion backlog\n[2026-08-31 21:12:46 UTC] Sentry SRE (Investigating): API is experiencing issues\n[2026-08-31 21:02:13 UTC] Sentry SRE (Monitoring): The fix has been deployed and our ingestion backlogs are recovering\n[2026-08-31 20:52:20 UTC] Sentry SRE (Investigating): We have identified the culprit and are rolling out a fix\n[2026-08-31 20:31:45 UTC] Sentry SRE (Investigating): we are investigating a failure in our infrastructure that is delaying ingestion", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: This incident has been resolved. Our systems are recovering from an ingestion backlog, webhooks are currently delayed Our systems are recovering from an ingestion backlog API is experiencing issues The fix has been deployed and our ingestion backlogs are recovering We have identified the culprit and are rolling out a fix we are investigating a failure in our infrastructure that is delaying ingestion", "breaking_config_code": "# Incident architectural state during Ingestion backlog\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"US Error Ingestion\", \"US Errors Alerting\", \"API\", \"US Transaction Ingestion\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on US Error Ingestion cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/4bkrdrmv44ym", "metadata": {"raw_id": "9ydqgcwy0fj4", "status": "resolved", "resolved_at": "2026-08-31T22:43:21.444Z"}}
{"incident_id": "INC-2026-SENTRY-qyd280cf", "company": "Sentry", "date": "2026-08-27", "title": "sentry.io is not available", "severity": "HIGH", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-08-27 15:41:45 UTC] Sentry SRE (Resolved): Our latency is now back to normal. Incident resolved\n[2026-08-27 13:58:28 UTC] Sentry SRE (Monitoring): Our latency is now back to normal. We'll keep monitoring our systems a few more time before declaring the incident as resolved\n[2026-08-27 13:39:48 UTC] Sentry SRE (Monitoring): We keep monitoring our systems while we recover to our usual latency\n[2026-08-27 12:48:17 UTC] Sentry SRE (Monitoring): We are continuing to monitor while our systems recover after an issue that affected the availability of our product and API\n[2026-08-27 11:44:21 UTC] Sentry SRE (Monitoring): We have identified and mitigated an issue that affected the availability of our product and API, and are now monitoring while our systems recover\n[2026-08-27 11:25:14 UTC] Sentry SRE (Investigating): We are continuing to investigate an issue that affects the availability of our product and API\n[2026-08-27 10:49:28 UTC] Sentry SRE (Investigating): We are continuing to investigate an issue that affects the availability of our product and API\n[2026-08-27 09:56:36 UTC] Sentry SRE (Investigating): We are continuing to investigate an issue that affects the availability of our product and API", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Our latency is now back to normal. Incident resolved Our latency is now back to normal. We'll keep monitoring our systems a few more time before declaring the incident as resolved We keep monitoring our systems while we recover to our usual latency We are continuing to monitor while our systems recover after an issue that affected the availability of our product and API We have identified and mitigated an issue that affected the availability of o", "breaking_config_code": "# Incident architectural state during sentry.io is not available\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/zthsn2d365m0", "metadata": {"raw_id": "qyd280cf2pzx", "status": "resolved", "resolved_at": "2026-08-27T15:41:45.825Z"}}
{"incident_id": "INC-2026-SENTRY-1l6k1160", "company": "Sentry", "date": "2026-08-26", "title": "Issues performance is degraded in the US", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-08-26 20:36:14 UTC] Sentry SRE (Resolved): The issue has been resolved\n[2026-08-26 20:04:04 UTC] Sentry SRE (Monitoring): We have put a fix into place and are monitoring the situation\n[2026-08-26 18:47:29 UTC] Sentry SRE (Monitoring): We have put a fix into place and are monitoring the situation\n[2026-08-26 17:53:29 UTC] Sentry SRE (Identified): We have identified a potential cause of excess traffic and are working on a fix.\n[2026-08-26 16:17:20 UTC] Sentry SRE (Investigating): We are experiencing slower page loads and API responses due to a database issue in us", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The issue has been resolved We have put a fix into place and are monitoring the situation We have put a fix into place and are monitoring the situation We have identified a potential cause of excess traffic and are working on a fix. We are experiencing slower page loads and API responses due to a database issue in us", "breaking_config_code": "# Incident architectural state during Issues performance is degraded in the US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/nbksfm6kzcb9", "metadata": {"raw_id": "1l6k1160fyys", "status": "resolved", "resolved_at": "2026-08-26T20:36:14.014Z"}}
{"incident_id": "INC-2026-SENTRY-v913q9jx", "company": "Sentry", "date": "2026-08-25", "title": "Errors alerting degraded in US region", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-25 12:38:27 UTC] Sentry SRE (Resolved): Error alerting is back to normal.\n[2026-08-25 12:27:34 UTC] Sentry SRE (Identified): We have identified the issue and implemented a fix.\n[2026-08-25 11:09:40 UTC] Sentry SRE (Investigating): We are continuing to investigate the issue\n[2026-08-25 09:38:01 UTC] Sentry SRE (Investigating): We are investigating delays in error alerts in the US region, up to 10 minutes", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Error alerting is back to normal. We have identified the issue and implemented a fix. We are continuing to investigate the issue We are investigating delays in error alerts in the US region, up to 10 minutes", "breaking_config_code": "# Incident architectural state during Errors alerting degraded in US region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/b0s1vw9m6vf8", "metadata": {"raw_id": "v913q9jxwlhr", "status": "resolved", "resolved_at": "2026-08-25T12:38:27.667Z"}}
{"incident_id": "INC-2026-SENTRY-gv6q6ygk", "company": "Sentry", "date": "2026-08-18", "title": "Alert backlogs in US", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-18 22:21:45 UTC] Sentry SRE (Resolved): The problem has been resolved, all backlogs have cleared and everything is operational again.\n[2026-08-18 22:15:07 UTC] Sentry SRE (Monitoring): We have implemented a fix and the systems are recovering. We are monitoring to ensure that backlogs are proessed.\n[2026-08-18 21:56:13 UTC] Sentry SRE (Identified): We have identified the cause and are working to determine a mitigation. This is only affecting US right now.\n[2026-08-18 21:42:54 UTC] Sentry SRE (Investigating): We are currently investigating a delay in evaluating alerts in the US region.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The problem has been resolved, all backlogs have cleared and everything is operational again. We have implemented a fix and the systems are recovering. We are monitoring to ensure that backlogs are proessed. We have identified the cause and are working to determine a mitigation. This is only affecting US right now. We are currently investigating a delay in evaluating alerts in the US region.", "breaking_config_code": "# Incident architectural state during Alert backlogs in US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/mynbbg9gwj4p", "metadata": {"raw_id": "gv6q6ygk757c", "status": "resolved", "resolved_at": "2026-08-18T22:21:45.122Z"}}
{"incident_id": "INC-2026-SENTRY-rgcnzc6q", "company": "Sentry", "date": "2026-08-13", "title": "Span & Transaction ingestion delayed in DE", "severity": "HIGH", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-13 22:27:03 UTC] Sentry SRE (Resolved): All backlogs have been processed.\n[2026-08-13 22:13:48 UTC] Sentry SRE (Monitoring): We continue to make progress on the spans backlog with an estimated completion time of 15 minutes.\n[2026-08-13 21:22:18 UTC] Sentry SRE (Monitoring): We're continuing to make progress on the span ingestion backlog in US.\n[2026-08-13 20:32:19 UTC] Sentry SRE (Monitoring): We've recovered all ingestion latency in DE. In US, errors have processed their backlog and we continue to make progress on spans in US.\n[2026-08-13 19:53:24 UTC] Sentry SRE (Monitoring): The problematic change has been reverted and we're processing backlogs.\n[2026-08-13 19:34:57 UTC] Sentry SRE (Monitoring): The problematic change has been reverted and we're processing backlogs.\n[2026-08-13 18:35:00 UTC] Sentry SRE (Identified): We've identified the source of latency and are reverting that change.\n[2026-08-13 18:07:49 UTC] Sentry SRE (Investigating): We are currently investigating ingestion delays for spans, transactions and alerts in DE and US", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: All backlogs have been processed. We continue to make progress on the spans backlog with an estimated completion time of 15 minutes. We're continuing to make progress on the span ingestion backlog in US. We've recovered all ingestion latency in DE. In US, errors have processed their backlog and we continue to make progress on spans in US. The problematic change has been reverted and we're processing backlogs. The problematic change has been rever", "breaking_config_code": "# Incident architectural state during Span & Transaction ingestion delayed in DE\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/3dh3m2pvx8f2", "metadata": {"raw_id": "rgcnzc6q3cgb", "status": "resolved", "resolved_at": "2026-08-13T22:27:03.735Z"}}
{"incident_id": "INC-2026-SENTRY-8mmq3ykd", "company": "Sentry", "date": "2026-08-12", "title": "Error ingestion delays in US", "severity": "HIGH", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-12 22:52:59 UTC] Sentry SRE (Resolved): Backlogs have been processed\n[2026-08-12 22:43:55 UTC] Sentry SRE (Identified): We've mitigated the source of ingestion latency and are processing the backlog.\n[2026-08-12 21:58:59 UTC] Sentry SRE (Investigating): We are currently investigating error ingestion latency in US.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Backlogs have been processed We've mitigated the source of ingestion latency and are processing the backlog. We are currently investigating error ingestion latency in US.", "breaking_config_code": "# Incident architectural state during Error ingestion delays in US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/qh9kqp474lw2", "metadata": {"raw_id": "8mmq3ykdqwvz", "status": "resolved", "resolved_at": "2026-08-12T22:52:59.753Z"}}
{"incident_id": "INC-2026-SENTRY-1vb2qjjj", "company": "Sentry", "date": "2026-08-12", "title": "Delayed Error ingestion in our US region", "severity": "HIGH", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-12 14:48:25 UTC] Sentry SRE (Resolved): The backlog has been processed\n[2026-08-12 14:21:12 UTC] Sentry SRE (Monitoring): We're processing new events and alerts in realtime, and continue to process the tail of the backlog.\n[2026-08-12 13:28:57 UTC] Sentry SRE (Identified): A fix has been made and the backlog is being processed.\n[2026-08-12 12:36:32 UTC] Sentry SRE (Investigating): We've identified the root cause and are actively working on mitigation.\n[2026-08-12 11:45:45 UTC] Sentry SRE (Investigating): We are actively investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The backlog has been processed We're processing new events and alerts in realtime, and continue to process the tail of the backlog. A fix has been made and the backlog is being processed. We've identified the root cause and are actively working on mitigation. We are actively investigating this issue.", "breaking_config_code": "# Incident architectural state during Delayed Error ingestion in our US region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/tcdgnyx93p0q", "metadata": {"raw_id": "1vb2qjjjm88k", "status": "resolved", "resolved_at": "2026-08-12T14:48:25.691Z"}}
{"incident_id": "INC-2026-SENTRY-mc7gkgm6", "company": "Sentry", "date": "2026-08-12", "title": "Sentry API timeouts (US)", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-12 14:24:49 UTC] Sentry SRE (Resolved): API performance has returned to expected levels.\n[2026-08-12 13:14:13 UTC] Sentry SRE (Monitoring): API performance has returned to expected levels. We are continuing to monitor.\n[2026-08-12 12:58:45 UTC] Sentry SRE (Investigating): We are currently investigating reports of API timeouts for the Sentry API in our US region.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: API performance has returned to expected levels. API performance has returned to expected levels. We are continuing to monitor. We are currently investigating reports of API timeouts for the Sentry API in our US region.", "breaking_config_code": "# Incident architectural state during Sentry API timeouts (US)\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/g39d36y8ptjn", "metadata": {"raw_id": "mc7gkgm6sprn", "status": "resolved", "resolved_at": "2026-08-12T14:24:49.273Z"}}
{"incident_id": "INC-2026-SENTRY-mw9jgw0v", "company": "Sentry", "date": "2026-08-07", "title": "Spans, crons, logs ingestion delayed in US region", "severity": "CRITICAL", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-07 17:08:22 UTC] Sentry SRE (Resolved): The ingestion delay is resolved\n[2026-08-07 16:48:50 UTC] Sentry SRE (Monitoring): Ingestion latency for spans, crons, and logs is back to normal levels.\n[2026-08-07 16:30:50 UTC] Sentry SRE (Identified): We've put a fix in place and are monitoring. We anticipate catching up to ingestion within 1 hour\n[2026-08-07 16:21:05 UTC] Sentry SRE (Investigating): We are currently investigating the issue", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The ingestion delay is resolved Ingestion latency for spans, crons, and logs is back to normal levels. We've put a fix in place and are monitoring. We anticipate catching up to ingestion within 1 hour We are currently investigating the issue", "breaking_config_code": "# Incident architectural state during Spans, crons, logs ingestion delayed in US region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/hm0ff1mzq3vl", "metadata": {"raw_id": "mw9jgw0v6z65", "status": "resolved", "resolved_at": "2026-08-07T17:08:22.375Z"}}
{"incident_id": "INC-2026-SENTRY-9wr3wq71", "company": "Sentry", "date": "2026-08-06", "title": "Delayed Error ingestion in our US region", "severity": "HIGH", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-06 11:21:06 UTC] Sentry SRE (Resolved): We've processed all backlogged events and have fully recovered.\n[2026-08-06 10:50:18 UTC] Sentry SRE (Monitoring): We're processing new events in real time, and are working through a backlog of events now.\n[2026-08-06 10:25:18 UTC] Sentry SRE (Investigating): We've identified the issue causing delays in ingestion and have applied a fix. We'll update again when we return to real time processing.\n[2026-08-06 09:55:48 UTC] Sentry SRE (Investigating): We are still actively investigating this issue.\n[2026-08-06 08:59:12 UTC] Sentry SRE (Investigating): We are actively investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: We've processed all backlogged events and have fully recovered. We're processing new events in real time, and are working through a backlog of events now. We've identified the issue causing delays in ingestion and have applied a fix. We'll update again when we return to real time processing. We are still actively investigating this issue. We are actively investigating this issue.", "breaking_config_code": "# Incident architectural state during Delayed Error ingestion in our US region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/g528fth7fzvw", "metadata": {"raw_id": "9wr3wq715fny", "status": "resolved", "resolved_at": "2026-08-06T11:21:06.139Z"}}
{"incident_id": "INC-2026-SENTRY-jbrm2d4g", "company": "Sentry", "date": "2026-07-27", "title": "Error and profile ingestion issues in US", "severity": "CRITICAL", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-27 18:27:00 UTC] Sentry SRE (Resolved): The backlog has been cleared and ingestion is back to normal.\n[2026-07-27 18:07:29 UTC] Sentry SRE (Monitoring): We have resolved the incident and are monitoring our ingestion backlog.\n[2026-07-27 16:56:22 UTC] Sentry SRE (Identified): We have identified the issue and error and profile ingestion is back up in US. Expect delays in ingestion and alerting for errors and profiles.\n[2026-07-27 16:23:47 UTC] Sentry SRE (Investigating): We are experiencing issues with error and profile ingestion in our US region and are investigating the issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The backlog has been cleared and ingestion is back to normal. We have resolved the incident and are monitoring our ingestion backlog. We have identified the issue and error and profile ingestion is back up in US. Expect delays in ingestion and alerting for errors and profiles. We are experiencing issues with error and profile ingestion in our US region and are investigating the issue.", "breaking_config_code": "# Incident architectural state during Error and profile ingestion issues in US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0cy4vyqy4yhr", "metadata": {"raw_id": "jbrm2d4g4ghk", "status": "resolved", "resolved_at": "2026-07-27T18:27:00.689Z"}}
{"incident_id": "INC-2026-SENTRY-4xg44g1c", "company": "Sentry", "date": "2026-07-21", "title": "Delayed ingestion on us region", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-21 14:14:44 UTC] Sentry SRE (Resolved): We've burned through our spans backlog. Latency across span consumers are normal.\n[2026-07-21 13:55:01 UTC] Sentry SRE (Monitoring): We're still burning through our spans backlog\n[2026-07-21 13:04:00 UTC] Sentry SRE (Monitoring): We've found and fixed the root cause and are burning through our spans backlog. Ingestion should be back to normal in around an hour.\n[2026-07-21 12:20:03 UTC] Sentry SRE (Investigating): We are still actively investigating this issue\n[2026-07-21 11:26:12 UTC] Sentry SRE (Investigating): We are still actively investigating this issue\n[2026-07-21 10:30:26 UTC] Sentry SRE (Investigating): We are actively investigating this issue", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: We've burned through our spans backlog. Latency across span consumers are normal. We're still burning through our spans backlog We've found and fixed the root cause and are burning through our spans backlog. Ingestion should be back to normal in around an hour. We are still actively investigating this issue We are still actively investigating this issue We are actively investigating this issue", "breaking_config_code": "# Incident architectural state during Delayed ingestion on us region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/sn99hk0v2nct", "metadata": {"raw_id": "4xg44g1ckg4z", "status": "resolved", "resolved_at": "2026-07-21T14:14:44.973Z"}}
{"incident_id": "INC-2026-SENTRY-lnsbtfnj", "company": "Sentry", "date": "2026-07-20", "title": "EU Region Error, Attachment, and Feedback latency", "severity": "CRITICAL", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-20 16:57:37 UTC] Sentry SRE (Resolved): We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types.\n[2026-07-20 16:09:46 UTC] Sentry SRE (Monitoring): We are still burning the backlog of EU region error events received during the incident. We are around halfway through the backlog.\n[2026-07-20 14:50:36 UTC] Sentry SRE (Monitoring): The backlog on attachments in our EU region is fully burned, and latency is back to normal. While new error events are being processed with normal latency, we have a backlog of old error events that we are now burning through.\n[2026-07-20 14:30:18 UTC] Sentry SRE (Monitoring): We have implemented a fix for our attachment ingestion issue in our EU region, and are monitoring while the backlog burns. We will update here when latency is back to normal.\n[2026-07-20 13:47:35 UTC] Sentry SRE (Identified): We have implemented a fix for errors and feedback ingestion in our EU region, and latency for those pipelines has returned to normal. We are still working on fixing our attachments ingestion pipeline in EU.\n[2026-07-20 13:19:23 UTC] Sentry SRE (Identified): We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.\n[2026-07-20 12:24:52 UTC] Sentry SRE (Identified): We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.\n[2026-07-20 12:10:57 UTC] Sentry SRE (Identified): We have identified the issue causing errors, attachments, and feedback events to have high ingest latency in our EU region and are continuing to work on a fix.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types. We are still burning the backlog of EU region error events received during the incident. We are around halfway through the backlog. The backlog on attachments in our EU region is fully burned, and latency is back to normal. While new error events are being processed with normal latency, we have a backlog of old error events ", "breaking_config_code": "# Incident architectural state during EU Region Error, Attachment, and Feedback latency\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0k3pvpywznz6", "metadata": {"raw_id": "lnsbtfnj7wqz", "status": "resolved", "resolved_at": "2026-07-20T16:57:37.519Z"}}
{"incident_id": "INC-2026-SENTRY-hsxmtdc6", "company": "Sentry", "date": "2026-07-16", "title": "Github Integration Webhook processing delay", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-17 06:57:09 UTC] Sentry SRE (Resolved): The webhook backlog is now resolved.\n[2026-07-17 05:49:06 UTC] Sentry SRE (Identified): The webhook backlog is processing.\n[2026-07-17 04:50:39 UTC] Sentry SRE (Identified): The webhook backlog is processing.\n[2026-07-17 03:49:41 UTC] Sentry SRE (Identified): The webhook backlog is processing. Estimated recovery is now 2-2.5 hours.\n[2026-07-17 02:44:06 UTC] Sentry SRE (Identified): The webhook backlog is processing.\n[2026-07-17 01:28:06 UTC] Sentry SRE (Identified): The webhook backlog is processing.\n[2026-07-17 00:44:52 UTC] Sentry SRE (Identified): The webhook backlog is being processed, ETA ~3 hours until fully caught up.\n\nSeer code reviews will run and linked Github issues and PRs will update incrementally.\n[2026-07-16 21:06:36 UTC] Sentry SRE (Identified): The issue is mitigated and the webhook backlog is being processed. Seer code reviews will run and linked Github issues and PRs will update incrementally.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The webhook backlog is now resolved. The webhook backlog is processing. The webhook backlog is processing. The webhook backlog is processing. Estimated recovery is now 2-2.5 hours. The webhook backlog is processing. The webhook backlog is processing. The webhook backlog is being processed, ETA ~3 hours until fully caught up.\n\nSeer code reviews will run and linked Github issues and PRs will update incrementally. The issue is mitigated and the webh", "breaking_config_code": "# Incident architectural state during Github Integration Webhook processing delay\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ymn08ybcfn05", "metadata": {"raw_id": "hsxmtdc6m5dv", "status": "resolved", "resolved_at": "2026-07-17T06:57:09.689Z"}}
{"incident_id": "INC-2026-SENTRY-2nb32dn3", "company": "Sentry", "date": "2026-07-14", "title": "Error ingestion degraded in DE region", "severity": "CRITICAL", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-14 19:32:24 UTC] Sentry SRE (Resolved): Feedback ingestion is back to realtime and the backlog has been processed.\n[2026-07-14 18:16:06 UTC] Sentry SRE (Monitoring): We are continuing to monitor ingestion, and a fix is being deployed to unblock feedback ingestion.\n[2026-07-14 17:40:27 UTC] Sentry SRE (Monitoring): We are processing errors in realtime, and error backlogs have been processed. We're continuing to monitor the situation before restoring feedback ingestion.\n[2026-07-14 17:02:09 UTC] Sentry SRE (Identified): We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.\n\nWe are working to start allowing user feedback in DE.\n[2026-07-14 16:49:47 UTC] Sentry SRE (Identified): We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.\n[2026-07-14 16:42:36 UTC] Sentry SRE (Identified): We have identified the problem and are working on recovery.\n[2026-07-14 15:42:54 UTC] Sentry SRE (Investigating): We continue to investigate the issue.\n[2026-07-14 14:44:35 UTC] Sentry SRE (Investigating): We are currently investigating the issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Feedback ingestion is back to realtime and the backlog has been processed. We are continuing to monitor ingestion, and a fix is being deployed to unblock feedback ingestion. We are processing errors in realtime, and error backlogs have been processed. We're continuing to monitor the situation before restoring feedback ingestion. We are still working on recovery. New errors should be processed in real time, and we are working on recovering histori", "breaking_config_code": "# Incident architectural state during Error ingestion degraded in DE region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/y9mjtr1fnjg4", "metadata": {"raw_id": "2nb32dn3mclz", "status": "resolved", "resolved_at": "2026-07-14T19:32:24.845Z"}}
{"incident_id": "INC-2026-SENTRY-m25vz3v3", "company": "Sentry", "date": "2026-07-13", "title": "Ingestion delays in US", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-13 14:25:13 UTC] Sentry SRE (Resolved): Service has been restored.\n[2026-07-13 12:41:45 UTC] Sentry SRE (Monitoring): Service has been restored and we are actively monitoring the situation\n[2026-07-13 12:24:13 UTC] Sentry SRE (Identified): We identified the issue and restoring service.\n[2026-07-13 11:51:46 UTC] Sentry SRE (Investigating): We are investigating ingestion delays.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Service has been restored. Service has been restored and we are actively monitoring the situation We identified the issue and restoring service. We are investigating ingestion delays.", "breaking_config_code": "# Incident architectural state during Ingestion delays in US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/djql0vrrkrg3", "metadata": {"raw_id": "m25vz3v3xmcy", "status": "resolved", "resolved_at": "2026-07-13T14:25:13.039Z"}}
{"incident_id": "INC-2026-SENTRY-7cn41psn", "company": "Sentry", "date": "2026-07-13", "title": "Ingestion delayed for spans, logs, crons in US region", "severity": "CRITICAL", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-13 02:56:40 UTC] Sentry SRE (Resolved): Ingestion has caught up and alerts have been restored.\n[2026-07-13 02:01:56 UTC] Sentry SRE (Monitoring): We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately.\n[2026-07-13 01:46:43 UTC] Sentry SRE (Identified): We have identified the problem and are working to restore ingestion\n[2026-07-13 00:58:14 UTC] Sentry SRE (Investigating): We are currently investigating the issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Ingestion has caught up and alerts have been restored. We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately. We have identified the problem and are working to restore ingestion We are currently investigating the issue.", "breaking_config_code": "# Incident architectural state during Ingestion delayed for spans, logs, crons in US region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/bmcxxpdgrvfj", "metadata": {"raw_id": "7cn41psn4znc", "status": "resolved", "resolved_at": "2026-07-13T02:56:40.922Z"}}
{"incident_id": "INC-2026-SENTRY-x19gt7qc", "company": "Sentry", "date": "2026-07-10", "title": "Error ingestion degraded in US region", "severity": "CRITICAL", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-07-11 03:34:49 UTC] Sentry SRE (Resolved): We have processed the backlog.\n[2026-07-11 03:28:41 UTC] Sentry SRE (Monitoring): We have processed the majority of our backlog. We are now recovering the tail of the backlog.\n[2026-07-11 02:37:41 UTC] Sentry SRE (Identified): We have processed the majority of our backlog. We are now recovering an additional 25M error events ranging from 22:20 to 23:20 UTC, which should complete in the next 2 hours\n[2026-07-11 01:46:49 UTC] Sentry SRE (Identified): We expect recovery of historical data to be complete within the next 2 hours.\n[2026-07-11 00:56:20 UTC] Sentry SRE (Identified): We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.\n[2026-07-11 00:04:36 UTC] Sentry SRE (Identified): We have identified the problem and are working on recovery.\n\nNew errors are being processed in real time and we are in the process of consuming backlogged errors.\n[2026-07-10 23:02:33 UTC] Sentry SRE (Identified): We have identified the problem and are working on a fix, ingested errors are delayed and will be processed once the fix is in place.\n[2026-07-10 22:43:49 UTC] Sentry SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: We have processed the backlog. We have processed the majority of our backlog. We are now recovering the tail of the backlog. We have processed the majority of our backlog. We are now recovering an additional 25M error events ranging from 22:20 to 23:20 UTC, which should complete in the next 2 hours We expect recovery of historical data to be complete within the next 2 hours. We are still working on recovery. New errors should be processed in real", "breaking_config_code": "# Incident architectural state during Error ingestion degraded in US region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/bw7pn5bh3bh2", "metadata": {"raw_id": "x19gt7qcgcwb", "status": "resolved", "resolved_at": "2026-07-11T03:34:49.853Z"}}
{"incident_id": "INC-2026-SENTRY-rxjtcg6m", "company": "Sentry", "date": "2026-07-07", "title": "Incoherent number of processed logs", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-07 14:36:02 UTC] Sentry SRE (Resolved): Between July 6th 20:25 UTC and July 7th 12:25 UTC, a wrong configuration change was deployed causing over-sampling of logs, spans and metrics.\nThe configuration change is now reverted and the issue is fixed.\n[2026-07-07 08:49:19 UTC] Sentry SRE (Investigating): We are currently investigating reports of inconsistent reported number of processed logs in Sentry for the last day", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Between July 6th 20:25 UTC and July 7th 12:25 UTC, a wrong configuration change was deployed causing over-sampling of logs, spans and metrics.\nThe configuration change is now reverted and the issue is fixed. We are currently investigating reports of inconsistent reported number of processed logs in Sentry for the last day", "breaking_config_code": "# Incident architectural state during Incoherent number of processed logs\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/yf7318fjnmj8", "metadata": {"raw_id": "rxjtcg6mnvdd", "status": "resolved", "resolved_at": "2026-07-07T14:36:02.839Z"}}
{"incident_id": "INC-2026-SENTRY-7tfjf5k3", "company": "Sentry", "date": "2026-07-06", "title": "DE items ingestion delayed", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-07-07 00:55:17 UTC] Sentry SRE (Resolved): The backlgo has been consumed and ingestion and alerting has returned to normal operation\n[2026-07-06 23:55:24 UTC] Sentry SRE (Monitoring): We're continuing to burn down the EU spans, logs, and metrics ingestion backlog.\n[2026-07-06 23:00:57 UTC] Sentry SRE (Monitoring): We are now processing the backlog in EU. Expect delays in ingestion and alerting for spans, logs, and metrics on the order of hours. We will keep this page updated as we make progress.\n[2026-07-06 21:56:24 UTC] Sentry SRE (Monitoring): API and dashboards for traces, logs, spans should be restored.\n\nIngestion is still behind but is expected to catch up in the next few hours", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The backlgo has been consumed and ingestion and alerting has returned to normal operation We're continuing to burn down the EU spans, logs, and metrics ingestion backlog. We are now processing the backlog in EU. Expect delays in ingestion and alerting for spans, logs, and metrics on the order of hours. We will keep this page updated as we make progress. API and dashboards for traces, logs, spans should be restored.\n\nIngestion is still behind but ", "breaking_config_code": "# Incident architectural state during DE items ingestion delayed\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0jxlf03w6pwh", "metadata": {"raw_id": "7tfjf5k3m0g3", "status": "resolved", "resolved_at": "2026-07-07T00:55:17.128Z"}}
{"incident_id": "INC-2026-SENTRY-p4n5p1x5", "company": "Sentry", "date": "2026-07-06", "title": "Spans, logs and metrics ingestion stopped", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-07-06 22:18:23 UTC] Sentry SRE (Resolved): US ingestion is back to normal. \n\nEU ingestion is still delayed, but we are now recovering. We have created a new Statuspage incident for tracking EU, follow that for further updates: https://status.sentry.io/incidents/7tfjf5k3m0g3\n[2026-07-06 21:28:47 UTC] Sentry SRE (Monitoring): We're still burning the last of our backlog in US and expect to be back to normal the next hour.\n\nWe're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident.\n[2026-07-06 20:29:15 UTC] Sentry SRE (Monitoring): We're continuing burning our backlog in US and expect to be have it fully consumed within the next hour.\n\nWe're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this incident.\n[2026-07-06 19:26:51 UTC] Sentry SRE (Monitoring): We're continuing burning our backlog in US and expect to be have it fully consumed in about 1 hour.\n\nWe're continuing to investigate the delayed ingestion in our EU region.\n[2026-07-06 18:30:33 UTC] Sentry SRE (Monitoring): We've taken steps to mitigate the issue in the US and we're burning our backlog and expect to be have it fully consumed in about 4 hours.\nWe're continuing to investigate the delayed ingestion in our EU region.\n[2026-07-06 17:14:21 UTC] Sentry SRE (Investigating): We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.\n[2026-07-06 16:18:10 UTC] Sentry SRE (Investigating): We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.\n[2026-07-06 15:22:07 UTC] Sentry SRE (Investigating): We're continuing to investigate delayed ingestion of spans, logs, and metrics in both our US and EU regions.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: US ingestion is back to normal. \n\nEU ingestion is still delayed, but we are now recovering. We have created a new Statuspage incident for tracking EU, follow that for further updates: https://status.sentry.io/incidents/7tfjf5k3m0g3 We're still burning the last of our backlog in US and expect to be back to normal the next hour.\n\nWe're continuing to investigate the delayed ingestion in our EU region. EU API and dashboards are also affected by this ", "breaking_config_code": "# Incident architectural state during Spans, logs and metrics ingestion stopped\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/npghss2gxrrr", "metadata": {"raw_id": "p4n5p1x5klvq", "status": "resolved", "resolved_at": "2026-07-06T22:18:23.890Z"}}
{"incident_id": "INC-2026-SENTRY-k6hr3xpv", "company": "Sentry", "date": "2026-07-02", "title": "Traces, spans, logs inaccesible for query or ingestion in de and us", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION"], "symptom_logs": "[2026-07-02 03:56:46 UTC] Sentry SRE (Resolved): All operations are back to normal, as of ~7:30PM PT\n[2026-07-02 00:46:10 UTC] Sentry SRE (Monitoring): The migration has been reversed in EU and US. Application functionality is restored but there is a 45 minute delay in ingestion in the US and no delay in EU\n[2026-07-02 00:34:03 UTC] Sentry SRE (Identified): We have identified a migration as the cause of the issue. We have reverted the migration in EU and are working on doing so in the US\n[2026-07-02 00:17:27 UTC] Sentry SRE (Investigating): We are currently investigating the issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: All operations are back to normal, as of ~7:30PM PT The migration has been reversed in EU and US. Application functionality is restored but there is a 45 minute delay in ingestion in the US and no delay in EU We have identified a migration as the cause of the issue. We have reverted the migration in EU and are working on doing so in the US We are currently investigating the issue.", "breaking_config_code": "# Incident architectural state during Traces, spans, logs inaccesible for query or ingestion in de and us\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/nhq41lnhsnz6", "metadata": {"raw_id": "k6hr3xpvzv40", "status": "resolved", "resolved_at": "2026-07-02T03:56:46.414Z"}}
{"incident_id": "INC-2026-SENTRY-4bnv32fj", "company": "Sentry", "date": "2026-06-30", "title": "Ingestion and query issues for logs, spans, traces in US", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-07-01 10:00:10 UTC] Sentry SRE (Resolved): Data is now processed live and the system are fully operational.\n[2026-07-01 06:14:15 UTC] Sentry SRE (Monitoring): We continue to monitor the fix. Ingestion is around 45 minutes behind and improving. APIs and dashboards are functioning normally (outside of data waiting to be ingested).\n[2026-07-01 05:22:14 UTC] Sentry SRE (Monitoring): We continue to monitor the situation\n[2026-07-01 04:26:35 UTC] Sentry SRE (Monitoring): We continue to monitor the situation\n[2026-07-01 03:30:33 UTC] Sentry SRE (Monitoring): We are currently burning down the ingestion backlog, and estimate that it will be complete by 2AM PT 2026-07-01.\n[2026-07-01 02:25:48 UTC] Sentry SRE (Investigating): We are attempting additional mitigations to restore ingestion for logs, spans, and traces in the US\n[2026-07-01 01:29:27 UTC] Sentry SRE (Investigating): Our ingestion fix was not successful. We are continuing to investigate possible solutions\n[2026-07-01 00:27:30 UTC] Sentry SRE (Investigating): Our database is stabilized. We are attempting a fix to increase the ingestion rate.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Data is now processed live and the system are fully operational. We continue to monitor the fix. Ingestion is around 45 minutes behind and improving. APIs and dashboards are functioning normally (outside of data waiting to be ingested). We continue to monitor the situation We continue to monitor the situation We are currently burning down the ingestion backlog, and estimate that it will be complete by 2AM PT 2026-07-01. We are attempting addition", "breaking_config_code": "# Incident architectural state during Ingestion and query issues for logs, spans, traces in US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/gnyhyysv5gvl", "metadata": {"raw_id": "4bnv32fjbj4q", "status": "resolved", "resolved_at": "2026-07-01T10:00:10.829Z"}}
{"incident_id": "INC-2026-SENTRY-9yvnf1h3", "company": "Sentry", "date": "2026-06-24", "title": "Delayed Span ingestion, Replay ingestion, and Issue creation in our US region", "severity": "MEDIUM", "service_stack": ["US Replay Ingestion", "US Span Ingestion", "Sentry Relay", "Kafka"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-06-24 20:48:03 UTC] Sentry SRE (Resolved): The issue in our US region has been resolved, and ingestion latency is back to normal.\n[2026-06-24 19:53:17 UTC] Sentry SRE (Monitoring): We have implemented a fix for the problem and are monitoring the situation. We are burning our US region ingestion backlog for replays, spans, and performance issues and will update here as the situation progresses.\n[2026-06-24 18:52:00 UTC] Sentry SRE (Identified): We have identified an issue in our US region causing delayed ingestion of spans and replays, as well as delayed creation of some issue types.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The issue in our US region has been resolved, and ingestion latency is back to normal. We have implemented a fix for the problem and are monitoring the situation. We are burning our US region ingestion backlog for replays, spans, and performance issues and will update here as the situation progresses. We have identified an issue in our US region causing delayed ingestion of spans and replays, as well as delayed creation of some issue types.", "breaking_config_code": "# Incident architectural state during Delayed Span ingestion, Replay ingestion, and Issue creation in our US region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"US Replay Ingestion\", \"US Span Ingestion\", \"Sentry Relay\", \"Kafka\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on US Replay Ingestion cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/p962182mq6km", "metadata": {"raw_id": "9yvnf1h3v721", "status": "resolved", "resolved_at": "2026-06-24T20:48:03.850Z"}}
{"incident_id": "INC-2026-SENTRY-hrtwjyjc", "company": "Sentry", "date": "2026-06-12", "title": "Missing SDK Client Reports and Rate Limiting Outcomes", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-12 11:30:03 UTC] Sentry SRE (Resolved): From approximately 10:55 UTC to 11:10 UTC we experienced a loss of outcomes which power the \"Stats\" in the organization settings.\n\nThe data loss is purely informational without impact on billing or ingested data.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: From approximately 10:55 UTC to 11:10 UTC we experienced a loss of outcomes which power the \"Stats\" in the organization settings.\n\nThe data loss is purely informational without impact on billing or ingested data.", "breaking_config_code": "# Incident architectural state during Missing SDK Client Reports and Rate Limiting Outcomes\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/xb0nhwg75j6f", "metadata": {"raw_id": "hrtwjyjc8jq9", "status": "resolved", "resolved_at": "2026-06-12T11:30:03.008Z"}}
{"incident_id": "INC-2026-SENTRY-ccv3pcf0", "company": "Sentry", "date": "2026-06-11", "title": "Notification delivery", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-11 14:48:19 UTC] Sentry SRE (Resolved): This issue has been resolved.\n[2026-06-11 14:18:30 UTC] Sentry SRE (Monitoring): The issue involving some alerts not firing has been mitigated. We will continue to monitor the situation to ensure it does not reoccur.\n[2026-06-11 13:23:48 UTC] Sentry SRE (Monitoring): We have identified an issue with one of our cloud providers that might have caused some alert notifications to not fire starting at around 4:00 AM GMT+2.\n\nSince around 1:30 PM GMT+2, alert notifications are now fully operational in the US region, while delivery is still partially degraded in the EU region.\n[2026-06-11 13:13:01 UTC] Sentry SRE (Monitoring): Notifications delivery is now close to fully functional in US and DE.\n\nWe have identified the root cause as caused by one of our cloud providers, and are closely monitoring the situation.\n[2026-06-11 11:51:09 UTC] Sentry SRE (Investigating): We are continuing to investigate the degraded notifications.\n[2026-06-11 10:53:24 UTC] Sentry SRE (Investigating): We are continuing to investigate the degraded notifications.\n[2026-06-11 09:50:38 UTC] Sentry SRE (Investigating): We're currently investigating degraded notification delivery.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: This issue has been resolved. The issue involving some alerts not firing has been mitigated. We will continue to monitor the situation to ensure it does not reoccur. We have identified an issue with one of our cloud providers that might have caused some alert notifications to not fire starting at around 4:00 AM GMT+2.\n\nSince around 1:30 PM GMT+2, alert notifications are now fully operational in the US region, while delivery is still partially deg", "breaking_config_code": "# Incident architectural state during Notification delivery\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/wr04xy9pxx4w", "metadata": {"raw_id": "ccv3pcf00mbt", "status": "resolved", "resolved_at": "2026-06-11T14:48:19.221Z"}}
{"incident_id": "INC-2026-SENTRY-224ybqqk", "company": "Sentry", "date": "2026-06-10", "title": "Users unable to login to sentry.io", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["AUTHENTICATION_FAILURE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-10 10:28:46 UTC] Sentry SRE (Resolved): Our auth systems are back operational\n[2026-06-10 10:17:26 UTC] Sentry SRE (Monitoring): We rolled back a configuration change we identified as the root cause of the issue. We'll keep monitoring our systems\n[2026-06-10 10:15:13 UTC] Sentry SRE (Monitoring): We deployed a fix and are monitoring the situation.\n[2026-06-10 10:05:57 UTC] Sentry SRE (Investigating): We are currently investigating the issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Our auth systems are back operational We rolled back a configuration change we identified as the root cause of the issue. We'll keep monitoring our systems We deployed a fix and are monitoring the situation. We are currently investigating the issue.", "breaking_config_code": "# Incident architectural state during Users unable to login to sentry.io\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/c0zxps5b0p7l", "metadata": {"raw_id": "224ybqqkrvfd", "status": "resolved", "resolved_at": "2026-06-10T10:28:46.798Z"}}
{"incident_id": "INC-2026-SENTRY-jn4d88vl", "company": "Sentry", "date": "2026-06-02", "title": "Elevated errors (EU)", "severity": "MEDIUM", "service_stack": ["API", "Sentry Relay", "Kafka", "ClickHouse"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-06-02 07:45:03 UTC] Sentry SRE (Resolved): Between 06:00-07:00 UTC, we saw increased numbers of API errors in the EU region. The largest impact was between 06:46-07:00. We've implemented a fix and we're no longer seeing elevated errors.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Between 06:00-07:00 UTC, we saw increased numbers of API errors in the EU region. The largest impact was between 06:46-07:00. We've implemented a fix and we're no longer seeing elevated errors.", "breaking_config_code": "# Incident architectural state during Elevated errors (EU)\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"API\", \"Sentry Relay\", \"Kafka\", \"ClickHouse\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/lh9b0dcrf0w5", "metadata": {"raw_id": "jn4d88vlnnfc", "status": "resolved", "resolved_at": "2026-06-02T07:45:03.887Z"}}
{"incident_id": "INC-2026-SENTRY-8220ms0c", "company": "Sentry", "date": "2026-05-28", "title": "Codereview, Autofix, and Ask Seer outage", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-05-28 14:28:12 UTC] Sentry SRE (Resolved): The issue has been resolved\n[2026-05-28 14:20:53 UTC] Sentry SRE (Monitoring): The fix has been deployed and we are monitoring the situation\n[2026-05-28 13:55:54 UTC] Sentry SRE (Identified): We have identified the cause of the issue and are deploying a fix\n[2026-05-28 13:40:02 UTC] Sentry SRE (Investigating): We are currently investigating the issue", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The issue has been resolved The fix has been deployed and we are monitoring the situation We have identified the cause of the issue and are deploying a fix We are currently investigating the issue", "breaking_config_code": "# Incident architectural state during Codereview, Autofix, and Ask Seer outage\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/3n98gq3n9lrl", "metadata": {"raw_id": "8220ms0cqx66", "status": "resolved", "resolved_at": "2026-05-28T14:28:12.308Z"}}
{"incident_id": "INC-2026-SENTRY-k829yyv0", "company": "Sentry", "date": "2026-05-26", "title": "sentry.io DE Region Outage", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-05-26 08:28:49 UTC] Sentry SRE (Resolved): Access to sentry.io is now fully operational\n[2026-05-26 08:19:55 UTC] Sentry SRE (Monitoring): We have implemented a fix and are monitoring.\n[2026-05-26 08:11:40 UTC] Sentry SRE (Investigating): We are currently investigating an issue causing 500 errors and preventing access to Sentry.io organizations in the DE region. The US region remains fully operational.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Access to sentry.io is now fully operational We have implemented a fix and are monitoring. We are currently investigating an issue causing 500 errors and preventing access to Sentry.io organizations in the DE region. The US region remains fully operational.", "breaking_config_code": "# Incident architectural state during sentry.io DE Region Outage\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/xjrsq9ywmm9q", "metadata": {"raw_id": "k829yyv0pf1j", "status": "resolved", "resolved_at": "2026-05-26T08:28:49.555Z"}}
{"incident_id": "INC-2026-SENTRY-9p5tgzq1", "company": "Sentry", "date": "2026-05-22", "title": "Higher than expected latency on sentry.io", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-05-22 08:23:45 UTC] Sentry SRE (Resolved): Latency for sentry.io has returned to normal.\n[2026-05-22 08:08:51 UTC] Sentry SRE (Monitoring): We have implemented a fix and are monitoring.\n[2026-05-22 07:42:51 UTC] Sentry SRE (Investigating): We are currently investigating slow page loads on sentry.io.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Latency for sentry.io has returned to normal. We have implemented a fix and are monitoring. We are currently investigating slow page loads on sentry.io.", "breaking_config_code": "# Incident architectural state during Higher than expected latency on sentry.io\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/f72fkmtrzn2m", "metadata": {"raw_id": "9p5tgzq13kj9", "status": "resolved", "resolved_at": "2026-05-22T08:23:45.045Z"}}
{"incident_id": "INC-2026-SENTRY-8jr1xp5p", "company": "Sentry", "date": "2026-05-19", "title": "Error Ingestion Delayed in US Region", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-05-19 18:48:53 UTC] Sentry SRE (Resolved): Ingestion for symbolicated issues is back to normal.\n[2026-05-19 17:41:54 UTC] Sentry SRE (Investigating): We are implementing a fix and monitoring the situation. Non-symbolicated issues are not experiencing delays.\n[2026-05-19 15:58:49 UTC] Sentry SRE (Investigating): We are experiencing ingestion delays for errors in the US region.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Ingestion for symbolicated issues is back to normal. We are implementing a fix and monitoring the situation. Non-symbolicated issues are not experiencing delays. We are experiencing ingestion delays for errors in the US region.", "breaking_config_code": "# Incident architectural state during Error Ingestion Delayed in US Region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/5yg7dxsx5d7h", "metadata": {"raw_id": "8jr1xp5pz85r", "status": "resolved", "resolved_at": "2026-05-19T18:48:53.726Z"}}
{"incident_id": "INC-2026-SENTRY-6df74ljy", "company": "Sentry", "date": "2026-05-19", "title": "Ingestion and alerts for transactions delayed in EU region", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-05-19 14:18:29 UTC] Sentry SRE (Resolved): Ingestion and alerting back to normal\n[2026-05-19 14:05:30 UTC] Sentry SRE (Monitoring): We've put in fixes and are monitoring the situation", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Ingestion and alerting back to normal We've put in fixes and are monitoring the situation", "breaking_config_code": "# Incident architectural state during Ingestion and alerts for transactions delayed in EU region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rdry9sq85gm2", "metadata": {"raw_id": "6df74ljyxcdx", "status": "resolved", "resolved_at": "2026-05-19T14:18:29.996Z"}}
{"incident_id": "INC-2026-SENTRY-4mr92qjf", "company": "Sentry", "date": "2026-05-18", "title": "Ingestion and alerting delays in US", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-05-18 07:11:03 UTC] Sentry SRE (Resolved): We have implemented a fix. Ingestion and alerting have returned to normal operation\n[2026-05-18 05:35:55 UTC] Sentry SRE (Investigating): We are continuing to investigate the issue.\n[2026-05-18 04:27:11 UTC] Sentry SRE (Investigating): We are still investigating the issue.\n[2026-05-18 03:27:20 UTC] Sentry SRE (Investigating): We are still investigating the issue.\n[2026-05-18 02:29:37 UTC] Sentry SRE (Investigating): We are still investigating the issue.\n[2026-05-18 01:41:35 UTC] Sentry SRE (Investigating): We are experiencing ingestion and alerting delays in us for spans, trace metrics, and logs", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: We have implemented a fix. Ingestion and alerting have returned to normal operation We are continuing to investigate the issue. We are still investigating the issue. We are still investigating the issue. We are still investigating the issue. We are experiencing ingestion and alerting delays in us for spans, trace metrics, and logs", "breaking_config_code": "# Incident architectural state during Ingestion and alerting delays in US\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/z6rsqwkrtfnz", "metadata": {"raw_id": "4mr92qjf3wdt", "status": "resolved", "resolved_at": "2026-05-18T07:11:03.891Z"}}
{"incident_id": "INC-2026-SENTRY-j9ggb9ns", "company": "Sentry", "date": "2026-05-13", "title": "Ingestion and alerting delays in us", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-05-13 17:56:30 UTC] Sentry SRE (Resolved): Ingestion and alerting are back to steady state in the US region.\n[2026-05-13 15:49:36 UTC] Sentry SRE (Monitoring): Ingestion and alerting are back to normal. We continue to monitor the situation\n[2026-05-13 14:38:38 UTC] Sentry SRE (Investigating): We are experiencing ingestion and alerting delays in us for spans, transactions, and replays", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Ingestion and alerting are back to steady state in the US region. Ingestion and alerting are back to normal. We continue to monitor the situation We are experiencing ingestion and alerting delays in us for spans, transactions, and replays", "breaking_config_code": "# Incident architectural state during Ingestion and alerting delays in us\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6zg89bt40sdt", "metadata": {"raw_id": "j9ggb9ns8zcl", "status": "resolved", "resolved_at": "2026-05-13T17:56:30.468Z"}}
{"incident_id": "INC-2026-SENTRY-k0wxvxbs", "company": "Sentry", "date": "2026-05-12", "title": "Increased UI and API timeouts", "severity": "MEDIUM", "service_stack": ["Dashboard", "API", "Sentry Relay", "Kafka"], "categories": ["DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-05-12 22:37:36 UTC] Sentry SRE (Resolved): This incident has been resolved.\n[2026-05-12 17:00:29 UTC] Sentry SRE (Monitoring): We've applied a configuration change to mitigate the API/UI errors being experienced.\n[2026-05-12 15:43:27 UTC] Sentry SRE (Investigating): We are continuing to investigate increased UI and API timeouts and errors.\n[2026-05-12 13:51:12 UTC] Sentry SRE (Investigating): We are continuing to investigate increased UI and API timeouts and errors\n[2026-05-12 12:28:24 UTC] Sentry SRE (Investigating): We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: This incident has been resolved. We've applied a configuration change to mitigate the API/UI errors being experienced. We are continuing to investigate increased UI and API timeouts and errors. We are continuing to investigate increased UI and API timeouts and errors We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected.", "breaking_config_code": "# Incident architectural state during Increased UI and API timeouts\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Dashboard\", \"API\", \"Sentry Relay\", \"Kafka\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Dashboard cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/llpp0hn6l4p6", "metadata": {"raw_id": "k0wxvxbs1wz5", "status": "resolved", "resolved_at": "2026-05-12T22:37:36.539Z"}}
{"incident_id": "INC-2026-SENTRY-w39v80r1", "company": "Sentry", "date": "2026-05-11", "title": "Sentry.io timeouts", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-05-11 22:11:27 UTC] Sentry SRE (Resolved): Database performance has returned to normal\n[2026-05-11 21:39:28 UTC] Sentry SRE (Monitoring): We have implemented a fix and are monitoring the situation\n[2026-05-11 21:08:27 UTC] Sentry SRE (Investigating): We are working on restoring normal service. API and application performance should be improved, ingestion still has delays.\n[2026-05-11 20:25:25 UTC] Sentry SRE (Investigating): Our event database continues to have issues and we are actively investigating the issue.\n[2026-05-11 19:28:19 UTC] Sentry SRE (Investigating): Ingestion for spans, replays, and crons is delayed by about 15 minutes.\n[2026-05-11 18:57:02 UTC] Sentry SRE (Investigating): We are continuing to investigate degraded database performance.\n[2026-05-11 15:32:14 UTC] Sentry SRE (Investigating): We are seeing increased UI and API timeouts and errors, due to an overloaded database cluster. Ingestion and alerting should not be affected", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Database performance has returned to normal We have implemented a fix and are monitoring the situation We are working on restoring normal service. API and application performance should be improved, ingestion still has delays. Our event database continues to have issues and we are actively investigating the issue. Ingestion for spans, replays, and crons is delayed by about 15 minutes. We are continuing to investigate degraded database performance", "breaking_config_code": "# Incident architectural state during Sentry.io timeouts\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/j08czhkhxqg4", "metadata": {"raw_id": "w39v80r1tw7p", "status": "resolved", "resolved_at": "2026-05-11T22:11:27.144Z"}}
{"incident_id": "INC-2026-SENTRY-phlszl3p", "company": "Sentry", "date": "2026-05-06", "title": "Sentry.io intermittently unreachable", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-05-06 07:55:58 UTC] Sentry SRE (Resolved): This incident has been resolved.\n[2026-05-06 07:42:28 UTC] Sentry SRE (Investigating): We are currently investigating the issue.", "root_cause_analysis": "Engineering telemetry at Sentry detected service interruption across Sentry Relay, Kafka, ClickHouse, Snuba. The incident resulted from capacity saturation and upstream dependency latency. Engineers identified degraded nodes and isolated traffic to restore nominal operations.", "breaking_config_code": "# Incident architectural state during Sentry.io intermittently unreachable\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/r9j9nkk76j8r", "metadata": {"raw_id": "phlszl3ptb24", "status": "resolved", "resolved_at": "2026-05-06T07:55:58.177Z"}}
{"incident_id": "INC-2026-SENTRY-gcxf5b2f", "company": "Sentry", "date": "2026-04-27", "title": "Ingestion delays and intermittent query failures", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-04-27 20:59:54 UTC] Sentry SRE (Resolved): This incident has been resolved.\n[2026-04-27 17:48:52 UTC] Sentry SRE (Monitoring): The system is operating as normal, we are monitoring the fix.\n[2026-04-27 17:31:23 UTC] Sentry SRE (Investigating): Ingestion is now back to normal, we are slowly increasing write traffic to reduce intermittent API failures\n[2026-04-27 16:52:12 UTC] Sentry SRE (Investigating): We are experiencing delays on our ingestion pipeline. Explorer views are in a degraded state", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: This incident has been resolved. The system is operating as normal, we are monitoring the fix. Ingestion is now back to normal, we are slowly increasing write traffic to reduce intermittent API failures We are experiencing delays on our ingestion pipeline. Explorer views are in a degraded state", "breaking_config_code": "# Incident architectural state during Ingestion delays and intermittent query failures\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/szssn7zf4fkh", "metadata": {"raw_id": "gcxf5b2fshl8", "status": "resolved", "resolved_at": "2026-04-27T20:59:54.489Z"}}
{"incident_id": "INC-2026-SENTRY-3mstbq6r", "company": "Sentry", "date": "2026-04-23", "title": "Application errors in Sentry [us]", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-04-23 02:17:48 UTC] Sentry SRE (Resolved): All application features are now operating as normal.\n[2026-04-23 02:12:24 UTC] Sentry SRE (Monitoring): Ingestion for spans and replays is about 10 minutes behind and catching up. API and Dashboard performance has returned to normal.\n[2026-04-23 02:06:53 UTC] Sentry SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: All application features are now operating as normal. Ingestion for spans and replays is about 10 minutes behind and catching up. API and Dashboard performance has returned to normal. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Application errors in Sentry [us]\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/87vzn5spgk4j", "metadata": {"raw_id": "3mstbq6rdw2n", "status": "resolved", "resolved_at": "2026-04-23T02:17:48.593Z"}}
{"incident_id": "INC-2026-SENTRY-9g0nslrz", "company": "Sentry", "date": "2026-04-22", "title": "Ingestion Issue in US Legacy", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-04-22 08:26:58 UTC] Sentry SRE (Resolved): Between 07:25 UTC and 07:28 UTC, customers sending data to the legacy ingestion endpoint in our US region experienced a brief ingestion disruption lasting approximately 3 minutes. The issue has been fully resolved and ingestion is operating normally.\n\nCustomers using modern DSN endpoints (`*.ingest.us.sentry.io`) were not affected.\n\nThe disruption occurred during a scheduled configuration change. We're investing in additional tooling to detect and mitigate this class of issue faster. We apologize for the inconvenience and appreciate your patience.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: Between 07:25 UTC and 07:28 UTC, customers sending data to the legacy ingestion endpoint in our US region experienced a brief ingestion disruption lasting approximately 3 minutes. The issue has been fully resolved and ingestion is operating normally.\n\nCustomers using modern DSN endpoints (`*.ingest.us.sentry.io`) were not affected.\n\nThe disruption occurred during a scheduled configuration change. We're investing in additional tooling to detect an", "breaking_config_code": "# Incident architectural state during Ingestion Issue in US Legacy\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/t3cnq98b076s", "metadata": {"raw_id": "9g0nslrzjd11", "status": "resolved", "resolved_at": "2026-04-22T08:26:58.618Z"}}
{"incident_id": "INC-2026-SENTRY-8hwy8bps", "company": "Sentry", "date": "2026-04-17", "title": "sentry.io intermittent availability", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-04-17 19:16:08 UTC] Sentry SRE (Resolved): This incident has been resolved.\n[2026-04-17 19:13:38 UTC] Sentry SRE (Monitoring): A fix has been implemented and we are monitoring the results.\n[2026-04-17 19:04:24 UTC] Sentry SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: This incident has been resolved. A fix has been implemented and we are monitoring the results. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during sentry.io intermittent availability\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8cmycw6mxl1q", "metadata": {"raw_id": "8hwy8bpsrvy1", "status": "resolved", "resolved_at": "2026-04-17T19:16:08.121Z"}}
{"incident_id": "INC-2026-SENTRY-ksnqt59v", "company": "Sentry", "date": "2026-04-16", "title": "Span Ingestion Delayed in the EU region", "severity": "MEDIUM", "service_stack": ["Sentry Relay", "Kafka", "ClickHouse", "Snuba"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-04-16 16:08:44 UTC] Sentry SRE (Resolved): The fix has been rolled out and ingestion is recovered.\n[2026-04-16 15:05:53 UTC] Sentry SRE (Monitoring): The delay has recovered and we are monitoring the fix.\n[2026-04-16 14:30:12 UTC] Sentry SRE (Identified): We have identified the issue and are working on a fix.\n[2026-04-16 13:36:39 UTC] Sentry SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by Sentry engineering: The fix has been rolled out and ingestion is recovered. The delay has recovered and we are monitoring the fix. We have identified the issue and are working on a fix. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Span Ingestion Delayed in the EU region\nservice_cluster:\n  provider: \"Sentry\"\n  impacted_components: [\"Sentry Relay\", \"Kafka\", \"ClickHouse\", \"Snuba\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by Sentry SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Sentry Relay cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/vqg8dbj3z6y3", "metadata": {"raw_id": "ksnqt59v4sgp", "status": "resolved", "resolved_at": "2026-04-16T16:08:44.253Z"}}
{"incident_id": "INC-2026-HASHICORP-01M425HC", "company": "HashiCorp", "date": "2026-10-04", "title": "HCP Vault Azure: Cluster Updates and Creation", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-10-04 00:38:03 UTC] HashiCorp SRE (Investigating): We are aware of an issue affecting cluster updates and cluster creation on HCP Vault Dedicated Azure clusters. Our team is actively investigating. We will provide updates as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: We are aware of an issue affecting cluster updates and cluster creation on HCP Vault Dedicated Azure clusters. Our team is actively investigating. We will provide updates as more information becomes available.", "breaking_config_code": "# Incident architectural state during HCP Vault Azure: Cluster Updates and Creation\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01M425HC0FED5GM4SH1DDR55X3", "metadata": {"raw_id": "01M425HC0FED5GM4SH1DDR55X3", "status": "investigating", "resolved_at": null}}
{"incident_id": "INC-2026-HASHICORP-01M3DQCP", "company": "HashiCorp", "date": "2026-09-26", "title": "Users unable to access releases.hashicorp.con", "severity": "HIGH", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-09-26 03:03:21 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-09-26 02:35:09 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-09-26 02:10:25 UTC] HashiCorp SRE (Investigating): Status: **Investigating**\n\n> Users are currently unable to access [releases.hashicorp.com](http://releases.hashicorp.com \"releases.hashicorp.com\"), resulting in 504 errors. The problem affects terraform provider downloads, and Vault Radar access. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.\n[2026-09-26 02:06:01 UTC] HashiCorp SRE (Investigating): Users are currently unable to access releases.hashicorp.com, resulting in 504 errors. The problem affect terraform provider downloads, and Vault Radar access.\nHashiCorp is investigating the problem and will provide further status update updates.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Status: **Investigating**\n\n> Users are currently unable to access [releases.hashicorp.com](http://re", "breaking_config_code": "# Incident architectural state during Users unable to access releases.hashicorp.con\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01M3DQCPFNPDR4WKAVGBXQZYKJ", "metadata": {"raw_id": "01M3DQCPFNPDR4WKAVGBXQZYKJ", "status": "resolved", "resolved_at": "2026-09-26T03:03:21Z"}}
{"incident_id": "INC-2026-HASHICORP-01M37NV4", "company": "HashiCorp", "date": "2026-09-23", "title": "HCP Terraform Returning 404s", "severity": "CRITICAL", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-23 20:02:09 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-09-23 18:06:49 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-09-23 18:02:13 UTC] HashiCorp SRE (Identified): Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update.\n[2026-09-23 17:59:54 UTC] HashiCorp SRE (Investigating): We are continuing to investigate issues with HCP Terraform. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.\n[2026-09-23 17:43:30 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of degraded performance with HCP Terraform. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Our Engineering team has identified the cause and we are actively working on a fix. Once we have add", "breaking_config_code": "# Incident architectural state during HCP Terraform Returning 404s\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01M37NV49VB1CF8B4RKYTQZ0CJ", "metadata": {"raw_id": "01M37NV49VB1CF8B4RKYTQZ0CJ", "status": "resolved", "resolved_at": "2026-09-23T20:02:09Z"}}
{"incident_id": "INC-2026-HASHICORP-01M2NMXX", "company": "HashiCorp", "date": "2026-09-16", "title": "Degraded commit/content scans in HCP Vault Radar", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-16 22:21:12 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-09-16 20:39:45 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. There may still be some higher than normal delays as the backlog is processed. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-09-16 19:57:35 UTC] HashiCorp SRE (Identified): Delays on scans should be minimal at this time, but may still be elevated from normal. Our engineering team is continuing to work on a more permanent fix.\n[2026-09-16 17:53:17 UTC] HashiCorp SRE (Identified): Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update.\n[2026-09-16 17:41:14 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of degraded performance handling some commit/content scans. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. There may still be some higher than normal delays as the backlog is processed. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Delays on scans shoul", "breaking_config_code": "# Incident architectural state during Degraded commit/content scans in HCP Vault Radar\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01M2NMXXN41JWNBCYGAP7VJPJE", "metadata": {"raw_id": "01M2NMXXN41JWNBCYGAP7VJPJE", "status": "resolved", "resolved_at": "2026-09-16T22:21:12Z"}}
{"incident_id": "INC-2026-HASHICORP-01M25QV9", "company": "HashiCorp", "date": "2026-09-10", "title": "Hashicorp Linux packages GPG key rotation", "severity": "HIGH", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-10 20:40:53 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-09-10 16:35:21 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-09-10 15:50:40 UTC] HashiCorp SRE (Identified): Our engineers have identified the issue and are working through remaining packages.\n[2026-09-10 14:45:25 UTC] HashiCorp SRE (Identified): We have updated the keys in the apt and rpm repos and the documentation. Our engineers are working to identify and re-sign packages signed with the older key\n[2026-09-10 13:24:22 UTC] HashiCorp SRE (Identified): We are currently updating documentation and package verification guidance following an ongoing **GPG** key rotation for all HashiCorp Linux packages. The fingerprint currently displayed on our site is outdated and may not match the active signing key.\n\nWe are actively updating the published fingerprint information and related documentation. We will provide an update once the corrected fingerprint details are available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Our engineers have identified the issue and are working through remaining packages. We have updated ", "breaking_config_code": "# Incident architectural state during Hashicorp Linux packages GPG key rotation\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01M25QV97NFJ5AS3NQFCFRC98S", "metadata": {"raw_id": "01M25QV97NFJ5AS3NQFCFRC98S", "status": "resolved", "resolved_at": "2026-09-10T20:40:53Z"}}
{"incident_id": "INC-2026-HASHICORP-01M1PRS0", "company": "HashiCorp", "date": "2026-09-04", "title": "Errors creating new VCS workspaces with Bitbucket cloud provider", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-04 21:46:08 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue with creating new VCS workspaces with the Bitbucket cloud provider. If you continue to experience any problems, please open a ticket with our support team.\n[2026-09-04 20:14:04 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix for errors when creating new VCS workspaces with the Bitbucket cloud provider. We are continuing to monitor the situation and will post an update as soon as the issue is fully resolved.\n[2026-09-04 18:31:17 UTC] HashiCorp SRE (Identified): Our Engineering team has identified the cause of errors when creating new VCS workspaces with the Bitbucket cloud provider. We are actively working on a fix. Once we have additional information, we will share another update.\n[2026-09-04 17:51:59 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of errors when creating new VCS workspaces using the Bitbucket cloud provider. We are working to identify and resolve the issue and will post updates with more information when it is available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue with creating new VCS workspaces with the Bitbucket cloud provider. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix for errors when creating new VCS workspaces with the Bitbucket cloud provider. We are continuing to monitor the situation and will post an update as soon as the issue is fully resolved. Our Engineering team ", "breaking_config_code": "# Incident architectural state during Errors creating new VCS workspaces with Bitbucket cloud provider\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01M1PRS06XEYC48D769GDVZ0YW", "metadata": {"raw_id": "01M1PRS06XEYC48D769GDVZ0YW", "status": "resolved", "resolved_at": "2026-09-04T21:46:08Z"}}
{"incident_id": "INC-2026-HASHICORP-01M036AM", "company": "HashiCorp", "date": "2026-08-15", "title": "Delayed HCP Terraform Runs", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-08-18 12:50:39 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-08-15 18:21:28 UTC] HashiCorp SRE (Monitoring): We've mitigated the delayed HCP Terraform run start times.  Customer jobs running on HashiCorp-hosted agents should start without unusual delay.\n[2026-08-15 17:08:18 UTC] HashiCorp SRE (Investigating): Our engineering team is investigating elevated Terraform Cloud run start times on HashiCorp-hosted agents,  In some cases, runs are taking about 10 minutes to start.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. We've mitigated the delayed HCP Terraform run start times.  Customer jobs running on HashiCorp-hosted agents should start without unusual delay. Our engineering team is investigating elevated Terraform Cloud run start times on HashiCorp-hosted agents,  In some cases, r", "breaking_config_code": "# Incident architectural state during Delayed HCP Terraform Runs\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01M036AM4VGQPG41CC4Q9SN1XK", "metadata": {"raw_id": "01M036AM4VGQPG41CC4Q9SN1XK", "status": "resolved", "resolved_at": "2026-08-18T12:50:39Z"}}
{"incident_id": "INC-2026-HASHICORP-01KZY3YW", "company": "HashiCorp", "date": "2026-08-13", "title": "Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resources", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-08-13 19:06:41 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. We released the Terraform AWS Provider v6.60.0 with a fix. Affected systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-08-13 17:50:44 UTC] HashiCorp SRE (Identified): Our engineering team has identified the cause of the \"Missing Resource Identity After Read\" errors and has completed a fix. We are preparing version 6.60.0 of the Terraform AWS Provider, which includes this fix. v6.60.0 is not yet available in the registry.\n\nThis affects `aws_network_acl_rule` resources that were created with provider versions earlier than 6.39.0. Terraform runs that do not manage `aws_network_acl_rule `resources are unaffected.\n\nUsers encountering errors can continue running Terraform by pinning the provider to version 6.58.0:\n\n\n```\nterraform {\n required_providers {\n  aws = {\n   source = \"hashicorp/aws\"\n   version = \"6.58.0\"\n  }\n }\n}\n```", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. We released the Terraform AWS Provider v6.60.0 with a fix. Affected systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our engineering team has identified the cause of the \"Missing Resource Identity After Read\" errors and has completed a fix. We are preparing version 6.60.0 of the Terraform AWS Provider, which includes this ", "breaking_config_code": "# Incident architectural state during Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resources\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KZY3YWKZEY9QFKPRZQFF5C82", "metadata": {"raw_id": "01KZY3YWKZEY9QFKPRZQFF5C82", "status": "resolved", "resolved_at": "2026-08-13T19:06:41Z"}}
{"incident_id": "INC-2026-HASHICORP-01KZVY0Y", "company": "HashiCorp", "date": "2026-08-12", "title": "Issues When Downloading Terraform Providers", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-08-12 23:14:06 UTC] HashiCorp SRE (Resolved): 3rd party provider downloads are confirmed to be functioning. Please retry any failed Terraform runs, and contact support if you have any further problems.\n[2026-08-12 23:08:22 UTC] HashiCorp SRE (Monitoring): GitHub has [reported resolution of their issues](https://www.githubstatus.com/incidents/lsvy8xsf0gxv \"reported resolution of their issues\"). 3rd party providers should be downloadable again. Please retry any failed Terraform runs and contact support if you continue to have problems.\n[2026-08-12 21:45:20 UTC] HashiCorp SRE (Identified): 3rd-party Terraform providers hosted on GitHub are experiencing download issues. Official providers are unaffected. [GitHub is investigating the problem](https://www.githubstatus.com/incidents/lsvy8xsf0gxv \"GitHub is investigating the problem\"). We will update this status page when we have more information.\n[2026-08-12 21:28:31 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of intermittent failures when downloading Terraform providers. Our team is working to identify the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: 3rd party provider downloads are confirmed to be functioning. Please retry any failed Terraform runs, and contact support if you have any further problems. GitHub has [reported resolution of their issues](https://www.githubstatus.com/incidents/lsvy8xsf0gxv \"reported resolution of their issues\"). 3rd party providers should be downloadable again. Please retry any failed Terraform runs and contact support if you continue to have problems. 3rd-party ", "breaking_config_code": "# Incident architectural state during Issues When Downloading Terraform Providers\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KZVY0YK6JMVA2RR6EX18WHYW", "metadata": {"raw_id": "01KZVY0YK6JMVA2RR6EX18WHYW", "status": "resolved", "resolved_at": "2026-08-12T23:14:06Z"}}
{"incident_id": "INC-2026-HASHICORP-01KZ9N6M", "company": "HashiCorp", "date": "2026-08-05", "title": "HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-08-06 20:33:13 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-08-05 20:46:52 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-08-05 19:39:29 UTC] HashiCorp SRE (Identified): Many customers are seeing failed Terraform runs with SIC-001 errors or 403 forbidden responses. We have confirmed around 220 similar errors in VCS audit logs.  We have found the root cause and are working on a fix. Once we have additional information, we will share another update.\n[2026-08-05 19:08:01 UTC] HashiCorp SRE (Investigating): Many customers are seeing failed Terraform runs with SIC-001 errors or 403 forbidden responses. We have confirmed around 220 similar errors in VCS audit logs, and at least two workspaces are affected. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Many customers are seeing failed Terraform runs with SIC-001 errors or 403 forbidden responses. We h", "breaking_config_code": "# Incident architectural state during HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KZ9N6MT7JM1Y4GGHJP14K0TG", "metadata": {"raw_id": "01KZ9N6MT7JM1Y4GGHJP14K0TG", "status": "resolved", "resolved_at": "2026-08-06T20:33:13Z"}}
{"incident_id": "INC-2026-HASHICORP-01KZB3Q1", "company": "HashiCorp", "date": "2026-08-06", "title": "DR Cluster Creation Failures", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-08-06 11:23:22 UTC] HashiCorp SRE (Resolved): We have implemented a mitigation for the issue affecting new Disaster Recovery (DR) cluster creation. Initial validation has been successful, and new DR cluster creation is functioning as expected. We are continuing to monitor the service to ensure stability before considering the incident fully resolved.\n[2026-08-06 11:20:55 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-08-06 08:40:52 UTC] HashiCorp SRE (Identified): We have identified an issue affecting the creation of new Disaster Recovery (DR) clusters. Customers attempting to create a DR cluster may encounter provisioning failures. Our engineering team has identified the cause and is working on a resolution. Existing clusters and workloads are not impacted. We will provide updates as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: We have implemented a mitigation for the issue affecting new Disaster Recovery (DR) cluster creation. Initial validation has been successful, and new DR cluster creation is functioning as expected. We are continuing to monitor the service to ensure stability before considering the incident fully resolved. Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please", "breaking_config_code": "# Incident architectural state during DR Cluster Creation Failures\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KZB3Q1A2PE4DQMVSMGE53TWV", "metadata": {"raw_id": "01KZB3Q1A2PE4DQMVSMGE53TWV", "status": "resolved", "resolved_at": "2026-08-06T11:20:55Z"}}
{"incident_id": "INC-2026-HASHICORP-01KZ9RQE", "company": "HashiCorp", "date": "2026-08-05", "title": "Infragraph Snapshot are stuck", "severity": "HIGH", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-08-05 22:08:16 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-08-05 20:09:37 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of degraded performance. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. We are aware of and investigating reports of degraded performance. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "breaking_config_code": "# Incident architectural state during Infragraph Snapshot are stuck\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KZ9RQERNZYT0WDPT5BQ0QYGB", "metadata": {"raw_id": "01KZ9RQERNZYT0WDPT5BQ0QYGB", "status": "resolved", "resolved_at": "2026-08-05T22:08:16Z"}}
{"incident_id": "INC-2026-HASHICORP-01KZ97P3", "company": "HashiCorp", "date": "2026-08-05", "title": "Infragraph Service and UI down", "severity": "CRITICAL", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-08-05 15:39:13 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-08-05 15:28:18 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-08-05 15:11:47 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of degraded performance. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. We are aware of and investigating reports of degraded performance. Our team is working to identify a", "breaking_config_code": "# Incident architectural state during Infragraph Service and UI down\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KZ97P3J2GBW60P0SQ3FR557H", "metadata": {"raw_id": "01KZ97P3J2GBW60P0SQ3FR557H", "status": "resolved", "resolved_at": "2026-08-05T15:39:13Z"}}
{"incident_id": "INC-2026-HASHICORP-01KZ7KT0", "company": "HashiCorp", "date": "2026-08-05", "title": "HCP Terraform UI Not Loading", "severity": "HIGH", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-08-05 01:59:29 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-08-05 00:44:27 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-08-05 00:05:09 UTC] HashiCorp SRE (Identified): Customers may see a blank, white screen while using HCP Terraform. This outage currently only impacts the UI; API calls, CI integrations, and CLI usage should not be affected at this time.\n\nOur Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Customers may see a blank, white screen while using HCP Terraform. This outage currently only impact", "breaking_config_code": "# Incident architectural state during HCP Terraform UI Not Loading\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KZ7KT06KN9ZZFGWN3RXFV9WR", "metadata": {"raw_id": "01KZ7KT06KN9ZZFGWN3RXFV9WR", "status": "resolved", "resolved_at": "2026-08-05T01:59:29Z"}}
{"incident_id": "INC-2026-HASHICORP-01KYTMEG", "company": "HashiCorp", "date": "2026-07-30", "title": "app.terraform.io is not loading", "severity": "HIGH", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-31 01:26:52 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue with [app.terraform.io](http://app.terraform.io \"app.terraform.io\") loading correctly. It should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-07-30 23:47:05 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. [app.terraform.io](http://app.terraform.io \"app.terraform.io\") should now load. We are continuing to monitor the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-07-30 23:06:14 UTC] HashiCorp SRE (Investigating): Our Engineering team is investigating degraded performance and inability to load [app.terraform.io](http://app.terraform.io \"app.terraform.io\"). We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue with [app.terraform.io](http://app.terraform.io \"app.terraform.io\") loading correctly. It should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. [app.terraform.io](http://app.terraform.io \"app.terraform.io\") should now load. We are continuing to monitor the situation closel", "breaking_config_code": "# Incident architectural state during app.terraform.io is not loading\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KYTMEGH8061RBGTX8RJ394XJ", "metadata": {"raw_id": "01KYTMEGH8061RBGTX8RJ394XJ", "status": "resolved", "resolved_at": "2026-07-31T01:26:52Z"}}
{"incident_id": "INC-2026-HASHICORP-01KYPY1K", "company": "HashiCorp", "date": "2026-07-29", "title": "HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade", "severity": "HIGH", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-29 20:44:50 UTC] HashiCorp SRE (Resolved): Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1.\n[2026-07-29 16:50:28 UTC] HashiCorp SRE (Monitoring): Our Engineering team has pulled v6.57.0 of the AWS provider from the registry, and continue to work to publish v6.57.1. We will continue to monitor for failures.\n[2026-07-29 16:08:25 UTC] HashiCorp SRE (Identified): Our Engineering team has identified the cause and we are actively working on a fix to publish a patch version of v6.57.1 and pull v6.57.0 from the registry. Prior to that we advise working around the issue by pinning the AWS provider to v6.56.0. Once we have additional information, we will share another update.\n[2026-07-29 12:56:39 UTC] HashiCorp SRE (Identified): Our Engineering team has identified the cause and we are actively working on a fix. A workaround would be to pin the aws provider to v6.56.0 till the fixed patch is released. Once we have additional information, we will share another update.\n[2026-07-29 12:36:59 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of degraded performance after AWS provider update. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1. Our Engineering team has pulled v6.57.0 of the AWS provider from the registry, and continue to work to publish v6.57.1. We will continue to monitor for failures. Our Engineering team has identified the cause and we are actively working on a fix to publish a patch version of v6.57.1 and pull v6.57.0 from the registry. Prior to that we advis", "breaking_config_code": "# Incident architectural state during HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KYPY1KTBE8KWC4E75RXN0XX8", "metadata": {"raw_id": "01KYPY1KTBE8KWC4E75RXN0XX8", "status": "resolved", "resolved_at": "2026-07-29T20:44:50Z"}}
{"incident_id": "INC-2026-HASHICORP-01KYNK8F", "company": "HashiCorp", "date": "2026-07-29", "title": "Increased Load Times for HCP Portal", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-29 15:50:27 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-07-29 01:21:07 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-07-29 00:09:15 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of degraded performance. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. We are aware of and investigating reports of degraded performance. Our team is working to identify a", "breaking_config_code": "# Incident architectural state during Increased Load Times for HCP Portal\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KYNK8FNDVDAMZG76CJ8PDWKZ", "metadata": {"raw_id": "01KYNK8FNDVDAMZG76CJ8PDWKZ", "status": "resolved", "resolved_at": "2026-07-29T15:50:27Z"}}
{"incident_id": "INC-2026-HASHICORP-01KY23QH", "company": "HashiCorp", "date": "2026-07-21", "title": "Terraform Runs Failing to Fetch GitHub Sources Over SSH", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["AUTHENTICATION_FAILURE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-21 12:43:59 UTC] HashiCorp SRE (Resolved): GitHub has completed remediation of the SSH deploy key incident. Terraform runs using GitHub-hosted modules/sources over SSH have recovered, clone operations are functioning normally, and no further authentication failures are being observed.\n[2026-07-21 12:05:28 UTC] HashiCorp SRE (Monitoring): GitHub has completed remediation of the incident affecting SSH deploy keys. Terraform runs using GitHub-hosted modules and sources over SSH have recovered, and clone operations are functioning normally. We are no longer observing related authentication failures and will continue monitoring.\n[2026-07-21 12:04:39 UTC] HashiCorp SRE (Monitoring): GitHub has completed remediation of the incident affecting SSH deploy keys. Terraform runs using GitHub-hosted modules and sources over SSH have recovered, and clone operations are functioning normally. We are no longer observing related authentication failures and will continue monitoring.\n[2026-07-21 10:32:18 UTC] HashiCorp SRE (Investigating): We are investigating failures cloning GitHub-hosted Terraform modules and sources over SSH, caused by an ongoing upstream GitHub incident affecting SSH deploy keys. Runs using `git::ssh://` or `git@github.com:` sources may fail with Permission denied (publickey); HTTPS and registry-based sources are unaffected. We're tracking GitHub's remediation and will update as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: GitHub has completed remediation of the SSH deploy key incident. Terraform runs using GitHub-hosted modules/sources over SSH have recovered, clone operations are functioning normally, and no further authentication failures are being observed. GitHub has completed remediation of the incident affecting SSH deploy keys. Terraform runs using GitHub-hosted modules and sources over SSH have recovered, and clone operations are functioning normally. We a", "breaking_config_code": "# Incident architectural state during Terraform Runs Failing to Fetch GitHub Sources Over SSH\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KY23QHWJSW7BDJ353WBPTCPG", "metadata": {"raw_id": "01KY23QHWJSW7BDJ353WBPTCPG", "status": "resolved", "resolved_at": "2026-07-21T12:43:59Z"}}
{"incident_id": "INC-2026-HASHICORP-01KWYDY6", "company": "HashiCorp", "date": "2026-07-07", "title": "Intermittent Bitbucket Data Center VCS Triggered Terraform run Failures", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-07 21:52:14 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-07-07 20:10:38 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-07-07 15:34:40 UTC] HashiCorp SRE (Identified): Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update.\n[2026-07-07 13:58:02 UTC] HashiCorp SRE (Investigating): We are continuing to investigate reports of intermittent issues with VCS-triggered Terraform runs for only workspaces connected to Bitbucket Data Center. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Our Engineering team has identified the cause and we are actively working on a fix. Once we have add", "breaking_config_code": "# Incident architectural state during Intermittent Bitbucket Data Center VCS Triggered Terraform run Failures\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KWYDY6NZFW5Z8NH8ZWZ29KM9", "metadata": {"raw_id": "01KWYDY6NZFW5Z8NH8ZWZ29KM9", "status": "resolved", "resolved_at": "2026-07-07T21:52:14Z"}}
{"incident_id": "INC-2026-HASHICORP-01KWC7AT", "company": "HashiCorp", "date": "2026-06-30", "title": "Terraform releases page experiencing errors", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-30 13:00:03 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. The release page should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-06-30 12:45:34 UTC] HashiCorp SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue with hitting endpoints on [releases.hashicorp.com/terraform/](http://releases.hashicorp.com/terraform/ \"releases.hashicorp.com/terraform/\"). We are monitoring the situation closely and will post an update as soon as the issue is confirmed resolved.\n[2026-06-30 12:16:15 UTC] HashiCorp SRE (Investigating): We continue to investigate new reports of 50x errors when attempting to access [releases.hashicorp.com/terraform/](http://releases.hashicorp.com/terraform/ \"releases.hashicorp.com/terraform/\"). Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. The release page should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has implemented a fix to resolve the issue with hitting endpoints on [releases.hashicorp.com/terraform/](http://releases.hashicorp.com/terraform/ \"releases.hashicorp.com/terraform/\"). We are monitoring the situation closely and will post an upda", "breaking_config_code": "# Incident architectural state during Terraform releases page experiencing errors\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KWC7AT3FX788RDTR759G7SNV", "metadata": {"raw_id": "01KWC7AT3FX788RDTR759G7SNV", "status": "resolved", "resolved_at": "2026-06-30T13:00:03Z"}}
{"incident_id": "INC-2026-HASHICORP-01KWBMP3", "company": "HashiCorp", "date": "2026-06-30", "title": "Cluster Provisioning and Management Operations Impacted", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-30 08:08:13 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-06-30 06:50:22 UTC] HashiCorp SRE (Investigating): We are currently investigating an issue affecting HVD cluster management operations. Customers may experience failures when creating, deleting, or resizing (upscaling) HVD clusters. Existing clusters and Vault operations remain unaffected. Our engineering team is actively investigating the issue and working to restore normal service. We will provide updates as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. We are currently investigating an issue affecting HVD cluster management operations. Customers may experience failures when creating, deleting, or resizing (upscaling) HVD clusters. Existing clusters and Vault operations remain unaffected. Our engineering team is activ", "breaking_config_code": "# Incident architectural state during Cluster Provisioning and Management Operations Impacted\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KWBMP3GJRBZ0H4EBZTRNSE6Z", "metadata": {"raw_id": "01KWBMP3GJRBZ0H4EBZTRNSE6Z", "status": "resolved", "resolved_at": "2026-06-30T08:08:13Z"}}
{"incident_id": "INC-2026-HASHICORP-01KVZVEW", "company": "HashiCorp", "date": "2026-06-25", "title": "Intermittent 5XX errors for registry", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-06-25 18:16:40 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-06-25 17:27:28 UTC] HashiCorp SRE (Identified): Terraform Registry is experiencing elevated error rates affecting terraform init workflows and documentation access. Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update.\n[2026-06-25 16:57:53 UTC] HashiCorp SRE (Investigating): Terraform Registry is experiencing elevated error rates affecting terraform init workflows and documentation access. Our engineering team is investigating the issue.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Terraform Registry is experiencing elevated error rates affecting terraform init workflows and documentation access. Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update. T", "breaking_config_code": "# Incident architectural state during Intermittent 5XX errors for registry\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KVZVEWTKPS0WBSQ40P5JYAEK", "metadata": {"raw_id": "01KVZVEWTKPS0WBSQ40P5JYAEK", "status": "resolved", "resolved_at": "2026-06-25T18:16:40Z"}}
{"incident_id": "INC-2026-HASHICORP-01KVPTXF", "company": "HashiCorp", "date": "2026-06-22", "title": "Cluster Creation Is Failing", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-22 08:10:42 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-06-22 07:01:48 UTC] HashiCorp SRE (Identified): Our Engineering team has identified the cause to be a a CI build-number drift between app-image and terraform-image jobs in the same workflow run caused the service to reference a non-existent terraform image tag. We are actively working on a fix. Once we have additional information, we will share another update.\n[2026-06-22 04:55:13 UTC] HashiCorp SRE (Investigating): We are aware of the issue that the cluster. creation is failing. We are actively investigating the issue. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our Engineering team has identified the cause to be a a CI build-number drift between app-image and terraform-image jobs in the same workflow run caused the service to reference a non-existent terraform image tag. We are actively working on a fix. Once we have addition", "breaking_config_code": "# Incident architectural state during Cluster Creation Is Failing\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KVPTXFSPZ5389AVP5X5NK264", "metadata": {"raw_id": "01KVPTXFSPZ5389AVP5X5NK264", "status": "resolved", "resolved_at": "2026-06-22T08:10:42Z"}}
{"incident_id": "INC-2026-HASHICORP-01KVEJH0", "company": "HashiCorp", "date": "2026-06-18", "title": "Terraform Provider Azure RM", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-19 22:46:18 UTC] HashiCorp SRE (Resolved): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-06-19 16:46:47 UTC] HashiCorp SRE (Identified): Our engineering team continues to coordinate with the relevant provider while we work toward a fix. We’ll share another update as soon as we have more information.\n[2026-06-19 01:10:59 UTC] HashiCorp SRE (Identified): Our engineering team has identified the cause as an upstream platform change, and we’re actively coordinating with the relevant provider while we work toward a fix. We’ll share another update as soon as we have more information.\n[2026-06-18 23:54:39 UTC] HashiCorp SRE (Investigating): We’re investigating an issue affecting Terraform state refresh for Azure App Service Environment v3 resources. Our Engineering teams are actively investigating the issue. We will update as soon as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Our engineering team continues to coordinate with the relevant provider while we work toward a fix. We’ll share another update as soon as we have more information. Our engineering team has identified the cause as an upstream platform change, and we’re actively coordina", "breaking_config_code": "# Incident architectural state during Terraform Provider Azure RM\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KVEJH06GXGGQ59MR003WNV76", "metadata": {"raw_id": "01KVEJH06GXGGQ59MR003WNV76", "status": "resolved", "resolved_at": "2026-06-19T22:46:18Z"}}
{"incident_id": "INC-2026-HASHICORP-01KVA1Y0", "company": "HashiCorp", "date": "2026-06-17", "title": "Issues Re-enabling SAML connections", "severity": "MEDIUM", "service_stack": ["Terraform Cloud", "Vault", "Consul", "Nomad"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-06-17 07:00:36 UTC] HashiCorp SRE (Resolved): Our upstream provider has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.\n[2026-06-17 06:28:31 UTC] HashiCorp SRE (Monitoring): We are seeing our upstream provider services recovering and our own tests are now passing. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.\n[2026-06-17 05:49:50 UTC] HashiCorp SRE (Identified): Our Engineering team has identified the cause Our Engineering team has identified the cause to be with an upstream provider. We are working with the provider to restore functionality as soon as possible. Once we have additional information, we will share another update.\n[2026-06-17 05:47:42 UTC] HashiCorp SRE (Investigating): We are aware of and investigating reports of errors when attempting to enable SAML for organizations right after having deleted SAML configurations.\n\nFor the moment, we strongly recommend not deleting SAML configurations from an organization.", "root_cause_analysis": "Official investigation timeline recorded by HashiCorp engineering: Our upstream provider has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. We are seeing our upstream provider services recovering and our own tests are now passing. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Our Engineering team has identified the cause Our Engineering team has id", "breaking_config_code": "# Incident architectural state during Issues Re-enabling SAML connections\nservice_cluster:\n  provider: \"HashiCorp\"\n  impacted_components: [\"Terraform Cloud\", \"Vault\", \"Consul\", \"Nomad\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by HashiCorp SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Terraform Cloud cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://status.hashicorp.com/incidents/01KVA1Y0VSYC53BZE9V4BCRYSG", "metadata": {"raw_id": "01KVA1Y0VSYC53BZE9V4BCRYSG", "status": "resolved", "resolved_at": "2026-06-17T07:00:36Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-6z6dt3t1", "company": "DigitalOcean", "date": "2026-10-03", "title": "A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)", "severity": "MEDIUM", "service_stack": ["Bangalore", "BLR1", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-10-03 14:51:13 UTC] DigitalOcean SRE (Resolved): From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region.\n\nMultiple network paths operated by our upstream connectivity providers were unavailable, including redundant paths intended to maintain connectivity during a disruption. Traffic shifted to a remaining link with insufficient capacity to handle the full load, resulting in network saturation and the connectivity issues described above. Our Engineering and Network teams worked closely with our upstream providers to restore normal routing and connectivity. All affected services have since returned to normal operation.\n\nWe apologize for the disruption and its impact on your work. If you continue to experience unexpected behavior, please open a support ticket so our team can investigate and assist you.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region.\n\nMultiple network paths operated by our upstream connectivity pr", "breaking_config_code": "# Incident architectural state during A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Bangalore\", \"BLR1\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Bangalore cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/kj9rd8tnd1wt", "metadata": {"raw_id": "6z6dt3t1bhb9", "status": "resolved", "resolved_at": "2026-10-03T14:51:13.627Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-grb2v0td", "company": "DigitalOcean", "date": "2026-09-16", "title": "Support Portal Service Disruption", "severity": "MEDIUM", "service_stack": ["Support Center", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-09-16 21:09:31 UTC] DigitalOcean SRE (Resolved): From 08:06 UTC to 13:41 UTC, users may have experienced issues accessing the Support Portal, creating new support tickets, or reviewing existing support requests. \n\nOur Engineering team has confirmed the full resolution of the issue affecting the Support Portal following a fix from our upstream provider. We have verified that the Support Portal, ticket creation, and ticket review are now operating normally.\n\nIf you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and appreciate your patience.\n[2026-09-16 14:07:22 UTC] DigitalOcean SRE (Monitoring): The Support Portal and ticket creation are now accessible. Our upstream provider has applied a fix, and we've verified ticket creation and review are working as expected. We'll continue monitoring for the next 2 hours to confirm full stability and will post a final update once the incident is closed. If you're still unable to access the portal, please use our Support Contact form as a backup: https://www.digitalocean.com/company/contact/support\nWe apologize for the disruption and appreciate your patience.\n[2026-09-16 09:48:19 UTC] DigitalOcean SRE (Investigating): Our Support Portal is currently experiencing issues due to a third-party service disruption impacting our systems. During this time, customers may be unable to access the Support Portal or create new support tickets for their concerns. Existing support requests may also experience delayed responses from our Support team.\n\nAs a workaround if you're unable to access the Support Portal or need to create a new support ticket, please submit your request via Support Contact form: https://www.digitalocean.com/company/contact/support.\n\nWe apologize for the inconvenience and appreciate your patience while we work to resolve the issue. We'll provide another update as soon as we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: From 08:06 UTC to 13:41 UTC, users may have experienced issues accessing the Support Portal, creating new support tickets, or reviewing existing support requests. \n\nOur Engineering team has confirmed the full resolution of the issue affecting the Support Portal following a fix from our upstream provider. We have verified that the Support Portal, ticket creation, and ticket review are now operating normally.\n\nIf you continue to experience problems", "breaking_config_code": "# Incident architectural state during Support Portal Service Disruption\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Support Center\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Support Center cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/n6hr8jd64qjl", "metadata": {"raw_id": "grb2v0td1nq5", "status": "resolved", "resolved_at": "2026-09-16T21:09:31.508Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-1t16vfgq", "company": "DigitalOcean", "date": "2026-09-09", "title": "Power Degradation impacting GPU Performance in ATL1", "severity": "MEDIUM", "service_stack": ["ATL1", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-09-09 12:25:52 UTC] DigitalOcean SRE (Resolved): This incident is now resolved. Power redundancy has been fully restored, and we have confirmed that customer impact has been mitigated. We are closing this incident.\n[2026-09-09 11:32:30 UTC] DigitalOcean SRE (Monitoring): The power issue affecting part of our ATL1 datacenter has been fully resolved. Power redundancy has been restored, and any potential customer impact has been mitigated.\n\nWe will continue monitoring the environment to ensure continued stability.\n[2026-09-09 10:47:40 UTC] DigitalOcean SRE (Investigating): We are investigating a power issue affecting part of our ATL1 datacenter. Redundant power systems are keeping servers online, and we have not observed any server outages.\n\nHowever, available power capacity is reduced, which may cause degraded performance for some GPU workloads, particularly during periods of high utilization.\n\nOur datacenter and infrastructure teams are working to restore full power redundancy. We will provide an update as more information becomes available. We apologize for the inconvenience and appreciate your patience.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: This incident is now resolved. Power redundancy has been fully restored, and we have confirmed that customer impact has been mitigated. We are closing this incident. The power issue affecting part of our ATL1 datacenter has been fully resolved. Power redundancy has been restored, and any potential customer impact has been mitigated.\n\nWe will continue monitoring the environment to ensure continued stability. We are investigating a power issue affe", "breaking_config_code": "# Incident architectural state during Power Degradation impacting GPU Performance in ATL1\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"ATL1\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on ATL1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/g4s2358yl9tt", "metadata": {"raw_id": "1t16vfgq3zpx", "status": "resolved", "resolved_at": "2026-09-09T12:25:52.141Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-4qwm6pzl", "company": "DigitalOcean", "date": "2026-08-24", "title": "Cloud Control Panel and API", "severity": "CRITICAL", "service_stack": ["API", "Cloud Control Panel", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-09-15 18:44:45 UTC] DigitalOcean SRE (Postmortem): ## 1. What happened\n\nBetween 16:56 UTC and 23:09 UTC on August 24, 2026, customers using DigitalOcean’s Cloud Control Panel, Public API, and dependent product management systems experienced elevated request error rates, peaking at 25%, in two distinct windows totaling 3.5 hours of active degradation within a 6-hour span. Running Droplets, network routing, and block storage \\(Volumes\\) remained fully functional and unaffected throughout the event. No customer data loss occurred.\n\nThe event was initiated during a planned infrastructure migration of the database layer supporting identity, authentication, and authorization services. The migration introduced increased execution latency for a critical authorization query. In response to the elevated query latency, multiple upstream services initiated automated hedged retries. This secondary request amplification led to queue buildup in excess of the authentication service pool's processing throughput, resulting in cascading request timeouts across the authorization path.\n\nTo mitigate the initial degradation, engineering teams rerouted authorization traffic onto a single healthy processing path and temporarily disabled hedging for primary callers, successfully restoring service availability. However, upon returning traffic to the standard multipath routing configuration, lingering query latency combined with retry behavior from unhedged callers caused recurrent queue saturation, leading to the second window of degradation.\n\n## 2. Impact\n\n* Active customer accounts \\(<2%\\) experienced one or more API or Control Panel request failures during the event windows.\n* Aggregate failure rates across both impact windows averaged approximately 10% of authenticated requests, with a peak error rate of 25% during the second window.\n* Affected management control planes included the Cloud Control Panel, Public API, Kubernetes cluster authentication, Container Registry, and Serverless / AI Inference endpoints.\n* Data plane components—including active Droplets, network routing, and block storage volumes—maintained 100% availability, as established connections do not depend on the affected authorization control path. There was zero data loss.\n\n## 3. Current state\n\nAll impacted control plane services have been restored to nominal operational capacity. The database infrastructure migration has been completed. Remediation controls have been validated to ensure system stability against similar query latency scenarios.\n\n## 4. Preventing recurrence\n\nTo prevent future occurrences and enhance systemic resilience, DigitalOcean has implemented the following technical enhancements:\n\n1. Automated Request Throttling and Circuit Breaking:\n\nDeployed automated circuit breakers across upstream services to detect downstream dependency degradation and automatically suppress hedged/retry amplification. Completed a broad architecture audit to ensure retry suppression and circuit breaking are uniformly enforced across all control plane services.\n\n1. Queue Management and Load Shedding:\n\nImplemented fast-fail load-shedding mechanisms to prevent request queue saturation during dependency slowness, accompanied by proactive telemetry alerts to identify queue backing prior to customer impact.\n\n1. Graceful Service Degradation:\n\nConfigured critical authorization components to operate in degraded execution modes utilizing asynchronous, eventually-consistent data replicas during primary database latency events.\n\n## 5. Timeline\n\n| **Time UTC** | **Event** |\n| --- | --- |\n| 16:56 | A specific authorization query began running significantly slower than its historical baseline. |\n| 16:58 | Automated monitoring detected abnormal error rates and latency; detected within 5 minutes of impact starting. |\n| 17:05–18:52 | Operators tuned retry configuration and consolidated requests to a healthy service instance \\(first unavailability window closed\\). |\n| 21:30 | Shifting traffic back to the production pattern caused the same saturation problem \\(second unavailability window begins\\). |\n| 21:30–23:09 | Teams disabled the retry/amplification behavior across the remaining affected services and added additional read capacity for the slow query. Service was restored to a stable state. |\n[2026-08-25 19:04:33 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed all services remain stable and we will now resolve this incident. Further details on root cause and mitigation will be provided in a postmortem via this status page for users interested in learning more. \n\nThank you for your patience throughout this incident. If you continue to experience any issues, please reach out to Support from within your account\n[2026-08-25 16:30:28 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has continued to monitor the health of all services and has observed no recurrence of impact over the past 12+ hours. We will continue to monitor services for a short period to confirm stability before we mark this incident resolved. We understand the impact this incident had for DigitalOcean users and we will publish a postmortem on the status page to provide further details on root cause and mitigation.\n[2026-08-25 00:54:37 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented mitigation measures to address the issue impacting the DigitalOcean public API and Cloud Control Panel. We are seeing improvements, and users should now be able to access the Cloud Control Panel and use the public API normally. \n\nWe are continuing to monitor the service to ensure it remains stable and will provide further updates as more information becomes available. We appreciate your patience and understanding.\n[2026-08-24 22:27:18 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating a recurrence of the issue impacting the DigitalOcean public API and Cloud Control Panel. This issue does not impact our data plane (i.e. running droplets).\n\nUsers may experience difficulties accessing the Cloud Control Panel, along with elevated latency and intermittent errors when accessing the public API or Cloud Control Plane.\n\nWe are actively investigating the issue and working to restore normal service. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.\n[2026-08-24 19:14:18 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented mitigation measures to address the issue affecting the DigitalOcean public API and Cloud Control Panel. We are seeing requests succeed, and users should now be able to access the Cloud Control Panel and issue/receive API requests normally.\n\nWe are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.\n[2026-08-24 18:33:07 UTC] DigitalOcean SRE (Investigating): We are continuing to investigate the issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, we are seeing some improvement in latency/error rates and some users may now be able to access the Cloud Control Panel.\n\nServerless Inference users may currently experience 403 and 503 errors when making API requests or accessing affected services.\n\nWe will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.\n[2026-08-24 17:14:43 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, users will see elevated 5xx errors for all API requests, including things like creates for various products. Users may also be unable to access cloud.digitalocean.com. \n\nWe are actively investigating the root cause and will provide updates as soon as more information becomes available.\n\nWe apologize for the inconvenience and appreciate your patience.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: ## 1. What happened\n\nBetween 16:56 UTC and 23:09 UTC on August 24, 2026, customers using DigitalOcean’s Cloud Control Panel, Public API, and dependent product management systems experienced elevated request error rates, peaking at 25%, in two distinct windows totaling 3.5 hours of active degradation within a 6-hour span. Running Droplets, network routing, and block storage \\(Volumes\\) remained fully functional and unaffected throughout the event.", "breaking_config_code": "# Incident architectural state during Cloud Control Panel and API\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"API\", \"Cloud Control Panel\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8l5c24cxh3hr", "metadata": {"raw_id": "4qwm6pzlx1z3", "status": "postmortem", "resolved_at": "2026-08-25T19:04:33.091Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-r96y45y5", "company": "DigitalOcean", "date": "2026-08-23", "title": "Managed Databases Creation", "severity": "MEDIUM", "service_stack": ["NYC1", "NYC3", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-08-23 14:33:31 UTC] DigitalOcean SRE (Resolved): Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally.\n\nOur Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team: https://cloudsupport.digitalocean.com/s/\n[2026-08-23 11:30:34 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented the necessary fixes affecting Managed Database cluster creation in the NYC3 and NYC1 regions. Users should now be able to create new Managed Database clusters.   \n\nWe are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.\n[2026-08-23 07:06:56 UTC] DigitalOcean SRE (Investigating): We continue to investigate an issue affecting DigitalOcean Managed Databases cluster creation across multiple regions.\n\nDuring this time, users may experience errors when creating Managed Database clusters via the Cloud Control Panel or API.\n\nOur engineering team is implementing a mitigation and working to restore normal provisioning. We will provide another update as soon as more information is available.\n[2026-08-23 05:11:37 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue with our Managed Database product. At this time, users may experience errors while creating clusters, both via Cloud Control Panel and API requests.\n\nWe apologize for the inconvenience and will share an update once we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally.\n\nOur Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team: https://c", "breaking_config_code": "# Incident architectural state during Managed Databases Creation\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"NYC1\", \"NYC3\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on NYC1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8ld5fpw01tg4", "metadata": {"raw_id": "r96y45y5sx59", "status": "resolved", "resolved_at": "2026-08-23T14:33:31.719Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-s0dyq97c", "company": "DigitalOcean", "date": "2026-08-21", "title": "Container Registry and Spaces Accessibility", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-21 14:52:40 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved. \n\nSpaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images without further issues.\n\nIf you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.\n[2026-08-21 13:06:06 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has identified the issue affecting Container Registry and Spaces buckets, and a fix has been applied.\n\nSpaces accessibility via the Cloud Control Panel should now be restored, and pushing and pulling container images should be back to normal. \n\nWe are continuing to monitor the results to ensure the issue has been fully resolved and will provide another update once we've confirmed normal service has been restored.\n[2026-08-21 12:59:42 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating reports of an issue affecting Container Registry and Spaces buckets in some regions.\n\nDuring this time, customers may experience failures when pushing or pulling container images. Additionally, customers may experience issues accessing Spaces via the Cloud Control Panel, where the page may display \"Looks like something went wrong…\"\n\nOur Engineering team is actively investigating the issue and treating it with priority. We will provide another update as soon as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the issue impacting Container Registry and Spaces accessibility has been resolved. \n\nSpaces accessibility via the Cloud Control Panel is now restored, and pushing and pulling container images is succeeding as expected. Customers who previously encountered these issues should now be able to access Spaces and deploy their container images without further issues.\n\nIf you continue to experience any problems, pl", "breaking_config_code": "# Incident architectural state during Container Registry and Spaces Accessibility\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/2b4phnbmtm49", "metadata": {"raw_id": "s0dyq97c5v72", "status": "resolved", "resolved_at": "2026-08-21T14:52:40.373Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-qd8v4wdd", "company": "DigitalOcean", "date": "2026-08-19", "title": "Major Service Interruption in MKC1", "severity": "CRITICAL", "service_stack": ["MKC1", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-08-19 19:34:54 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally.\n\nGPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates.\n\nThank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account.\n[2026-08-19 18:59:03 UTC] DigitalOcean SRE (Monitoring): At this time, the regional control plane is fully healthy. CPU Droplets, Managed databases, Load balancers, Block storage and Spaces are operating normally. Droplet create, resize and other management operations are working. Kubernetes (DOKS) control planes are reachable.\n\nOur teams are continuing to work with the facility to restore all equipment. GPU Droplets in MKC1 remain offline or unreachable. DOKS GPU worker nodes may remain NotReady, and GPU-backed inference endpoints in this region may be unavailable. \n\nWe will monitor the regional control plane for a short time and then resolve this incident. GPU customers will receive personalized updates with more information in lieu of this status page. \n\nIf you have questions about your affected resources, contact support and reference this incident.\n[2026-08-19 15:28:37 UTC] DigitalOcean SRE (Identified): Our Engineering team continues to work on the issue affecting the MKC1 region. We are actively working to restore connectivity and bring the impacted nodes back online.\nWe will provide another update as soon as we have more information.\n[2026-08-19 12:22:47 UTC] DigitalOcean SRE (Identified): We have identified the root cause of the issue in the MKC1 region affecting multiple racks and nodes. Our Engineering team is actively implementing remediation steps to restore connectivity and bring the impacted nodes back online.\nDuring this time, customers may continue to experience disruptions to GPU workloads and Serverless Inference. Kubernetes (DOKS) worker nodes may also remain in a NotReady state, and customers may be unable to reach Kubernetes API endpoints or perform cluster-management operations in affected clusters. We will provide another update as soon as we have more information.\n[2026-08-19 11:10:06 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an issue in the MKC1 region affecting multiple racks and nodes.\n\nDuring this time, customers may experience disruptions to GPU workloads, and Kubernetes (DOKS) worker nodes may enter a NotReady state.\n\nOur team is actively working to restore connectivity and bring impacted nodes back online. If you continue to experience issues, please open a support ticket from within your account.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally.\n\nGPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates.\n\nThank you for your patience throughout this inci", "breaking_config_code": "# Incident architectural state during Major Service Interruption in MKC1\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"MKC1\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on MKC1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/gdzqj0v18x0r", "metadata": {"raw_id": "qd8v4wddyqjr", "status": "resolved", "resolved_at": "2026-08-19T19:34:54.136Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-y3kn2w2q", "company": "DigitalOcean", "date": "2026-08-13", "title": "Volume Attach/Detach events in FRA1", "severity": "MEDIUM", "service_stack": ["FRA1", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["QUEUE_DELAY", "STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-08-13 14:59:44 UTC] DigitalOcean SRE (Resolved): Between Aug 13, 09:50 UTC  and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters.\n\nDuring this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources.\n\nBlock Storage Volumes attachment and detachment operations now appear to be functioning normally, and customers should no longer experience issues with these operations. For Managed Kubernetes clusters specifically, some residual cleanup of affected volume attachments may still be needed, and our team is actively working through this.\n\nWe apologize for any inconvenience this may have caused. If you continue to experience issues with Block Storage Volumes operations, please don't hesitate to open a support ticket for further investigation. Our team will be happy to assist you.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between Aug 13, 09:50 UTC  and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters.\n\nDuring this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources.\n\nBlock Storage Volumes attachment and detachment operations now appear to be functioning normally, and cu", "breaking_config_code": "# Incident architectural state during Volume Attach/Detach events in FRA1\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"FRA1\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on FRA1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/yldnj7859gcp", "metadata": {"raw_id": "y3kn2w2qf5s4", "status": "resolved", "resolved_at": "2026-08-13T14:59:44.895Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-2wql4f4s", "company": "DigitalOcean", "date": "2026-08-08", "title": "Account Registration, Droplets, and Related Services", "severity": "MEDIUM", "service_stack": ["Global", "Reserved IP", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["DATABASE_DEGRADATION"], "symptom_logs": "[2026-08-09 01:01:02 UTC] DigitalOcean SRE (Resolved): Our Engineering team confirms the full resolution of the issue affecting all impacted services, including new account registration, Droplet Creation, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet Console, and Database cluster creation.\n\nWe apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account.\n[2026-08-09 00:31:29 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix for the issue affecting new account registration, Droplets, Reserved IPs, Snapshots, and DOKS clusters across multiple regions, and is currently monitoring the situation. At this time, customers should no longer experience errors with:\n\nNew account registration\nDroplet creation\nReserved IP allocation\nAutomated Backups and Snapshots operations\nDroplet Autoscale scaling operations\nDOKS cluster operations\nGenAI services\nAccess to the Droplet console\nDatabase cluster creation\n\nWe will continue to monitor the situation to ensure that all services are stable and functioning as expected. We will post an update as soon as the issue is fully resolved.\n[2026-08-08 22:02:55 UTC] DigitalOcean SRE (Identified): Our Engineering team continues to work on implementing and rolling out a fix for the issue affecting multiple services across multiple regions, including new account registration, Droplets, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet console, and Database cluster creation.\n\nCustomers may continue to experience the previously reported service disruptions while remediation efforts remain in progress. We will provide another update as soon as more information becomes available.\n[2026-08-08 20:02:35 UTC] DigitalOcean SRE (Identified): Our Engineering team has identified the root cause of the issue affecting new account registration, Droplets, Reserved IPs, Snapshots, and DOKS clusters across multiple regions.\n\nCustomers may experience the following:\n\nUnable to create new accounts\nUnable to create Droplets\nUnable to allocate Reserved IPs\nFailures with Automated Backups and Snapshots operations\nDroplet Autoscale scaling operations not working as expected\nDOKS cluster operations failing\nGenAI services impacted\nUnable to access the Droplet console\nDatabase clusters stuck in a \"Creating\" state\n\nOur Engineering team is working on implementing a fix and we will provide another update as soon as more information becomes available.\n[2026-08-08 19:38:23 UTC] DigitalOcean SRE (Investigating): Our Engineering team is continuing to investigate reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions.\n\nDuring this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected.\n\nFurther investigation has found that GenAI services are also affected due to this issue, customers may also be unable to access the Droplet console, and Database clusters may be stuck in a \"Creating\" state.\n\nOur Engineering team is actively investigating the issue and we will provide another update as soon as more information becomes available.\n[2026-08-08 18:57:49 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions.\n\nDuring this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected.\n\nOur Engineering team is actively investigating the issue and we will provide another update as soon as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team confirms the full resolution of the issue affecting all impacted services, including new account registration, Droplet Creation, Reserved IPs, Automated Backups and Snapshots, Droplet Autoscale, DOKS clusters, GenAI services, the Droplet Console, and Database cluster creation.\n\nWe apologize for the inconvenience. If you continue to experience any issues, please open a support ticket from within your account. Our Engineering t", "breaking_config_code": "# Incident architectural state during Account Registration, Droplets, and Related Services\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Reserved IP\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/grfh9nf5bp3f", "metadata": {"raw_id": "2wql4f4sb13r", "status": "resolved", "resolved_at": "2026-08-09T01:01:02.727Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-cg3q7h89", "company": "DigitalOcean", "date": "2026-08-06", "title": "Functions on App Platform", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-08-06 21:05:05 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the issue affecting Functions on App Platform has been fully resolved. Functions builds, deploys, and requests to Functions endpoints are all working as expected. The fix implemented earlier was successful, and we are no longer seeing any problems affecting Functions.\n\nHowever, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation.\n[2026-08-06 20:02:03 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix for the issue affecting Functions on App Platform. Functions builds/deploys and requests to Functions endpoints should now be completing successfully. We are currently monitoring the situation to ensure the service has returned to normal operation and remains stable.\n\nWe apologize for the inconvenience and will provide a further update once the incident is confirmed resolved.\n[2026-08-06 19:01:27 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue impacting Functions on App Platform. During this time, users may experience build/deploy failures for Functions components, and requests to Functions endpoints may fail with a 504 error, caused by an SSL error when App Platform attempts to forward requests to Functions. This issue currently appears to be isolated to Functions deployed within App Platform.\n\nWe apologize for the inconvenience and will share an update once we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the issue affecting Functions on App Platform has been fully resolved. Functions builds, deploys, and requests to Functions endpoints are all working as expected. The fix implemented earlier was successful, and we are no longer seeing any problems affecting Functions.\n\nHowever, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. Our Engineerin", "breaking_config_code": "# Incident architectural state during Functions on App Platform\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/7pm9l1jwpkr6", "metadata": {"raw_id": "cg3q7h89dbnq", "status": "resolved", "resolved_at": "2026-08-06T21:05:05.672Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-vjm8qnbt", "company": "DigitalOcean", "date": "2026-08-06", "title": "Multiple Services Availability", "severity": "MEDIUM", "service_stack": ["Global", "Cloud Firewall", "DNS", "Droplets Hypervisor"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-08-06 16:33:14 UTC] DigitalOcean SRE (Resolved): Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing.\n\nCustomers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes experienced failures. These operations returned errors, preventing customers from managing their resources. Additionally, event processing was delayed or failed during this window, which may have impacted the timeliness of resource status updates and notifications.\n\nThe services have recovered and are now operating normally. Customers should no longer experience issues with write operations, configuration changes, or event processing.\n\nWe apologize for any inconvenience this may have caused. If you continue to experience issues with any of these services, please don't hesitate to open a support ticket. Our team will be happy to assist you.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing.\n\nCustomers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes", "breaking_config_code": "# Incident architectural state during Multiple Services Availability\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Cloud Firewall\", \"DNS\", \"Droplets Hypervisor\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/zscj6w048lfx", "metadata": {"raw_id": "vjm8qnbt45tb", "status": "resolved", "resolved_at": "2026-08-06T16:33:14.860Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-l20hw5cf", "company": "DigitalOcean", "date": "2026-08-04", "title": "Spaces Cold Storage Billing", "severity": "MEDIUM", "service_stack": ["Global", "Billing", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-08-04 21:42:43 UTC] DigitalOcean SRE (Resolved): As of 21:06 UTC, our Engineering team has resolved the issue affecting Spaces Cold Storage billing. An error in our billing processing system caused incorrect values to be reflected in daily usage and current invoices for customers with cold storage buckets.\n\nOur team identified and corrected an issue with the billing data sync, ensuring accurate usage reporting. If you continue to experience any issues, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.\n[2026-08-04 20:44:49 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix for the issue affecting Spaces Cold Storage billing and is currently monitoring the situation. Customers with cold storage buckets should no longer see incorrect values reflected in their daily usage and current invoices. We will post an update as soon as the issue is fully resolved.\n[2026-08-04 18:52:27 UTC] DigitalOcean SRE (Identified): Our Engineering team has identified the issue affecting Spaces Cold Storage billing. The team is actively working on a fix to resolve the issue. We apologize for the inconvenience and will provide another update as soon as more information becomes available.\n[2026-08-04 16:13:35 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue affecting Spaces Cold Storage billing. During this time, customers with cold storage buckets may see incorrect values reflected in their daily usage and current invoices.\n\nWe apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: As of 21:06 UTC, our Engineering team has resolved the issue affecting Spaces Cold Storage billing. An error in our billing processing system caused incorrect values to be reflected in daily usage and current invoices for customers with cold storage buckets.\n\nOur team identified and corrected an issue with the billing data sync, ensuring accurate usage reporting. If you continue to experience any issues, please open a ticket with our Support team", "breaking_config_code": "# Incident architectural state during Spaces Cold Storage Billing\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Billing\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/qb6zv0kdjy50", "metadata": {"raw_id": "l20hw5cfhksw", "status": "resolved", "resolved_at": "2026-08-04T21:42:43.197Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-3nt69xj3", "company": "DigitalOcean", "date": "2026-08-03", "title": "Cloud Control Panel Access", "severity": "MEDIUM", "service_stack": ["Cloud Control Panel", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-08-03 17:59:42 UTC] DigitalOcean SRE (Resolved): Between 09:36 and 13:30 UTC on August 3, some customers experienced intermittent errors while accessing the DigitalOcean Cloud Control Panel. We renewed the affected internal certificates and restored access. The issue is resolved, and the Cloud Control Panel is operating normally. We apologize for the disruption.\n[2026-08-03 16:39:40 UTC] DigitalOcean SRE (Monitoring): We have implemented mitigation for the issue causing some customers to experience intermittent errors when accessing the DigitalOcean Cloud Control Panel. We are seeing recovery and are monitoring the service closely. We will provide another update once we have confirmed the issue is fully resolved\n[2026-08-03 13:58:04 UTC] DigitalOcean SRE (Investigating): Beginning at 09:36 UTC on August 3, some customers may experience intermittent errors when accessing the DigitalOcean Cloud Control Panel, including an \"mTLS verification failed\" message. Our engineering team is actively investigating. \n\nWe apologise for the inconvenience this may have caused. We will provide another update as soon as more information is available.\n\nIf you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between 09:36 and 13:30 UTC on August 3, some customers experienced intermittent errors while accessing the DigitalOcean Cloud Control Panel. We renewed the affected internal certificates and restored access. The issue is resolved, and the Cloud Control Panel is operating normally. We apologize for the disruption. We have implemented mitigation for the issue causing some customers to experience intermittent errors when accessing the DigitalOcean ", "breaking_config_code": "# Incident architectural state during Cloud Control Panel Access\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Cloud Control Panel\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloud Control Panel cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/045lx5xqfdns", "metadata": {"raw_id": "3nt69xj3wkk9", "status": "resolved", "resolved_at": "2026-08-03T17:59:42.943Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-rdfp2h4s", "company": "DigitalOcean", "date": "2026-07-29", "title": "Response Degradation Impacting Kimi-K3", "severity": "MEDIUM", "service_stack": ["Model Services", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["DATABASE_DEGRADATION"], "symptom_logs": "[2026-07-30 06:15:55 UTC] DigitalOcean SRE (Resolved): Our Engineering team has resolved the issue causing empty or broken responses from Kimi-K3. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.\n[2026-07-29 21:41:12 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating reports of empty or broken responses impacting Kimi-K3.\nAt this point, users may experience degraded response quality, specifically empty or broken outputs (including repeated characters), when querying the Kimi-K3 service.\nWe apologize for the inconvenience and will share an update once we have more information.\n[2026-07-29 17:56:51 UTC] DigitalOcean SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has resolved the issue causing empty or broken responses from Kimi-K3. If you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused. Our Engineering team is investigating reports of empty or broken responses impacting Kimi-K3.\nAt this point, users may experience degraded response quality, specifically empty or broken outputs (including repeated", "breaking_config_code": "# Incident architectural state during Response Degradation Impacting Kimi-K3\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Model Services\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Model Services cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ynhlvpy6ctcm", "metadata": {"raw_id": "rdfp2h4syxz8", "status": "resolved", "resolved_at": "2026-07-30T06:15:55.395Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-fcfplv03", "company": "DigitalOcean", "date": "2026-07-27", "title": "Agent Platform Requests Returning HTTP 500 Errors", "severity": "HIGH", "service_stack": ["Agent Runtime", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-07-28 15:24:28 UTC] DigitalOcean SRE (Resolved): This incident has been resolved.\n[2026-07-27 19:44:00 UTC] DigitalOcean SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-07-27 18:31:40 UTC] DigitalOcean SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: This incident has been resolved. The issue has been identified and a fix is being implemented. We are currently investigating this issue.", "breaking_config_code": "# Incident architectural state during Agent Platform Requests Returning HTTP 500 Errors\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Agent Runtime\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Agent Runtime cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/54mh0lzk9733", "metadata": {"raw_id": "fcfplv03vbwt", "status": "resolved", "resolved_at": "2026-07-28T15:24:28.800Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-w53965sh", "company": "DigitalOcean", "date": "2026-07-24", "title": "Network Connectivity from India to NYC", "severity": "MEDIUM", "service_stack": ["NYC1", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-07-24 12:42:25 UTC] DigitalOcean SRE (Resolved): Between 07:46  UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP.\n\nOur investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources.\n\nWe apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further.\n[2026-07-24 11:45:42 UTC] DigitalOcean SRE (Monitoring): We are observing improvements in network connectivity for users in India accessing resources in our NYC region. Our team is monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.\n[2026-07-24 10:36:52 UTC] DigitalOcean SRE (Identified): We have noticed ​​​​​​​network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between 07:46  UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP.\n\nOur investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing t", "breaking_config_code": "# Incident architectural state during Network Connectivity from India to NYC\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"NYC1\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on NYC1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/y9g7qgc9qs6m", "metadata": {"raw_id": "w53965shllfq", "status": "resolved", "resolved_at": "2026-07-24T12:42:25.955Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-ym1lj8ww", "company": "DigitalOcean", "date": "2026-07-23", "title": "Llama-4-Maverick Model Availability", "severity": "MEDIUM", "service_stack": ["Inference", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-07-23 12:37:00 UTC] DigitalOcean SRE (Resolved): This incident has been resolved.\n[2026-07-23 11:16:59 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an issue where the llama-4-maverick model is unavailable. Users may experience HTTP 500 errors while using this model with Serverless Inference.\n\nWe apologize for the inconvenience. Our Engineering team is working with high priority to resolve the issue. Thank you for your patience and understanding.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: This incident has been resolved. Our Engineering team is currently investigating an issue where the llama-4-maverick model is unavailable. Users may experience HTTP 500 errors while using this model with Serverless Inference.\n\nWe apologize for the inconvenience. Our Engineering team is working with high priority to resolve the issue. Thank you for your patience and understanding.", "breaking_config_code": "# Incident architectural state during Llama-4-Maverick Model Availability\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Inference\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Inference cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/9pxmkrlffl58", "metadata": {"raw_id": "ym1lj8ww7cpz", "status": "resolved", "resolved_at": "2026-07-23T12:37:00.025Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-j6cjljph", "company": "DigitalOcean", "date": "2026-07-22", "title": "Gradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17b", "severity": "MEDIUM", "service_stack": ["Inference", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-22 19:42:17 UTC] DigitalOcean SRE (Resolved): This incident has been resolved.\n[2026-07-22 16:50:42 UTC] DigitalOcean SRE (Investigating): We are currently investigating this issue.", "root_cause_analysis": "Engineering telemetry at DigitalOcean detected service interruption across Inference, Droplets Hypervisor, DOKS Kubernetes, Block Storage. The incident resulted from capacity saturation and upstream dependency latency. Engineers identified degraded nodes and isolated traffic to restore nominal operations.", "breaking_config_code": "# Incident architectural state during Gradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17b\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Inference\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Inference cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/2fdnm4tns3f1", "metadata": {"raw_id": "j6cjljphvgq7", "status": "resolved", "resolved_at": "2026-07-22T19:42:17.085Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-84v7d9gk", "company": "DigitalOcean", "date": "2026-07-19", "title": "Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1", "severity": "MEDIUM", "service_stack": ["BLR1", "NYC1", "NYC3", "SGP1"], "categories": ["STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-07-19 15:32:39 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.\n[2026-07-19 14:52:16 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has identified the root cause of the issue preventing volume attachments to Droplets in NYC1, NYC3, SGP1, SYD1, and BLR1 and has successfully implemented a fix. You should now be able to attach volumes to your Droplet(s) without encountering any further errors or issues.\n\nWe are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.\n[2026-07-19 13:36:11 UTC] DigitalOcean SRE (Investigating): We are continuing to investigate this issue.\n[2026-07-19 13:34:53 UTC] DigitalOcean SRE (Investigating): We are continuing to investigate this issue.\n[2026-07-19 09:51:19 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1, NYC3, SGP1, SYD1 and BLR1 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the issue regarding volume attachment to Droplets in the NYC1, NYC3, SGP1, SYD1, and BLR1 regions has been fully resolved, and all services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused. Our Engineering team has identified the root cause of the issue preventing volume attachments to Drople", "breaking_config_code": "# Incident architectural state during Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"BLR1\", \"NYC1\", \"NYC3\", \"SGP1\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on BLR1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/wv68wmnz55ln", "metadata": {"raw_id": "84v7d9gkkzzf", "status": "resolved", "resolved_at": "2026-07-19T15:32:39.578Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-qzbsmdsw", "company": "DigitalOcean", "date": "2026-07-19", "title": "Networking in BLR1", "severity": "MEDIUM", "service_stack": ["BLR1", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-07-19 09:52:00 UTC] DigitalOcean SRE (Resolved): Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.\n[2026-07-19 09:31:03 UTC] DigitalOcean SRE (Monitoring): Our engineering team has implemented the necessary fixes affecting upstream network connectivity for Droplet-based services in the BLR1 region. Users should now be able to connect to the external endpoints from Droplets in BLR1.\n\nWe are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.\n[2026-07-19 08:27:36 UTC] DigitalOcean SRE (Identified): Our Engineering team has identified an issue affecting upstream network connectivity for Droplet-based services in the BLR1 region and is actively working with the relevant upstream providers to implement a resolution.\n\nCustomers may continue to experience intermittent timeouts or connectivity issues when attempting to reach external endpoints from Droplets in BLR1.\n\nWe will provide another update once the issue has been fully resolved or when additional information becomes available.\n[2026-07-19 06:57:41 UTC] DigitalOcean SRE (Investigating): We are currently investigating an issue affecting outbound network traffic for Droplets in the BLR1 region. Customers may experience timeout errors or connectivity issues when attempting to reach external services.\nOur Engineering team is actively investigating the issue and working to identify the root cause. We will provide additional updates as soon as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our engineering team has resolved the outbound network connectivity issue in the BLR1 region. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience. Our engineering team has implemented the necessary fixes affecting upstream network connectivity for Droplet-based services in the BLR1 region. Users should now be able to connect to the external endpoints from Droplets in BLR1.\n\nWe are", "breaking_config_code": "# Incident architectural state during Networking in BLR1\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"BLR1\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on BLR1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8yc90q76srsl", "metadata": {"raw_id": "qzbsmdsw9lq8", "status": "resolved", "resolved_at": "2026-07-19T09:52:00.733Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-nfhvp4yh", "company": "DigitalOcean", "date": "2026-07-16", "title": "Reserved IP routing in TOR1", "severity": "MEDIUM", "service_stack": ["Reserved IP", "TOR1", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-07-16 17:24:35 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.\n[2026-07-16 17:01:27 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitoring the results.\n\nInbound and outbound traffic to and from Reserved IPs in TOR1 should now be restored. If you reassigned your Reserved IP as a workaround and are still experiencing issues, please reach out to our support team.\n\nWe will continue to monitor the situation closely and provide a further update once we have confirmed the issue is fully resolved.\n[2026-07-16 15:30:04 UTC] DigitalOcean SRE (Identified): Our Engineering team has identified the cause of the issue affecting Reserved IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.\n\nDetaching and reassigning the Reserved IP to the Droplet may restore connectivity in the meantime. We recommend trying this workaround if you are still experiencing issues with your Reserved IP in TOR1.\n\nOur engineering team is now working on implementing a fix. We will provide updates as more information becomes available.\n[2026-07-16 13:39:47 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.\n\nIn the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1.\n\nOur engineering team is actively investigating the root cause and working towards a resolution. We will provide updates as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused. Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitor", "breaking_config_code": "# Incident architectural state during Reserved IP routing in TOR1\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Reserved IP\", \"TOR1\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Reserved IP cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/x0s0pghvdcgv", "metadata": {"raw_id": "nfhvp4yhyrfl", "status": "resolved", "resolved_at": "2026-07-16T17:24:35.996Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-8sjb7kmq", "company": "DigitalOcean", "date": "2026-07-13", "title": "Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow Responses", "severity": "MEDIUM", "service_stack": ["Inference", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["QUEUE_DELAY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-15 21:46:35 UTC] DigitalOcean SRE (Resolved): The deployed fix has successfully restored full functionality, and our monitoring shows that system performance has completely stabilized. Response times for all Gemma 4 inference workflows have returned to normal baseline levels.\nWe will continue to track platform stability moving forward to ensure long-term reliability. We apologize for any disruption this may have caused to your workflows and appreciate your patience throughout the recovery process.\n[2026-07-15 10:06:19 UTC] DigitalOcean SRE (Monitoring): A fix has been deployed to resolve the issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.\n[2026-07-14 11:07:24 UTC] DigitalOcean SRE (Identified): We are currently experiencing an issue affecting customers using the Gemma 4 model on our Serverless Inference platform. Customers may experience significantly increased latency or request timeouts.\n\nOur Engineering team has identified a backend configuration issue as the root cause, which is temporarily impacting model performance. Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority.\n\nWe sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.\n[2026-07-13 22:24:14 UTC] DigitalOcean SRE (Monitoring): A fix has been deployed to resolve the backend configuration issue. We are closely monitoring system performance to ensure full recovery and normal response times for all Gemma 4 inference workflows.\n[2026-07-13 19:04:10 UTC] DigitalOcean SRE (Identified): We are currently experiencing an issue where customers using the Gemma 4 model on our Serverless Inference and Dedicated Inference platforms may experience severe latency or request timeouts.\nOur engineering team has identified a backend configuration issue as the root cause, which is temporarily degrading performance. We are actively working on a fix to restore normal response times and will provide another update as soon as the mitigation is in place", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: The deployed fix has successfully restored full functionality, and our monitoring shows that system performance has completely stabilized. Response times for all Gemma 4 inference workflows have returned to normal baseline levels.\nWe will continue to track platform stability moving forward to ensure long-term reliability. We apologize for any disruption this may have caused to your workflows and appreciate your patience throughout the recovery pr", "breaking_config_code": "# Incident architectural state during Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow Responses\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Inference\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Inference cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rzs04wclgpfq", "metadata": {"raw_id": "8sjb7kmqnvk9", "status": "resolved", "resolved_at": "2026-07-15T21:46:35.616Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-2kxtxyvz", "company": "DigitalOcean", "date": "2026-07-09", "title": "Kubernetes Deployments in NYC1", "severity": "MEDIUM", "service_stack": ["NYC1", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-07-11 01:27:56 UTC] DigitalOcean SRE (Resolved): The issue affecting Kubernetes deployments in the NYC1 region has been resolved. Our investigation found intermittent DNS timeouts affecting a small number of DOKS clusters, with affected worker nodes running on shared-CPU Droplets. This is a documented limitation for latency-sensitive cluster DNS workloads such as CoreDNS.\n\nThe affected clusters are currently functional. To reduce the risk of recurrence, we recommend running CoreDNS on non-shared/dedicated CPU node pools and using sufficient CoreDNS replicas. \n\nIf you continue to see DNS failures or NodeNotReady events, please open a support ticket so we can investigate that cluster specifically.\n[2026-07-10 01:18:00 UTC] DigitalOcean SRE (Monitoring): The issue affecting Kubernetes deployments in NYC1 has subsided. Workloads should now be functioning normally.\n\nOur Engineering team is continuing to monitor the affected systems to confirm full resolution. We'll update this page if any further action is needed. We apologize for the inconvenience this may have caused.\n[2026-07-09 20:31:52 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue affecting Kubernetes deployments in NYC1. Users may see intermittent DNS failures and NodeNotReady events from application workloads during this time.\n\nWe apologize for the inconvenience, we'll share new information on this page as soon as it is available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: The issue affecting Kubernetes deployments in the NYC1 region has been resolved. Our investigation found intermittent DNS timeouts affecting a small number of DOKS clusters, with affected worker nodes running on shared-CPU Droplets. This is a documented limitation for latency-sensitive cluster DNS workloads such as CoreDNS.\n\nThe affected clusters are currently functional. To reduce the risk of recurrence, we recommend running CoreDNS on non-share", "breaking_config_code": "# Incident architectural state during Kubernetes Deployments in NYC1\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"NYC1\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on NYC1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/p8xctv4k5yjv", "metadata": {"raw_id": "2kxtxyvzzzk0", "status": "resolved", "resolved_at": "2026-07-11T01:27:56.795Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-wvj4t3y9", "company": "DigitalOcean", "date": "2026-07-04", "title": "Limited access to Deepseek V4 Pro model", "severity": "HIGH", "service_stack": ["Inference", "Model Services", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-05 00:53:19 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform has been fully resolved. The model is now operational, and users should be able to use it without experiencing any errors.\n\nIf you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience.\n[2026-07-04 23:18:01 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix for the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform. The model should now be operational, and users should no longer receive error 429 messages when attempting to use it. We are currently monitoring the situation to ensure the fix is successful and the model is functioning as expected. We will post an update if any further issues arise. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.\n[2026-07-04 22:13:45 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating reports of an incident affecting the Deepseek V4 Pro model in Serverless Inference and Agent Platform. Users may experience errors when attempting to use this model, specifically receiving error 429 messages. We apologize for the inconvenience and are working to resolve the issue as soon as possible. We will provide an update once we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the issue with the Deepseek V4 Pro model in Serverless Inference and Agent Platform has been fully resolved. The model is now operational, and users should be able to use it without experiencing any errors.\n\nIf you continue to experience any problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused and appreciate your patience. Our Engineering team has imp", "breaking_config_code": "# Incident architectural state during Limited access to Deepseek V4 Pro model\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Inference\", \"Model Services\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Inference cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/wwsc9zft1lxd", "metadata": {"raw_id": "wvj4t3y98gs7", "status": "resolved", "resolved_at": "2026-07-05T00:53:19.389Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-7vmz1hml", "company": "DigitalOcean", "date": "2026-07-04", "title": "Droplet Actions in NYC3", "severity": "MEDIUM", "service_stack": ["NYC3", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-04 15:10:06 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the issue impacting Droplets in the NYC3 region has been fully resolved. Users can now perform actions on their Droplets or create new Droplets in this region without any issues.\n\nWe appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.\n[2026-07-04 14:42:47 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix to address the issue affecting Droplets in the NYC3 region. The issue, which began at 12:38 UTC, caused disruptions to customers attempting to perform actions on their Droplets in the NYC3 region.\n\nDuring this time, customers may also have experienced errors when trying to create Droplets in this region.\n\nWe are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the issue impacting Droplets in the NYC3 region has been fully resolved. Users can now perform actions on their Droplets or create new Droplets in this region without any issues.\n\nWe appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further. Our Engineering team has implemente", "breaking_config_code": "# Incident architectural state during Droplet Actions in NYC3\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"NYC3\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on NYC3 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/1ggj0xnb3n4v", "metadata": {"raw_id": "7vmz1hmlzzrc", "status": "resolved", "resolved_at": "2026-07-04T15:10:06.071Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-rjfr3rbz", "company": "DigitalOcean", "date": "2026-07-02", "title": "Managed Database Clusters", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION", "API_ERROR_SPIKE"], "symptom_logs": "[2026-07-03 08:20:23 UTC] DigitalOcean SRE (Resolved): Our engineering team has resolved the issue with Managed Database Clusters. All database systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.\n[2026-07-03 06:08:12 UTC] DigitalOcean SRE (Monitoring): Our engineering team has implemented a fix to resolve the issue with Managed Database Clusters and is monitoring the situation. We will post an update as soon as the issue is fully resolved.\n[2026-07-03 02:28:14 UTC] DigitalOcean SRE (Investigating): Our engineering team is still investigating the issue affecting Managed Database Clusters. Users may still encounter delays creating/scaling/forking/restoring the aforementioned Managed Database Clusters. \n\nWe are working to resolve this as soon as possible. we apologize for the inconvenience. We will post an update here once we have more information.\n[2026-07-02 22:04:53 UTC] DigitalOcean SRE (Investigating): Our engineering team is investigating an issue affecting Managed Database Clusters. Currently, users may encounter delays when creating/scaling/forking and restoring Standard MySQL, Standard PostgreSQL, OpenSearch, Kafka, and Valkey clusters through the Cloud Control Panel or API.\n\nWe apologize for the inconvenience and will provide further updates as soon as more information is available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our engineering team has resolved the issue with Managed Database Clusters. All database systems should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience. Our engineering team has implemented a fix to resolve the issue with Managed Database Clusters and is monitoring the situation. We will post an update as soon as the issue is fully resolved. Our engi", "breaking_config_code": "# Incident architectural state during Managed Database Clusters\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rpkck6zr7ht5", "metadata": {"raw_id": "rjfr3rbzxlx1", "status": "resolved", "resolved_at": "2026-07-03T08:20:23.462Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-76l7xym7", "company": "DigitalOcean", "date": "2026-07-01", "title": "Agent Timeouts While Retrieving Data from Knowledge Bases", "severity": "MEDIUM", "service_stack": ["Agent Runtime", "Knowledge Bases", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-07-02 03:38:53 UTC] DigitalOcean SRE (Resolved): This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support.\n[2026-07-01 08:39:50 UTC] DigitalOcean SRE (Identified): Our Engineering team has identified the issue causing Agents to experience timeouts while retrieving data from Knowledge Bases.\n\nPlease be assured that our Engineering team is actively working on a fix and is treating this issue with high priority.\n\nWe sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.\n[2026-07-01 06:25:23 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an issue where Agents are experiencing timeouts while retrieving data from Knowledge Bases. As a result, affected Agents may fail to retrieve data and return the following error:\n\n\"Failed to retrieve data from Knowledge base(s) - timeout\"\n\nPlease be assured that we are treating this as a high-priority issue and are actively working to mitigate it.\n\nWe sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can investigate your specific case further.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: This incident has been resolved, and our teams continue to monitor the results. If you experience any further issues, please contact support. Our Engineering team has identified the issue causing Agents to experience timeouts while retrieving data from Knowledge Bases.\n\nPlease be assured that our Engineering team is actively working on a fix and is treating this issue with high priority.\n\nWe sincerely apologise for any inconvenience this may have", "breaking_config_code": "# Incident architectural state during Agent Timeouts While Retrieving Data from Knowledge Bases\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Agent Runtime\", \"Knowledge Bases\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Agent Runtime cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/sp8b09xxqvjt", "metadata": {"raw_id": "76l7xym7jd5m", "status": "resolved", "resolved_at": "2026-07-02T03:38:53.338Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-phwpbgwc", "company": "DigitalOcean", "date": "2026-07-01", "title": "DNS Lookup Failures for Managed Database", "severity": "MEDIUM", "service_stack": ["FRA1", "DNS", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["DATABASE_DEGRADATION", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-07-01 16:28:25 UTC] DigitalOcean SRE (Resolved): The intermittent DNS lookup failures between Managed Kubernetes and Managed Database hostnames in the FRA1 region have been resolved for now but please let us know if you see the issue again. Connectivity has remained stable, and all systems are operating normally. If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.\n[2026-07-01 12:15:49 UTC] DigitalOcean SRE (Investigating): We are continuing to investigate this issue.\n[2026-07-01 11:35:29 UTC] DigitalOcean SRE (Investigating): As of 06:39 UTC, our Engineering team is investigating reports of intermittent DNS lookup failures for Managed Database hostnames from Managed Kubernetes, primarily affecting connections from Managed Kubernetes to Managed Database hostnames. \n\nAt this point, customers in the FRA1 region may experience intermittent connectivity issues. \n\nWe apologize for the inconvenience and will share an update once we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: The intermittent DNS lookup failures between Managed Kubernetes and Managed Database hostnames in the FRA1 region have been resolved for now but please let us know if you see the issue again. Connectivity has remained stable, and all systems are operating normally. If you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience. We are continuing to invest", "breaking_config_code": "# Incident architectural state during DNS Lookup Failures for Managed Database\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"FRA1\", \"DNS\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on FRA1 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/r6yw4xc720r8", "metadata": {"raw_id": "phwpbgwcmkjn", "status": "resolved", "resolved_at": "2026-07-01T16:28:25.933Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-8mvnl6s4", "company": "DigitalOcean", "date": "2026-07-01", "title": "Droplet Resize", "severity": "MEDIUM", "service_stack": ["Cloud Control Panel", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-07-01 13:28:10 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the issue impacting Droplet resizes using the \"Downscale Anytime\" option has been fully resolved. Users can now resize their Droplets using the \"Downscale Anytime\" option without any issues.\n\nWe appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further.\n[2026-07-01 12:43:33 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has identified the root cause of the issue affecting Droplet resizes using the \"Downscale Anytime\" option and has implemented a fix. Users should now be able to resize their Droplets using the \"Downscale Anytime\" option without experiencing any issues or errors.\n\nWe are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.\n[2026-07-01 11:13:21 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue affecting Droplet resizes using the \"Downscale Anytime\" option. At this time users may find this option unavailable or unresponsive in the Cloud Control Panel.\n\nAs a workaround, resizes can be performed via the API while we work to resolve this issue.\n\nWe apologize for the inconvenience and will share an update once we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the issue impacting Droplet resizes using the \"Downscale Anytime\" option has been fully resolved. Users can now resize their Droplets using the \"Downscale Anytime\" option without any issues.\n\nWe appreciate your patience while we worked to resolve this issue. If you continue to experience any problems, please open a support ticket from your account so our team can investigate further. Our Engineering team ha", "breaking_config_code": "# Incident architectural state during Droplet Resize\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Cloud Control Panel\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloud Control Panel cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/m6y2gmlz3jrv", "metadata": {"raw_id": "8mvnl6s4cmdt", "status": "resolved", "resolved_at": "2026-07-01T13:28:10.841Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-m2shb5ks", "company": "DigitalOcean", "date": "2026-06-27", "title": "Droplet Backup Service", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-27 18:24:25 UTC] DigitalOcean SRE (Resolved): Between 00:00 UTC & 16:00 UTC today, our Engineering team identified an issue affecting backup operations on Droplets.  During this period, backups scheduled within this window may not have been created and may appear as missing.\n\nOur team has taken necessary measures to resolve the issue, and we can confirm that the backup service has been restored and is now functioning normally. Upcoming scheduled backups should be performed as expected.\n\nWe sincerely apologize for any inconvenience this may have caused and appreciate your understanding. However, if you have any further questions or concerns, please create a support ticket for further analysis.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between 00:00 UTC & 16:00 UTC today, our Engineering team identified an issue affecting backup operations on Droplets.  During this period, backups scheduled within this window may not have been created and may appear as missing.\n\nOur team has taken necessary measures to resolve the issue, and we can confirm that the backup service has been restored and is now functioning normally. Upcoming scheduled backups should be performed as expected.\n\nWe s", "breaking_config_code": "# Incident architectural state during Droplet Backup Service\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/djw8kv2yfvcd", "metadata": {"raw_id": "m2shb5ks2rml", "status": "resolved", "resolved_at": "2026-06-27T18:24:25.102Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-psk2b3pg", "company": "DigitalOcean", "date": "2026-06-27", "title": "Anthropic Inference Model Availability", "severity": "MEDIUM", "service_stack": ["Inference", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-27 05:15:38 UTC] DigitalOcean SRE (Resolved): Our Engineering team has resolved the issue that was causing HTTP 400 errors for requests to Anthropic models. Users should now be able to access Anthropic models without any issues.\nIf you continue to experience problems, please open a ticket with our Support team so we can investigate further.\nWe apologize for any inconvenience this may have caused.\n[2026-06-27 04:43:29 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has mitigated an issue with Anthropic models. Previously, users may have encountered 400 errors when attempting to use any Anthropic model.\n\nAlthough the root cause of the issue is still being addressed by Anthropic, users should now be able to access and use Anthropic models again. We will continue to monitor the situation and provide updates if necessary. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has resolved the issue that was causing HTTP 400 errors for requests to Anthropic models. Users should now be able to access Anthropic models without any issues.\nIf you continue to experience problems, please open a ticket with our Support team so we can investigate further.\nWe apologize for any inconvenience this may have caused. Our Engineering team has mitigated an issue with Anthropic models. Previously, users may have en", "breaking_config_code": "# Incident architectural state during Anthropic Inference Model Availability\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Inference\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Inference cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/s2bx05f4wxkb", "metadata": {"raw_id": "psk2b3pgbblq", "status": "resolved", "resolved_at": "2026-06-27T05:15:38.421Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-nqkv7bnz", "company": "DigitalOcean", "date": "2026-06-19", "title": "Monitoring Graphs in the Cloud Control Panel", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["DATABASE_DEGRADATION"], "symptom_logs": "[2026-06-19 16:37:38 UTC] DigitalOcean SRE (Resolved): Between 13:22 & 14:26 UTC today, users have experienced missing monitoring graphs for Droplets (with DO agent installed), Load Balancers, Databases, and other services within the Cloud Control Panel.\n\nOur engineering team has identified the root cause of the issue and has taken appropriate steps to restore functionality. We can confirm that services have been restored and are functioning as expected.\n\nWe apologize for any inconvenience this may have caused. If you continue to experience issues viewing monitoring graphs, please create a support ticket for further analysis. Thank you for your patience and understanding\n[2026-06-19 14:50:38 UTC] DigitalOcean SRE (Monitoring): Our engineering team has implemented the necessary fixes to address the issue affecting the visibility of monitoring graphs within the Cloud Panel. Users should now be able to view monitoring graphs for their services, including Droplets with DO Agent installed, Load Balancers, Databases, etc.\n\nWe are currently monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.\n[2026-06-19 14:00:33 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an issue affecting the visibility of monitoring graphs within the Cloud Panel. During this period, users may notice missing or unavailable monitoring graphs for services such as Droplets(with DO agent installed), Load Balancers, Databases, etc.\n\nWe apologize for the inconvenience caused. We'll update once we have more information", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between 13:22 & 14:26 UTC today, users have experienced missing monitoring graphs for Droplets (with DO agent installed), Load Balancers, Databases, and other services within the Cloud Control Panel.\n\nOur engineering team has identified the root cause of the issue and has taken appropriate steps to restore functionality. We can confirm that services have been restored and are functioning as expected.\n\nWe apologize for any inconvenience this may h", "breaking_config_code": "# Incident architectural state during Monitoring Graphs in the Cloud Control Panel\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/8jy6pdvsszwm", "metadata": {"raw_id": "nqkv7bnzr4l3", "status": "resolved", "resolved_at": "2026-06-19T16:37:38.303Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-bfsh34my", "company": "DigitalOcean", "date": "2026-06-16", "title": "Intermittent 500 Errors on Serverless/GenAI Inference API", "severity": "MEDIUM", "service_stack": ["Inference", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-06-17 00:29:42 UTC] DigitalOcean SRE (Resolved): The connectivity issues affecting our Serverless/GenAI Inference API have been fully resolved.\nOur engineering teams successfully completed the connectivity restoration. All systems should be functioning normally, and the endpoint should be fully operational.\n[2026-06-16 23:29:14 UTC] DigitalOcean SRE (Monitoring): Our engineering teams have successfully begun implementing mitigation steps to resolve the connectivity issues affecting the inference API. We will provide another update once the API has fully recovered and error rates return to normal.\n[2026-06-16 22:52:52 UTC] DigitalOcean SRE (Investigating): We are actively investigating an issue causing elevated HTTP 500 error rates for customers utilizing our Serverless/GenAI Inference API.\nCustomer Impact: Customers making calls to the inference API—specifically targeting /v1/* endpoints—will experience intermittent HTTP 500 errors and failed requests.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: The connectivity issues affecting our Serverless/GenAI Inference API have been fully resolved.\nOur engineering teams successfully completed the connectivity restoration. All systems should be functioning normally, and the endpoint should be fully operational. Our engineering teams have successfully begun implementing mitigation steps to resolve the connectivity issues affecting the inference API. We will provide another update once the API has fu", "breaking_config_code": "# Incident architectural state during Intermittent 500 Errors on Serverless/GenAI Inference API\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Inference\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Inference cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/40ln0gl1x56j", "metadata": {"raw_id": "bfsh34myw3bc", "status": "resolved", "resolved_at": "2026-06-17T00:29:42.280Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-505mwh53", "company": "DigitalOcean", "date": "2026-06-11", "title": "DeepSeek V4 Pro is returning HTTP 429 \"Rate limit exceeded\"", "severity": "HIGH", "service_stack": ["Model Services", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-06-11 17:42:05 UTC] DigitalOcean SRE (Resolved): This incident has been resolved.\n[2026-06-11 14:31:01 UTC] DigitalOcean SRE (Identified): The issue has been identified and a fix is being implemented.\n[2026-06-11 14:30:20 UTC] DigitalOcean SRE (Investigating): We are continuing to investigate this issue.\n[2026-06-11 14:24:20 UTC] DigitalOcean SRE (Investigating): We are currently facing issues with Gradient AI DeepSeek V4 Pro is returning HTTP 429 \"Rate limit exceeded\"", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: This incident has been resolved. The issue has been identified and a fix is being implemented. We are continuing to investigate this issue. We are currently facing issues with Gradient AI DeepSeek V4 Pro is returning HTTP 429 \"Rate limit exceeded\"", "breaking_config_code": "# Incident architectural state during DeepSeek V4 Pro is returning HTTP 429 \"Rate limit exceeded\"\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Model Services\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Model Services cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/r8mzkb94pf9g", "metadata": {"raw_id": "505mwh53nwl2", "status": "resolved", "resolved_at": "2026-06-11T17:42:05.051Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-nnt4rfbg", "company": "DigitalOcean", "date": "2026-06-04", "title": "DNS API Service", "severity": "MEDIUM", "service_stack": ["Global", "DNS", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-06-04 11:47:05 UTC] DigitalOcean SRE (Resolved): Between 09:41 and 11:24 UTC, our Engineering team identified an issue impacting the DNS API service. During this period, users may have experienced issues performing domain and DNS record management operations through the Control Panel and API. Services dependent on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, were also impacted.\n\nOur Engineering team has confirmed that the underlying issue affecting the DNS API service has been fully resolved, and all affected services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.\n[2026-06-04 11:39:16 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue impacting our DNS API service. Users should now be able to perform domain and DNS record management operations successfully through the Control Panel and API. Additionally, services affected by this issue, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, should now be functioning as expected.\n\nWe are monitoring the situation closely and will share an update once the issue is resolved completely.\n[2026-06-04 11:32:22 UTC] DigitalOcean SRE (Identified): Our Engineering team has identified the cause of the issue impacting our DNS API service and is actively working on a fix. During this time, users may experience errors when attempting to create, update, or delete domains and DNS records through the Control Panel and API. As a result, services that depend on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, may also be impacted.\n\nWe will post an update as soon as additional information is available.\n[2026-06-04 10:59:17 UTC] DigitalOcean SRE (Investigating): Our Engineering team continues to investigate an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that depend on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete operations, may also be impacted.\n\nWe apologize for the inconvenience and will share more information as it becomes available.\n[2026-06-04 10:12:10 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that rely on DNS API operations, such as Let's Encrypt certificate provisioning and MongoDB cluster creation, may also be impacted.\n\nWe apologize for the inconvenience and will share an update once we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between 09:41 and 11:24 UTC, our Engineering team identified an issue impacting the DNS API service. During this period, users may have experienced issues performing domain and DNS record management operations through the Control Panel and API. Services dependent on DNS API operations, including Let's Encrypt certificate provisioning, MongoDB cluster creation, App Platform deployments, and DigitalOcean Kubernetes (DOKS) cluster create and delete ", "breaking_config_code": "# Incident architectural state during DNS API Service\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"DNS\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/c9tgc3txntpg", "metadata": {"raw_id": "nnt4rfbgn1y6", "status": "resolved", "resolved_at": "2026-06-04T11:47:05.272Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-y3p9v8vm", "company": "DigitalOcean", "date": "2026-05-29", "title": "App Platform Deployments", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-05-29 07:58:23 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the issue impacting build failures on App Platform has been resolved at 07:00 am UTC. All App Platform builds are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.\n\nIf you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.\n[2026-05-29 01:58:49 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue with build failures on App Platform. Users should see their builds deploy successfully now.\n\nWe are closely monitoring the situation, and will post an update once we've confirmed this is fully resolved.\n[2026-05-29 00:14:19 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an issue with build failures on App Platform in multiple regions. Users may experience errors when attempting to build their applications, resulting in failed deployments.\n\nOur Engineering team is working to fix the issue and will share an update once we have more details.\n\nWe apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the issue impacting build failures on App Platform has been resolved at 07:00 am UTC. All App Platform builds are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.\n\nIf you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any i", "breaking_config_code": "# Incident architectural state during App Platform Deployments\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/c5cpdwx9rc37", "metadata": {"raw_id": "y3p9v8vm4tfn", "status": "resolved", "resolved_at": "2026-05-29T07:58:23.373Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-55wh1mbv", "company": "DigitalOcean", "date": "2026-05-20", "title": "Cloud Firewall", "severity": "MEDIUM", "service_stack": ["Cloud Firewall", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-05-20 13:03:09 UTC] DigitalOcean SRE (Resolved): Between 06:35 UTC & 12:36 UTC today, our engineering team identified an issue impacting the Cloud Firewall. During this period, users might have encountered issues while updating their firewall rules.\n\nOur team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.\n\nWe regret the inconvenience caused and appreciate your patience and understanding. However, if you continue to experience any issues, please create a support ticket for further analysis.\n[2026-05-20 12:43:17 UTC] DigitalOcean SRE (Monitoring): Our engineering team has implemented a fix that affected the Cloud Firewall rules. Users should now be able to update their firewalls successfully.\n\nWe are actively monitoring the situation to ensure overall stability. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.\n[2026-05-20 12:08:27 UTC] DigitalOcean SRE (Identified): Our engineering team identified an issue impacting Cloud Firewall Product. During this time, users may notice HTTP 500 errors when updating firewalls.\n\nWe apologize for the inconvenience and will share an update once more information is available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between 06:35 UTC & 12:36 UTC today, our engineering team identified an issue impacting the Cloud Firewall. During this period, users might have encountered issues while updating their firewall rules.\n\nOur team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.\n\nWe regret the inconvenience caused and appreciate your patience and understanding. However, if you continu", "breaking_config_code": "# Incident architectural state during Cloud Firewall\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Cloud Firewall\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloud Firewall cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/5dzt41b39qvv", "metadata": {"raw_id": "55wh1mbv7vbs", "status": "resolved", "resolved_at": "2026-05-20T13:03:09.605Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-sv0tfb6j", "company": "DigitalOcean", "date": "2026-05-20", "title": "Cloud Firewall", "severity": "MEDIUM", "service_stack": ["Cloud Firewall", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-05-20 07:48:14 UTC] DigitalOcean SRE (Resolved): Our Engineering team has verified that the issue causing incorrect Cloud Firewall rules to display on the cloud panel is fully resolved. The user interface continues to function as expected, and all systems have returned to normal operating conditions.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident.\n[2026-05-20 07:15:10 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix to resolve the issue causing incorrect Cloud Firewall rules to display on the cloud panel. At this time, the user interface is functioning as expected, and we are actively monitoring the situation to ensure continued stability.\n\nWe will provide a final update once we have verified that the issue is fully resolved.\n[2026-05-20 05:35:48 UTC] DigitalOcean SRE (Investigating): We are currently investigating an issue with incorrect Cloud Firewall rules appearing on the cloud panel. Our engineering team is aware of the situation and actively working to identify the root cause. Since this is a user interface issue, users should not experience any problems with other services or networking.\n\nWe apologize for the inconvenience and appreciate your patience. We will continue to provide updates as we learn more.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has verified that the issue causing incorrect Cloud Firewall rules to display on the cloud panel is fully resolved. The user interface continues to function as expected, and all systems have returned to normal operating conditions.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident. Our Engineering team has implemented a fix to resolve the ", "breaking_config_code": "# Incident architectural state during Cloud Firewall\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Cloud Firewall\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloud Firewall cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/6y9xmwmgkyy4", "metadata": {"raw_id": "sv0tfb6jhqz8", "status": "resolved", "resolved_at": "2026-05-20T07:48:14.980Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-spgd2scv", "company": "DigitalOcean", "date": "2026-05-20", "title": "Block Storage Volume Performance", "severity": "MEDIUM", "service_stack": ["NYC3", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["STORAGE_SUBSYSTEM"], "symptom_logs": "[2026-05-20 05:13:50 UTC] DigitalOcean SRE (Resolved): From 00:00 UTC to 01:40 UTC, users may have experienced degraded write performance and intermittent impacts to workloads dependent on Block Storage Volumes in the NYC3 region.\n\nOur Engineering team has confirmed that the underlying infrastructure issue affecting Block Storage Volumes at the storage layer has been fully resolved, and services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.\n[2026-05-20 02:19:45 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented mitigation measures for the infrastructure issue affecting Block Storage Volumes in the NYC3 region. The team is monitoring the situation, and we will share another update once the issue is fully resolved\n[2026-05-20 01:05:16 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an ongoing infrastructure issue in the NYC3 region affecting Block Storage Volumes at the storage layer. Users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure.\n\nWe apologize for the inconvenience and will continue to provide updates as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: From 00:00 UTC to 01:40 UTC, users may have experienced degraded write performance and intermittent impacts to workloads dependent on Block Storage Volumes in the NYC3 region.\n\nOur Engineering team has confirmed that the underlying infrastructure issue affecting Block Storage Volumes at the storage layer has been fully resolved, and services are now operating normally.\n\nIf you continue to experience any issues, please contact our Support team by ", "breaking_config_code": "# Incident architectural state during Block Storage Volume Performance\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"NYC3\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on NYC3 cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/1cr62wpw64kx", "metadata": {"raw_id": "spgd2scvttth", "status": "resolved", "resolved_at": "2026-05-20T05:13:50.000Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-lrrw084g", "company": "DigitalOcean", "date": "2026-05-15", "title": "Anthropic reported outage that's impacting access to their Serverless Inference models", "severity": "HIGH", "service_stack": ["Agent Runtime", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-05-15 02:00:39 UTC] DigitalOcean SRE (Resolved): As of the current time, our Engineering team has confirmed that the issue with Serverless Inference has been resolved. The root cause of the issue was an outage with our provider, Anthropic, which affected users of Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have resolved the outage. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.\n[2026-05-15 01:23:56 UTC] DigitalOcean SRE (Identified): According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have identified the root cause and are actively working on a fix. At this time, users may continue to experience errors when attempting to use Sonnet 4.6 and Opus 4.7 models. We will provide another update once Anthropic has implemented a fix and service is restored.\n[2026-05-15 01:21:51 UTC] DigitalOcean SRE (Monitoring): As of the current time, our Engineering team is aware of an ongoing incident with our provider, Anthropic, that is impacting Serverless Inference. The outage is affecting all users attempting to use Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they are currently experiencing an outage that is causing this disruption. We apologize for the inconvenience and will provide updates as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: As of the current time, our Engineering team has confirmed that the issue with Serverless Inference has been resolved. The root cause of the issue was an outage with our provider, Anthropic, which affected users of Sonnet 4.6 and Opus 4.7 models. According to Anthropic's status page (https://status.claude.com/incidents/8z7l5zcy0v3b), they have resolved the outage. If you continue to experience problems, please open a ticket with our Support team.", "breaking_config_code": "# Incident architectural state during Anthropic reported outage that's impacting access to their Serverless Inference models\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Agent Runtime\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Agent Runtime cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/d47rft5t1t68", "metadata": {"raw_id": "lrrw084g3whn", "status": "resolved", "resolved_at": "2026-05-15T02:00:39.064Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-gwgh41d5", "company": "DigitalOcean", "date": "2026-05-14", "title": "DNS service, Certificates and Managed MongoDB", "severity": "MEDIUM", "service_stack": ["Global", "DNS", "Droplets Hypervisor", "DOKS Kubernetes"], "categories": ["QUEUE_DELAY", "NETWORK_CONNECTIVITY"], "symptom_logs": "[2026-05-14 20:46:40 UTC] DigitalOcean SRE (Resolved): As of 19:50 UTC, the issue affecting the DNS service has been fully resolved, and all related services, including Let's Encrypt certificate issuance and Managed MongoDB provisioning, are now operating normally.\n\nThe backlog of delayed requests has been successfully processed, and all DNS record updates, pending certificate, and MongoDB operations should now be complete. \n\nWe apologize for the disruption this caused and appreciate your patience while our team worked to restore full functionality.\n\nHowever, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.\n[2026-05-14 16:42:45 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix for the issue affecting our DNS service and are now seeing DNS record updates successfully propagate to the edge.\n\nAs a result, Let's Encrypt certificate issuance and Managed MongoDB provisioning (including scaling operations) should resume. We are currently monitoring the systems as they process the backlog of delayed requests. Affected MongoDB clusters and certificate requests should complete their provisioning automatically.\n\nWe will continue to monitor the situation closely to ensure full stability. We appreciate your patience throughout this process and will provide an update once the issue is fully confirmed as resolved.\n[2026-05-14 15:52:48 UTC] DigitalOcean SRE (Investigating): Our engineering team continues to investigate an issue affecting our DNS service. At this time, DNS resolution remains functional; however, new changes to DNS records are currently not being reflected at the edge.\n\nThis issue is also impacting related services. Specifically, customers may be unable to create new Let's Encrypt certificates. Regarding Managed MongoDB, customers will be able to submit requests to create new clusters or scale existing ones, but the completion of the provisioning process is currently delayed. This is due to the dependency on Let's Encrypt certificate issuance, which requires functional DNS propagation.\n\nAffected clusters will automatically recover and complete their provisioning once the DNS issue is resolved. Our engineering team is actively working to restore full functionality across all affected services.\n\nWe apologize for the inconvenience and will share more information as it becomes available.\n[2026-05-14 13:57:38 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue affecting our DNS service. At this time, DNS resolution remains functional but any changes to DNS records are not being reflected at the edge. Additionally, customers may be unable to create new Let's Encrypt certificates at this time. Our engineering team is actively working to identify the root cause and restore full functionality.\n\nWe apologize for any inconvenience, and we'll share more information as it becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: As of 19:50 UTC, the issue affecting the DNS service has been fully resolved, and all related services, including Let's Encrypt certificate issuance and Managed MongoDB provisioning, are now operating normally.\n\nThe backlog of delayed requests has been successfully processed, and all DNS record updates, pending certificate, and MongoDB operations should now be complete. \n\nWe apologize for the disruption this caused and appreciate your patience wh", "breaking_config_code": "# Incident architectural state during DNS service, Certificates and Managed MongoDB\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"DNS\", \"Droplets Hypervisor\", \"DOKS Kubernetes\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/r6dtr7gc9pch", "metadata": {"raw_id": "gwgh41d5r0nz", "status": "resolved", "resolved_at": "2026-05-14T20:46:40.334Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-bnq93nhg", "company": "DigitalOcean", "date": "2026-05-12", "title": "GradientAI: Agent Platform Playground Interaction Errors", "severity": "HIGH", "service_stack": ["Agent Runtime", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-05-12 11:37:12 UTC] DigitalOcean SRE (Resolved): The remediation for the issue affecting the GradientAI Agent Platform Playground has been fully implemented, and the service is operating normally. We are no longer observing customer impact related to this issue, and the incident has been resolved.\n[2026-05-12 11:36:13 UTC] DigitalOcean SRE (Monitoring): We have applied a fix for the issue affecting the GradientAI Agent Platform Playground and are monitoring the service to ensure continued stability. At this time, we are no longer observing new reports related to this issue.\n[2026-05-12 11:14:45 UTC] DigitalOcean SRE (Identified): A fix has been applied for the issue affecting the GradientAI Agent Platform Playground, and we are observing recovery in service behavior.\n[2026-05-12 10:50:10 UTC] DigitalOcean SRE (Identified): We have identified the cause of the issue affecting the GradientAI Agent Platform Playground. Our engineering team is implementing a fix, and we will provide another update as soon as it is available.\n[2026-05-12 10:24:07 UTC] DigitalOcean SRE (Investigating): We are currently investigating an issue affecting the GradientAI Agent Platform Playground. Users may see a “Something went wrong” error for all agent interactions in the Playground. Agent functionality through API endpoints remains unaffected. We are actively working to identify the cause and will provide an update as soon as more information is available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: The remediation for the issue affecting the GradientAI Agent Platform Playground has been fully implemented, and the service is operating normally. We are no longer observing customer impact related to this issue, and the incident has been resolved. We have applied a fix for the issue affecting the GradientAI Agent Platform Playground and are monitoring the service to ensure continued stability. At this time, we are no longer observing new report", "breaking_config_code": "# Incident architectural state during GradientAI: Agent Platform Playground Interaction Errors\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Agent Runtime\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Agent Runtime cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/ll1m0fw2m4g9", "metadata": {"raw_id": "bnq93nhgvtm6", "status": "resolved", "resolved_at": "2026-05-12T11:37:12.000Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-7hb39w1w", "company": "DigitalOcean", "date": "2026-05-09", "title": "Control Panel Errors - Unable to Enable 2FA and Google/GitHub", "severity": "MEDIUM", "service_stack": ["Cloud Control Panel", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["AUTHENTICATION_FAILURE"], "symptom_logs": "[2026-05-09 14:42:15 UTC] DigitalOcean SRE (Resolved): Between 5:35 and 14:25 UTC today, our Engineering team identified an issue that prevents enabling Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this period, users might have encountered issues while enabling authentication methods and accessing teams with secure sign-in enabled.\n\nOur team has taken appropriate measures to address the issue. We can confirm that service has been restored and is now functioning normally.\n\nWe regret the inconvenience caused. However, if you continue to experience any issues, please create a support ticket for further analysis.\n[2026-05-09 13:51:39 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented necessary changes to address the issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. Our team is currently monitoring the situation to ensure stability.\n\nWe appreciate your patience and will provide an update once the issue is fully confirmed as resolved.\n[2026-05-09 11:15:11 UTC] DigitalOcean SRE (Investigating): Our Engineering team is investigating an issue affecting the ability to enable Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this time, users may encounter errors while enabling these authentication methods and could also experience issues accessing teams with secure sign-in enabled.\n\nWe apologize for the inconvenience and will provide an update as soon as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Between 5:35 and 14:25 UTC today, our Engineering team identified an issue that prevents enabling Two-Factor Authentication (2FA) and Google/GitHub authentication through the Control Panel. During this period, users might have encountered issues while enabling authentication methods and accessing teams with secure sign-in enabled.\n\nOur team has taken appropriate measures to address the issue. We can confirm that service has been restored and is n", "breaking_config_code": "# Incident architectural state during Control Panel Errors - Unable to Enable 2FA and Google/GitHub\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Cloud Control Panel\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Cloud Control Panel cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/tyb995vv9ykq", "metadata": {"raw_id": "7hb39w1wzmwf", "status": "resolved", "resolved_at": "2026-05-09T14:42:15.691Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-p3zyn7c4", "company": "DigitalOcean", "date": "2026-05-08", "title": "Let's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["QUEUE_DELAY", "DATABASE_DEGRADATION"], "symptom_logs": "[2026-05-08 21:54:44 UTC] DigitalOcean SRE (Resolved): The upstream outage with Let's Encrypt has been resolved. Customers should now be able to issue Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains. Our Engineering team has also confirmed that stuck or delayed actions with Mongo, Advanced PG, and Advanced MySQL databases should complete normally now. \n\nWe appreciate your patience. If you continue to experience any issues, please open a support ticket from within your account.\n[2026-05-08 20:46:22 UTC] DigitalOcean SRE (Identified): Our Engineering team is aware of an upstream outage with Let's Encrypt (see https://letsencrypt.status.io/) which impacts the following services: \n\n- Inability to create new Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains\n- Stuck or delayed creates/forks/restores on Mongo, PG, and MySQL databases. \n\nPlease note that operations related to Managed Databases and App Platform Custom Domains will automatically retry and should complete successfully once the upstream outage is resolved. \n\nWe'll continue to monitor this situation and provide updates. We apologize for the inconvenience.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: The upstream outage with Let's Encrypt has been resolved. Customers should now be able to issue Let's Encrypt certificates for Spaces, Load Balancers, and App Platform Custom Domains. Our Engineering team has also confirmed that stuck or delayed actions with Mongo, Advanced PG, and Advanced MySQL databases should complete normally now. \n\nWe appreciate your patience. If you continue to experience any issues, please open a support ticket from withi", "breaking_config_code": "# Incident architectural state during Let's Encrypt Outage Affecting Certificate Issuance and Managed Databases Operations\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/rw9m9n69q6tg", "metadata": {"raw_id": "p3zyn7c4jyx7", "status": "resolved", "resolved_at": "2026-05-08T21:54:44.593Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-h9t3sfjx", "company": "DigitalOcean", "date": "2026-05-08", "title": "Multiple Services in NYC2", "severity": "MEDIUM", "service_stack": ["API", "New York", "NYC2", "Droplets Hypervisor"], "categories": ["NETWORK_CONNECTIVITY", "API_ERROR_SPIKE"], "symptom_logs": "[2026-05-08 19:59:48 UTC] DigitalOcean SRE (Resolved): Our engineering team has resolved the issue with multiple services in NYC2 region, and all services should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and thank you for your patience.\n[2026-05-08 19:53:53 UTC] DigitalOcean SRE (Monitoring): We are continuing to monitor for any further issues.\n[2026-05-08 19:21:31 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has identified the issue and implemented a fix to resolve the issues with multiple services, and is monitoring the situation. We will post an update as soon as the issue is fully resolved.\n[2026-05-08 18:01:42 UTC] DigitalOcean SRE (Investigating): We are currently investigating an issue affecting multiple services in our NYC2 region. Our engineering team is aware of the situation and is working to identify the root cause and restore full connectivity as quickly as possible.\n\nUsers with resources in the NYC2 region may experience issues with Droplet connectivity, API requests, or other services.\n\nWe will provide additional updates as more information becomes available. We apologize for any inconvenience this may cause.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our engineering team has resolved the issue with multiple services in NYC2 region, and all services should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience and thank you for your patience. We are continuing to monitor for any further issues. Our Engineering team has identified the issue and implemented a fix to resolve the issues with multiple service", "breaking_config_code": "# Incident architectural state during Multiple Services in NYC2\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"API\", \"New York\", \"NYC2\", \"Droplets Hypervisor\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on API cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/tb7f2ntnj8hm", "metadata": {"raw_id": "h9t3sfjx36l3", "status": "resolved", "resolved_at": "2026-05-08T19:59:48.942Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-z5fjzx3k", "company": "DigitalOcean", "date": "2026-04-28", "title": "Elevated 5xx “context canceled” errors impacting serverless inference", "severity": "MEDIUM", "service_stack": ["Agent Runtime", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["QUEUE_DELAY"], "symptom_logs": "[2026-04-28 19:33:38 UTC] DigitalOcean SRE (Resolved): All services are operating normally. We will continue to monitor the system to ensure ongoing reliability.\n\nThank you for your patience while we worked to resolve this issue.\n[2026-04-28 19:00:24 UTC] DigitalOcean SRE (Monitoring): Service for Serverless Inference has been restored.\nWe’ve implemented tighter rate limits to help prevent recurrence and are closely monitoring system performance. Some users may still experience intermittent latency as we complete final stabilization efforts.\nOur team remains actively engaged to ensure full recovery. We appreciate your patience and will provide further updates as needed.\n[2026-04-28 15:59:26 UTC] DigitalOcean SRE (Identified): We have identified an issue affecting our service and are currently working to implement a fix. Our team is actively investigating and taking the necessary steps to restore normal operations as quickly as possible.\n\nWe appreciate your patience and will provide updates as soon as more information becomes available.\n[2026-04-28 13:45:20 UTC] DigitalOcean SRE (Investigating): Serverless inference customers are experiencing elevated 5xx errors, including “context canceled” responses. This may result in intermittent request failures. Our team is actively investigating and will provide updates as more information becomes available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: All services are operating normally. We will continue to monitor the system to ensure ongoing reliability.\n\nThank you for your patience while we worked to resolve this issue. Service for Serverless Inference has been restored.\nWe’ve implemented tighter rate limits to help prevent recurrence and are closely monitoring system performance. Some users may still experience intermittent latency as we complete final stabilization efforts.\nOur team remai", "breaking_config_code": "# Incident architectural state during Elevated 5xx “context canceled” errors impacting serverless inference\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Agent Runtime\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Agent Runtime cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/qf13crcjzkmn", "metadata": {"raw_id": "z5fjzx3kp16z", "status": "resolved", "resolved_at": "2026-04-28T19:33:38.769Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-5gsk0hfc", "company": "DigitalOcean", "date": "2026-04-27", "title": "Serverless Inference - Intermittent Rate Limiting Affecting Some Customers Using Anthropic Models", "severity": "HIGH", "service_stack": ["Agent Runtime", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-04-27 11:37:36 UTC] DigitalOcean SRE (Resolved): The issue is resolved, and service is operating normally.\n[2026-04-27 11:07:50 UTC] DigitalOcean SRE (Monitoring): We identified the cause of intermittent HTTP 429 responses affecting some customers using Anthropic models on DigitalOcean Serverless Inference and applied a mitigation. Service has recovered, and we are monitoring stability.\n[2026-04-27 10:38:30 UTC] DigitalOcean SRE (Investigating): We are investigating an issue affecting some customers using DigitalOcean Serverless Inference with Anthropic models. Over the last two hours, impacted customers may have experienced intermittent request failures, including HTTP 429 responses, on some Anthropic model requests. Our engineering team is actively investigating the issue. We apologize for the inconvenience and will share another update as soon as more information is available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: The issue is resolved, and service is operating normally. We identified the cause of intermittent HTTP 429 responses affecting some customers using Anthropic models on DigitalOcean Serverless Inference and applied a mitigation. Service has recovered, and we are monitoring stability. We are investigating an issue affecting some customers using DigitalOcean Serverless Inference with Anthropic models. Over the last two hours, impacted customers may ", "breaking_config_code": "# Incident architectural state during Serverless Inference - Intermittent Rate Limiting Affecting Some Customers Using Anthropic Models\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Agent Runtime\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Agent Runtime cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/y8cgtdqrkct1", "metadata": {"raw_id": "5gsk0hfctqp5", "status": "resolved", "resolved_at": "2026-04-27T11:37:36.467Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-1y9gxbdc", "company": "DigitalOcean", "date": "2026-04-23", "title": "Intermittent errors impacting some Serverless Inference models in ATL1", "severity": "MEDIUM", "service_stack": ["Agent Runtime", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["INFRASTRUCTURE_DEGRADATION", "SERVICE_OUTAGE"], "symptom_logs": "[2026-04-23 23:51:58 UTC] DigitalOcean SRE (Resolved): This incident has been resolved.\n[2026-04-23 22:26:34 UTC] DigitalOcean SRE (Investigating): As of 21:53 UTC, our Engineering team is investigating reports of increased internal errors for models Llama 3.3 70B, GPT OSS 120B, GPT OSS 20B, Qwen3 32B and Deepseek R1 70B hosted in the ATL1 region, impacting Serverless Inference. At this point, users with models hosted in ATL1 may experience intermittent errors when using Serverless Inference. We apologize for the inconvenience and will share an update once we have more information.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: This incident has been resolved. As of 21:53 UTC, our Engineering team is investigating reports of increased internal errors for models Llama 3.3 70B, GPT OSS 120B, GPT OSS 20B, Qwen3 32B and Deepseek R1 70B hosted in the ATL1 region, impacting Serverless Inference. At this point, users with models hosted in ATL1 may experience intermittent errors when using Serverless Inference. We apologize for the inconvenience and will share an update once we", "breaking_config_code": "# Incident architectural state during Intermittent errors impacting some Serverless Inference models in ATL1\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Agent Runtime\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Agent Runtime cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/z4pxt0jh8n97", "metadata": {"raw_id": "1y9gxbdcqb71", "status": "resolved", "resolved_at": "2026-04-23T23:51:58.178Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-2rby4tk1", "company": "DigitalOcean", "date": "2026-04-23", "title": "App Platform Deployments", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["NETWORK_CONNECTIVITY", "PIPELINE_EXECUTION_FAILURE"], "symptom_logs": "[2026-04-23 10:09:54 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed that the issue impacting App Platform deployments and Kubernetes (DOKS) nodes has been fully resolved at 09:22 UTC. Users may already notice improvements while deploying apps and DOKS nodes.\n\nAll App Platform deployments are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.\n\nIf you continue to experience any problems, please open a ticket with our support team. Thank you for your patience, and we apologize for any inconvenience.\n[2026-04-23 09:52:00 UTC] DigitalOcean SRE (Monitoring): Our Engineering team has implemented a fix to address the issue causing in App Platform deployments and Kubernetes (DOKS) nodes. We are actively monitoring the situation to ensure overall stability.\nUsers may already notice improvements while deploying apps and DOKS nodes. We appreciate your patience throughout the process and will provide a further update once the issue is fully confirmed to be resolved.\n[2026-04-23 08:31:00 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating reports of build failures on App Platform. During this time, some users may encounter errors while building their applications, which may result in failed deployments.\nIn addition, we are observing an issue where Kubernetes (DOKS) nodes are being marked as unhealthy by load balancers, which may impact traffic routing for affected services.\nOur Engineering team is actively working to resolve these issues and will share an update as soon as more information becomes available.\nWe apologize for the inconvenience this may be causing and appreciate your patience.\n[2026-04-23 08:08:37 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating reports of build failures on App Platform. Users may experience errors when attempting to build their applications, resulting in failed deployments.\n\nOur Engineering team is working to fix the issue and will share an update once we have more information. \n\nWe apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed that the issue impacting App Platform deployments and Kubernetes (DOKS) nodes has been fully resolved at 09:22 UTC. Users may already notice improvements while deploying apps and DOKS nodes.\n\nAll App Platform deployments are now succeeding as expected. Customers who previously encountered build failures should now be able to deploy their applications without further issues.\n\nIf you continue to experience any pro", "breaking_config_code": "# Incident architectural state during App Platform Deployments\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/0rby3knkk6s1", "metadata": {"raw_id": "2rby4tk1q6mm", "status": "resolved", "resolved_at": "2026-04-23T10:09:54.770Z"}}
{"incident_id": "INC-2026-DIGITALOCEAN-p1jbzg2b", "company": "DigitalOcean", "date": "2026-04-23", "title": "Cloud UI for Managed Kubernetes", "severity": "MEDIUM", "service_stack": ["Global", "Droplets Hypervisor", "DOKS Kubernetes", "Block Storage"], "categories": ["API_ERROR_SPIKE"], "symptom_logs": "[2026-04-23 08:46:39 UTC] DigitalOcean SRE (Resolved): Our Engineering team has confirmed full resolution of the issue with Cloud UI for Managed Kubernetes at 09:19 UTC.\n\nAll the services should be functioning as expected.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident!\n[2026-04-23 07:52:05 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an issue impacting the Managed Kubernetes UI across all regions. During this time, users with a Member role may experience the Kubernetes UI page not loading in the cloud console.\nAs a workaround, the DigitalOcean API and doctl (CLI) continue to function normally, and you can use them to manage your Kubernetes resources in the meantime.\nWe apologize for the inconvenience and will share more information as soon as it becomes available\n[2026-04-23 07:14:44 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an issue impacting the Create Managed Kubernetes UI across all regions. During this time, users with a Member role may experience the Kubernetes UI page not loading in the cloud console.\nAs a workaround, the DigitalOcean API and doctl (CLI) continue to function normally, and you can use them to manage your Kubernetes resources in the meantime.\nWe apologize for the inconvenience and will share more information as soon as it becomes available.\n[2026-04-23 07:01:46 UTC] DigitalOcean SRE (Investigating): Our Engineering team is currently investigating an issue impacting Managed Kubernetes UI across all regions. During this time, some users may experience the Kubernetes UI page not loading in DigitalOcean Onboarding.\n\nWe apologize for the inconvenience and will share more information as soon as it's available.", "root_cause_analysis": "Official investigation timeline recorded by DigitalOcean engineering: Our Engineering team has confirmed full resolution of the issue with Cloud UI for Managed Kubernetes at 09:19 UTC.\n\nAll the services should be functioning as expected.\n\nIf you continue to experience problems, please open a ticket with our support team. Thank you for your patience throughout this incident! Our Engineering team is currently investigating an issue impacting the Managed Kubernetes UI across all regions. During this time, users with a", "breaking_config_code": "# Incident architectural state during Cloud UI for Managed Kubernetes\nservice_cluster:\n  provider: \"DigitalOcean\"\n  impacted_components: [\"Global\", \"Droplets Hypervisor\", \"DOKS Kubernetes\", \"Block Storage\"]\n  health_check_status: DEGRADED\n  circuit_breaker: OPEN\n  observed_error_threshold: 0.05", "remediation_patch": "# Remediation mitigation applied by DigitalOcean SRE\ndeployment_mitigation:\n  action: \"Drain degraded node pool and scale healthy replicas\"\n  traffic_rerouting: ENABLED\n  rate_limiting_tier: STRICT\n  status: RESOLVED", "prevention_checklist": ["Validate automatic health checks and circuit breaking on Global cluster", "Enforce automated failover thresholds for cross-zone dependency outages", "Integrate real-time statuspage webhook alerting into PagerDuty on-call rotation"], "source_url": "https://stspg.io/3tff32qrsv77", "metadata": {"raw_id": "p1jbzg2bvhj9", "status": "resolved", "resolved_at": "2026-04-23T08:46:39.799Z"}}