incident_id stringlengths 21 30 | company stringclasses 10
values | date timestamp[s]date 2024-01-24 00:00:00 2026-10-05 00:00:00 | title stringlengths 10 113 | severity stringclasses 3
values | service_stack listlengths 4 4 | categories listlengths 1 3 | symptom_logs stringlengths 92 8.06k | root_cause_analysis stringlengths 153 520 | breaking_config_code stringlengths 248 368 | remediation_patch stringclasses 10
values | prevention_checklist listlengths 3 3 | source_url stringlengths 29 65 | metadata dict |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
INC-2026-GITHUB-2dpbcq5j | GitHub | 2026-10-01T00:00:00 | Actions Job Delays | MEDIUM | [
"Actions",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"PIPELINE_EXECUTION_FAILURE"
] | [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.
[2026-10-01 17:50:54 UTC] GitHub SRE (Investigating): GitHub Actions experienced degraded ... | 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... | # Incident architectural state during Actions Job Delays
service_cluster:
provider: "GitHub"
impacted_components: ["Actions", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/kdqxfjn5qg6q | {
"raw_id": "2dpbcq5j165n",
"status": "resolved",
"resolved_at": "2026-10-01T17:56:54.260Z"
} |
INC-2026-GITHUB-c8466lzv | GitHub | 2026-10-01T00:00:00 | Elevated request latency | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE"
] | [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.
[2026-10-01 13:51:20 UTC] GitHub SRE (Monitoring): The degradation has been mitigated. We ... | 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. ... | # Incident architectural state during Elevated request latency
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/cz0ngh11q0tf | {
"raw_id": "c8466lzvnmsv",
"status": "resolved",
"resolved_at": "2026-10-01T13:57:59.327Z"
} |
INC-2026-GITHUB-dqn46wtv | GitHub | 2026-10-01T00:00:00 | [Retroactive] Actions workflow run failures after deployment gate approvals | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"NETWORK_CONNECTIVITY",
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [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... | 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. Servi... | # Incident architectural state during [Retroactive] Actions workflow run failures after deployment gate approvals
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/f0yg8jk2gm80 | {
"raw_id": "dqn46wtvbdzv",
"status": "resolved",
"resolved_at": "2026-10-01T02:00:00.000Z"
} |
INC-2026-GITHUB-169pg72g | GitHub | 2026-09-28T00:00:00 | Copilot Code Review is unable to complete reviews | CRITICAL | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [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 we... | 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... | # Incident architectural state during Copilot Code Review is unable to complete reviews
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/phqvtmdm3y2m | {
"raw_id": "169pg72gg9jr",
"status": "resolved",
"resolved_at": "2026-09-28T22:08:20.216Z"
} |
INC-2026-GITHUB-1dk955gg | GitHub | 2026-09-24T00:00:00 | Disruption with billing information updates | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE"
] | [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, ... | 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 va... | # Incident architectural state during Disruption with billing information updates
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/g2q4g5kv9frp | {
"raw_id": "1dk955gg3bvz",
"status": "resolved",
"resolved_at": "2026-09-24T20:41:12.518Z"
} |
INC-2026-GITHUB-8zc63m64 | GitHub | 2026-09-23T00:00:00 | Incident across several services | MEDIUM | [
"API Requests",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"DATABASE_DEGRADATION",
"API_ERROR_SPIKE"
] | [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 experience... | 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 ... | # Incident architectural state during Incident across several services
service_cluster:
provider: "GitHub"
impacted_components: ["API Requests", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/m1ps7yrhp4n8 | {
"raw_id": "8zc63m64hy36",
"status": "resolved",
"resolved_at": "2026-09-24T04:55:33.949Z"
} |
INC-2026-GITHUB-f6yrxnz5 | GitHub | 2026-09-20T00:00:00 | Incident with Pull Requests | MEDIUM | [
"Pull Requests",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"STORAGE_SUBSYSTEM"
] | [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 A... | 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.... | # Incident architectural state during Incident with Pull Requests
service_cluster:
provider: "GitHub"
impacted_components: ["Pull Requests", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/cx8xcm6k8f9s | {
"raw_id": "f6yrxnz5f7bs",
"status": "resolved",
"resolved_at": "2026-09-20T23:22:16.710Z"
} |
INC-2026-GITHUB-nvy2q96m | GitHub | 2026-09-17T00:00:00 | Elevated rate of errors for OpenAI models provided by Copilot | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"API_ERROR_SPIKE"
] | [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 ... | 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 th... | # Incident architectural state during Elevated rate of errors for OpenAI models provided by Copilot
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/t938cy7649sn | {
"raw_id": "nvy2q96mcmyg",
"status": "resolved",
"resolved_at": "2026-09-17T21:49:01.417Z"
} |
INC-2026-GITHUB-nlxnbqnk | GitHub | 2026-09-16T00:00:00 | Degradation with Gemini 3.8 Flash | HIGH | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [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 n... | 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 Copilo... | # Incident architectural state during Degradation with Gemini 3.8 Flash
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/hsjy12f57b24 | {
"raw_id": "nlxnbqnkdzdl",
"status": "resolved",
"resolved_at": "2026-09-16T17:48:49.246Z"
} |
INC-2026-GITHUB-bk7zgdcq | GitHub | 2026-09-15T00:00:00 | Disruption with some GitHub services | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE"
] | [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... | 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 c... | # Incident architectural state during Disruption with some GitHub services
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/tbh60vgxfxj6 | {
"raw_id": "bk7zgdcq7s9t",
"status": "resolved",
"resolved_at": "2026-09-15T20:00:50.512Z"
} |
INC-2026-GITHUB-qwdwmtqg | GitHub | 2026-09-15T00:00:00 | Disruption with some GitHub services | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"API_ERROR_SPIKE"
] | [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 f... | 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,... | # Incident architectural state during Disruption with some GitHub services
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/6pn81yd1x4hz | {
"raw_id": "qwdwmtqghpk5",
"status": "resolved",
"resolved_at": "2026-09-15T11:17:22.038Z"
} |
INC-2026-GITHUB-kzh5j0mt | GitHub | 2026-09-14T00:00:00 | Actions Larger Runner Jobs for some customers may be slow to start | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"API_ERROR_SPIKE",
"AUTHENTICATION_FAILURE",
"PIPELINE_EXECUTION_FAILURE"
] | [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... | 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 e... | # Incident architectural state during Actions Larger Runner Jobs for some customers may be slow to start
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/f2b6fd4l83wy | {
"raw_id": "kzh5j0mt7qwc",
"status": "resolved",
"resolved_at": "2026-09-14T19:35:48.136Z"
} |
INC-2026-GITHUB-0rn90wk1 | GitHub | 2026-09-13T00:00:00 | Incident with several GitHub Services | CRITICAL | [
"API Requests",
"Issues",
"Pull Requests",
"Actions"
] | [
"QUEUE_DELAY",
"DATABASE_DEGRADATION",
"API_ERROR_SPIKE"
] | [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 re... | 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 p... | # Incident architectural state during Incident with several GitHub Services
service_cluster:
provider: "GitHub"
impacted_components: ["API Requests", "Issues", "Pull Requests", "Actions"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/8f3xch4y0v2k | {
"raw_id": "0rn90wk115q9",
"status": "resolved",
"resolved_at": "2026-09-13T10:44:55.016Z"
} |
INC-2026-GITHUB-zw1hbx2y | GitHub | 2026-09-04T00:00:00 | Disruption with Copilot Code Review | HIGH | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"API_ERROR_SPIKE",
"AUTHENTICATION_FAILURE"
] | [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 p... | 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 a... | # Incident architectural state during Disruption with Copilot Code Review
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/dddfhld6fj0z | {
"raw_id": "zw1hbx2yyhvr",
"status": "resolved",
"resolved_at": "2026-09-04T22:26:46.740Z"
} |
INC-2026-GITHUB-r05vk75c | GitHub | 2026-09-04T00:00:00 | Degradation in repos contents API | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"NETWORK_CONNECTIVITY",
"API_ERROR_SPIKE"
] | [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 ... | 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 c... | # Incident architectural state during Degradation in repos contents API
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/vhmsw2rhdcgv | {
"raw_id": "r05vk75c594j",
"status": "resolved",
"resolved_at": "2026-09-04T22:23:34.887Z"
} |
INC-2026-GITHUB-ktdr5t0x | GitHub | 2026-09-03T00:00:00 | Incident with Grok Copilot AI Model Provider | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"API_ERROR_SPIKE"
] | [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 wi... | 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... | # Incident architectural state during Incident with Grok Copilot AI Model Provider
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/p217h6l54208 | {
"raw_id": "ktdr5t0xwnhp",
"status": "resolved",
"resolved_at": "2026-09-03T17:11:47.860Z"
} |
INC-2026-GITHUB-jk2dy5h9 | GitHub | 2026-09-01T00:00:00 | Delays in commit processing | MEDIUM | [
"Pull Requests",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"STORAGE_SUBSYSTEM"
] | [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 m... | 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 ... | # Incident architectural state during Delays in commit processing
service_cluster:
provider: "GitHub"
impacted_components: ["Pull Requests", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/0xbhhq84v4mt | {
"raw_id": "jk2dy5h9yp3m",
"status": "resolved",
"resolved_at": "2026-09-01T16:01:21.369Z"
} |
INC-2026-GITHUB-7fxts6gm | GitHub | 2026-08-31T00:00:00 | Elevated rate of errors for OpenAI models provided by Copilot | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"API_ERROR_SPIKE"
] | [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 rat... | 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 ele... | # Incident architectural state during Elevated rate of errors for OpenAI models provided by Copilot
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/8trzn5bjrtnn | {
"raw_id": "7fxts6gmq5gr",
"status": "resolved",
"resolved_at": "2026-08-31T09:58:14.157Z"
} |
INC-2026-GITHUB-5bn0vk44 | GitHub | 2026-08-26T00:00:00 | Disruption with GitHub Billing | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE",
"STORAGE_SUBSYSTEM"
] | [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 continui... | 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 start... | # Incident architectural state during Disruption with GitHub Billing
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/cpgst4hly3mh | {
"raw_id": "5bn0vk444m1w",
"status": "resolved",
"resolved_at": "2026-08-27T19:44:08.799Z"
} |
INC-2026-GITHUB-tx9qn4kh | GitHub | 2026-08-27T00:00:00 | Incident with Copilot AI Model Providers | CRITICAL | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"API_ERROR_SPIKE"
] | [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 /... | 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 ... | # Incident architectural state during Incident with Copilot AI Model Providers
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/573gc8p4328b | {
"raw_id": "tx9qn4khd664",
"status": "resolved",
"resolved_at": "2026-08-27T12:12:58.387Z"
} |
INC-2026-GITHUB-kfspvrz1 | GitHub | 2026-08-26T00:00:00 | Incident with Actions and Pull Requests | MEDIUM | [
"Pull Requests",
"Actions",
"GitHub Actions",
"Git"
] | [
"QUEUE_DELAY"
] | [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, ... | 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, mergeabilit... | # Incident architectural state during Incident with Actions and Pull Requests
service_cluster:
provider: "GitHub"
impacted_components: ["Pull Requests", "Actions", "GitHub Actions", "Git"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/nrbwjftcz72d | {
"raw_id": "kfspvrz14xr0",
"status": "resolved",
"resolved_at": "2026-08-27T00:26:44.772Z"
} |
INC-2026-GITHUB-y1t7p9fz | GitHub | 2026-08-26T00:00:00 | Incident with Actions | CRITICAL | [
"Actions",
"Pages",
"GitHub Actions",
"Git"
] | [
"QUEUE_DELAY",
"DATABASE_DEGRADATION",
"PIPELINE_EXECUTION_FAILURE"
] | [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 ... | 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... | # Incident architectural state during Incident with Actions
service_cluster:
provider: "GitHub"
impacted_components: ["Actions", "Pages", "GitHub Actions", "Git"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/pg14nv9m3095 | {
"raw_id": "y1t7p9fzrlj2",
"status": "resolved",
"resolved_at": "2026-08-26T18:01:30.665Z"
} |
INC-2026-GITHUB-hcbtzksc | GitHub | 2026-08-26T00:00:00 | Disruption with some GitHub services | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"API_ERROR_SPIKE"
] | [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
[2026-08-26 15:09:03 UTC] GitHub SRE (Investigating): We are investigating reports of impacted performance for some GitHub services. | 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. | # Incident architectural state during Disruption with some GitHub services
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/4s4bvnc0frrj | {
"raw_id": "hcbtzksccj2f",
"status": "resolved",
"resolved_at": "2026-08-26T16:07:52.512Z"
} |
INC-2026-GITHUB-lyppgxbq | GitHub | 2026-08-24T00:00:00 | Actions delays in starting runs | MEDIUM | [
"Actions",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"PIPELINE_EXECUTION_FAILURE",
"STORAGE_SUBSYSTEM"
] | [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 responsi... | 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 ins... | # Incident architectural state during Actions delays in starting runs
service_cluster:
provider: "GitHub"
impacted_components: ["Actions", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/v6ysclb9vcbd | {
"raw_id": "lyppgxbq1nyk",
"status": "resolved",
"resolved_at": "2026-08-24T14:34:42.451Z"
} |
INC-2026-GITHUB-wt3hjqcr | GitHub | 2026-08-24T00:00:00 | Elevated errors on Fable 5 due to upstream provider | HIGH | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"API_ERROR_SPIKE"
] | [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 sometime... | 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 re... | # Incident architectural state during Elevated errors on Fable 5 due to upstream provider
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/4dz9rv14dz14 | {
"raw_id": "wt3hjqcrczfg",
"status": "resolved",
"resolved_at": "2026-08-24T07:58:41.636Z"
} |
INC-2026-GITHUB-wms44hv6 | GitHub | 2026-08-21T00:00:00 | Degraded Git Operations over SSH | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"API_ERROR_SPIKE"
] | [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 appr... | 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... | # Incident architectural state during Degraded Git Operations over SSH
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/9nls6g9ln8p4 | {
"raw_id": "wms44hv62t3p",
"status": "resolved",
"resolved_at": "2026-08-21T14:00:00.000Z"
} |
INC-2026-GITHUB-bhbcjn4n | GitHub | 2026-08-20T00:00:00 | Intermittent failures creating agent tasks | CRITICAL | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"DATABASE_DEGRADATION",
"API_ERROR_SPIKE"
] | [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... | 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 compl... | # Incident architectural state during Intermittent failures creating agent tasks
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/py1yl5mnq89c | {
"raw_id": "bhbcjn4n3jzp",
"status": "resolved",
"resolved_at": "2026-08-21T00:37:20.224Z"
} |
INC-2026-GITHUB-bmpybhnr | GitHub | 2026-08-18T00:00:00 | Intermittent failures in runner group and runner-related permissions pages | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"API_ERROR_SPIKE",
"AUTHENTICATION_FAILURE",
"PIPELINE_EXECUTION_FAILURE"
] | [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 failur... | 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 d... | # Incident architectural state during Intermittent failures in runner group and runner-related permissions pages
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/98zqb1k9jh0x | {
"raw_id": "bmpybhnrky3x",
"status": "resolved",
"resolved_at": "2026-08-18T11:42:59.304Z"
} |
INC-2026-GITHUB-gx7js8bd | GitHub | 2026-08-18T00:00:00 | Incident with Actions | HIGH | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"API_ERROR_SPIKE",
"AUTHENTICATION_FAILURE",
"PIPELINE_EXECUTION_FAILURE"
] | [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... | 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 fail... | # Incident architectural state during Incident with Actions
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/q3ck88mqw08z | {
"raw_id": "gx7js8bd0jpz",
"status": "resolved",
"resolved_at": "2026-08-18T10:23:23.000Z"
} |
INC-2026-GITHUB-zkxwbgr0 | GitHub | 2026-08-17T00:00:00 | Incident with GitHub.com | CRITICAL | [
"Git Operations",
"Webhooks",
"API Requests",
"Issues"
] | [
"QUEUE_DELAY",
"NETWORK_CONNECTIVITY",
"API_ERROR_SPIKE"
] | [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 approximat... | 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 rea... | # Incident architectural state during Incident with GitHub.com
service_cluster:
provider: "GitHub"
impacted_components: ["Git Operations", "Webhooks", "API Requests", "Issues"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/y1fl26l6wpzr | {
"raw_id": "zkxwbgr0cnmx",
"status": "resolved",
"resolved_at": "2026-08-17T21:15:46.623Z"
} |
INC-2026-GITHUB-pf25whpq | GitHub | 2026-08-13T00:00:00 | Disruption with GHEC Team Sync | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [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... | 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 gr... | # Incident architectural state during Disruption with GHEC Team Sync
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/l6tmhqw07cmj | {
"raw_id": "pf25whpq58hh",
"status": "resolved",
"resolved_at": "2026-08-13T18:27:54.660Z"
} |
INC-2026-GITHUB-24t8gsgq | GitHub | 2026-08-13T00:00:00 | Errors with the Fable 5 Model in Copilot | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"API_ERROR_SPIKE"
] | [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 sele... | 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%.... | # Incident architectural state during Errors with the Fable 5 Model in Copilot
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/8htrnxk0q09v | {
"raw_id": "24t8gsgqx2qb",
"status": "resolved",
"resolved_at": "2026-08-13T15:47:22.384Z"
} |
INC-2026-GITHUB-k8vbzwqj | GitHub | 2026-08-13T00:00:00 | Incident with Webhooks | MEDIUM | [
"Git Operations",
"Webhooks",
"Issues",
"Pull Requests"
] | [
"DATABASE_DEGRADATION",
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [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, wit... | 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 mana... | # Incident architectural state during Incident with Webhooks
service_cluster:
provider: "GitHub"
impacted_components: ["Git Operations", "Webhooks", "Issues", "Pull Requests"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/f0cgtdc0kqxg | {
"raw_id": "k8vbzwqjkxzn",
"status": "resolved",
"resolved_at": "2026-08-13T15:36:34.631Z"
} |
INC-2026-GITHUB-lsvy8xsf | GitHub | 2026-08-12T00:00:00 | Disruption with Login and Release Asset downloads | HIGH | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"NETWORK_CONNECTIVITY",
"API_ERROR_SPIKE",
"AUTHENTICATION_FAILURE"
] | [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 infrastruct... | 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 ... | # Incident architectural state during Disruption with Login and Release Asset downloads
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/xp36nwz4rrh1 | {
"raw_id": "lsvy8xsf0gxv",
"status": "resolved",
"resolved_at": "2026-08-12T22:56:39.025Z"
} |
INC-2026-GITHUB-76t89hbf | GitHub | 2026-08-12T00:00:00 | Incident with Pull Requests and Issues | MEDIUM | [
"Issues",
"Pull Requests",
"GitHub Actions",
"Git"
] | [
"DATABASE_DEGRADATION"
] | [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 remov... | 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 ind... | # Incident architectural state during Incident with Pull Requests and Issues
service_cluster:
provider: "GitHub"
impacted_components: ["Issues", "Pull Requests", "GitHub Actions", "Git"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/ssd9z8l2g46v | {
"raw_id": "76t89hbfb09h",
"status": "resolved",
"resolved_at": "2026-08-12T16:41:18.768Z"
} |
INC-2026-GITHUB-vm1w8zq9 | GitHub | 2026-08-11T00:00:00 | Incident with GraphQL API Requests | MEDIUM | [
"API Requests",
"GitHub Actions",
"Git",
"REST API"
] | [
"NETWORK_CONNECTIVITY",
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [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 increase... | 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 ... | # Incident architectural state during Incident with GraphQL API Requests
service_cluster:
provider: "GitHub"
impacted_components: ["API Requests", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/3xn46bst0bjh | {
"raw_id": "vm1w8zq95wkt",
"status": "resolved",
"resolved_at": "2026-08-11T20:06:56.575Z"
} |
INC-2026-GITHUB-1t7x65n7 | GitHub | 2026-08-10T00:00:00 | Disruption with Copilot for access to some models | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [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 shorte... | 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 f... | # Incident architectural state during Disruption with Copilot for access to some models
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/4x5bd0ghzy0x | {
"raw_id": "1t7x65n7kvt1",
"status": "resolved",
"resolved_at": "2026-08-10T21:50:43.756Z"
} |
INC-2026-GITHUB-s19bth7w | GitHub | 2026-08-10T00:00:00 | Disruption with creation of fine grained personal access tokens | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"API_ERROR_SPIKE",
"AUTHENTICATION_FAILURE"
] | [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... | 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... | # Incident architectural state during Disruption with creation of fine grained personal access tokens
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/tjf46x5zq25c | {
"raw_id": "s19bth7wzkf7",
"status": "resolved",
"resolved_at": "2026-08-10T18:46:22.280Z"
} |
INC-2026-GITHUB-qcvjkzcs | GitHub | 2026-08-06T00:00:00 | Incident with Actions | CRITICAL | [
"Actions",
"Pages",
"GitHub Actions",
"Git"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [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 ... | 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-hoste... | # Incident architectural state during Incident with Actions
service_cluster:
provider: "GitHub"
impacted_components: ["Actions", "Pages", "GitHub Actions", "Git"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/rcz3fcm83sff | {
"raw_id": "qcvjkzcs7j74",
"status": "resolved",
"resolved_at": "2026-08-07T02:04:44.460Z"
} |
INC-2026-GITHUB-1xqvzyv9 | GitHub | 2026-08-06T00:00:00 | Incident with Pages - Deployment Lag | MEDIUM | [
"Pages",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"DATABASE_DEGRADATION",
"PIPELINE_EXECUTION_FAILURE"
] | [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... | 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. <b... | # Incident architectural state during Incident with Pages - Deployment Lag
service_cluster:
provider: "GitHub"
impacted_components: ["Pages", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/b0n00sx9z3ht | {
"raw_id": "1xqvzyv99skw",
"status": "resolved",
"resolved_at": "2026-08-06T16:22:59.638Z"
} |
INC-2026-GITHUB-9wzhl5jr | GitHub | 2026-08-05T00:00:00 | Some Copilot Cloud Agent jobs not starting | MEDIUM | [
"GitHub Actions",
"Git",
"REST API",
"Webhooks"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE"
] | [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 ... | 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 ... | # Incident architectural state during Some Copilot Cloud Agent jobs not starting
service_cluster:
provider: "GitHub"
impacted_components: ["GitHub Actions", "Git", "REST API", "Webhooks"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/kxdh3hfxm3zl | {
"raw_id": "9wzhl5jr80jt",
"status": "resolved",
"resolved_at": "2026-08-05T13:00:25.857Z"
} |
INC-2026-GITHUB-7s119p1y | GitHub | 2026-08-03T00:00:00 | Incident with Copilot | MEDIUM | [
"Copilot",
"GitHub Actions",
"Git",
"REST API"
] | [
"AUTHENTICATION_FAILURE"
] | [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 ... | 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, ... | # Incident architectural state during Incident with Copilot
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/y3tm8v1gmn85 | {
"raw_id": "7s119p1yxttr",
"status": "resolved",
"resolved_at": "2026-08-03T11:25:12.371Z"
} |
INC-2026-GITHUB-sj1tzyrx | GitHub | 2026-08-01T00:00:00 | Incident with Copilot AI Model Providers | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE"
] | [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 r... | 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%.... | # Incident architectural state during Incident with Copilot AI Model Providers
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/z58g1g529hzz | {
"raw_id": "sj1tzyrx599x",
"status": "resolved",
"resolved_at": "2026-08-01T18:44:28.733Z"
} |
INC-2026-GITHUB-kk183dsl | GitHub | 2026-08-01T00:00:00 | Degraded availability GPT 5.6 Luna | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [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 ... | 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, a... | # Incident architectural state during Degraded availability GPT 5.6 Luna
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/pj5lgggbc2rb | {
"raw_id": "kk183dslzdzd",
"status": "resolved",
"resolved_at": "2026-08-01T12:30:21.775Z"
} |
INC-2026-GITHUB-9tpgqq1h | GitHub | 2026-07-30T00:00:00 | Copilot model Claude Fable 5 experiencing elevated errors | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [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 ca... | 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 o... | # Incident architectural state during Copilot model Claude Fable 5 experiencing elevated errors
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/45g8r57kv3n9 | {
"raw_id": "9tpgqq1h4bs7",
"status": "resolved",
"resolved_at": "2026-07-30T10:12:15.489Z"
} |
INC-2026-GITHUB-dsrfymph | GitHub | 2026-07-29T00:00:00 | Incident with Copilot AI Model Providers | MEDIUM | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE"
] | [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 rem... | 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%. O... | # Incident architectural state during Incident with Copilot AI Model Providers
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/tdw1hjz3lj91 | {
"raw_id": "dsrfymph7my0",
"status": "resolved",
"resolved_at": "2026-07-29T21:51:26.803Z"
} |
INC-2026-GITHUB-75g5xmzp | GitHub | 2026-07-29T00:00:00 | Incident with Actions | HIGH | [
"Actions",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [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 ... | 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. T... | # Incident architectural state during Incident with Actions
service_cluster:
provider: "GitHub"
impacted_components: ["Actions", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/8nsh6820sff9 | {
"raw_id": "75g5xmzptjqb",
"status": "resolved",
"resolved_at": "2026-07-29T16:00:54.006Z"
} |
INC-2026-GITHUB-fmmsrcg5 | GitHub | 2026-07-27T00:00:00 | Incident with GraphQL API Requests | MEDIUM | [
"API Requests",
"GitHub Actions",
"Git",
"REST API"
] | [
"API_ERROR_SPIKE"
] | [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, wit... | 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 reg... | # Incident architectural state during Incident with GraphQL API Requests
service_cluster:
provider: "GitHub"
impacted_components: ["API Requests", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/vr201n49yl53 | {
"raw_id": "fmmsrcg5x638",
"status": "resolved",
"resolved_at": "2026-07-27T04:09:10.590Z"
} |
INC-2026-GITHUB-pz7g535g | GitHub | 2026-07-25T00:00:00 | Actions run failures and delays | CRITICAL | [
"Actions",
"GitHub Actions",
"Git",
"REST API"
] | [
"QUEUE_DELAY"
] | [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
[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 p... | 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 queu... | # Incident architectural state during Actions run failures and delays
service_cluster:
provider: "GitHub"
impacted_components: ["Actions", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/448g37mrq066 | {
"raw_id": "pz7g535gbs6p",
"status": "resolved",
"resolved_at": "2026-07-25T13:13:21.503Z"
} |
INC-2026-GITHUB-vv9vvksm | GitHub | 2026-07-25T00:00:00 | Several GPT models degraded | HIGH | [
"Copilot AI Model Providers",
"GitHub Actions",
"Git",
"REST API"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [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 fai... | 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... | # Incident architectural state during Several GPT models degraded
service_cluster:
provider: "GitHub"
impacted_components: ["Copilot AI Model Providers", "GitHub Actions", "Git", "REST API"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by GitHub SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://stspg.io/vh0xxw69dr6v | {
"raw_id": "vv9vvksmj4s9",
"status": "resolved",
"resolved_at": "2026-07-25T10:11:16.738Z"
} |
INC-2026-CLOUDFLARE-q2bck6r3 | Cloudflare | 2026-10-03T00:00:00 | Issues with Workers Build failing to start | MEDIUM | [
"Workers Builds",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"PIPELINE_EXECUTION_FAILURE"
] | [2026-10-05 07:28:10 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-10-03 08:54:50 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-10-03 05:54:59 UTC] Cloudflare SRE (Investigating): Cloudflare is aware of and investigating an issue with Clou... | 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 u... | # Incident architectural state during Issues with Workers Build failing to start
service_cluster:
provider: "Cloudflare"
impacted_components: ["Workers Builds", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/q2bck6r39bzk | {
"raw_id": "q2bck6r39bzk",
"status": "resolved",
"resolved_at": "2026-10-05T07:28:10.019Z"
} |
INC-2026-CLOUDFLARE-2xnmsnv8 | Cloudflare | 2026-10-02T00:00:00 | Cloudflare CDN experiencing increase in errors. | CRITICAL | [
"CDN/Cache",
"CDN Cache Purge",
"Cloudflare Edge",
"DNS"
] | [
"API_ERROR_SPIKE"
] | [2026-10-02 21:57:57 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[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 co... | 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... | # Incident architectural state during Cloudflare CDN experiencing increase in errors.
service_cluster:
provider: "Cloudflare"
impacted_components: ["CDN/Cache", "CDN Cache Purge", "Cloudflare Edge", "DNS"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/2xnmsnv8yv5x | {
"raw_id": "2xnmsnv8yv5x",
"status": "resolved",
"resolved_at": "2026-10-02T21:57:57.692Z"
} |
INC-2026-CLOUDFLARE-0kj5cjjq | Cloudflare | 2026-10-02T00:00:00 | Network Performance Issues - Seoul (ICN) | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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).
The issue has been identified and fully mitigated, and network performance has returned to normal levels. | Official investigation timeline recorded by Cloudflare engineering: Between 17:11 and 17:22 UTC, Cloudflare experienced network performance degradation impacting Seoul, South Korea (ICN).
The issue has been identified and fully mitigated, and network performance has returned to normal levels. | # Incident architectural state during Network Performance Issues - Seoul (ICN)
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/0kj5cjjq93xn | {
"raw_id": "0kj5cjjq93xn",
"status": "resolved",
"resolved_at": "2026-10-02T16:00:00.000Z"
} |
INC-2026-CLOUDFLARE-fs7dz54l | Cloudflare | 2026-09-30T00:00:00 | Network Performance Issues in Madrid | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [2026-10-02 05:42:29 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-30 14:06:40 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-30 11:31:16 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
... | 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).
We are working to... | # Incident architectural state during Network Performance Issues in Madrid
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/fs7dz54l226c | {
"raw_id": "fs7dz54l226c",
"status": "resolved",
"resolved_at": "2026-10-02T05:42:29.851Z"
} |
INC-2026-CLOUDFLARE-4m03612l | Cloudflare | 2026-09-30T00:00:00 | Cloudflare Workers build delays | MEDIUM | [
"Workers Builds",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY",
"PIPELINE_EXECUTION_FAILURE"
] | [2026-10-01 21:27:12 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-30 17:42:28 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-30 15:33:06 UTC] Cloudflare SRE (Investigating): Cloudflare is aware of and investigating an issue with Clou... | 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 p... | # Incident architectural state during Cloudflare Workers build delays
service_cluster:
provider: "Cloudflare"
impacted_components: ["Workers Builds", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/4m03612lprhr | {
"raw_id": "4m03612lprhr",
"status": "resolved",
"resolved_at": "2026-10-01T21:27:12.818Z"
} |
INC-2026-CLOUDFLARE-hyv5p7wn | Cloudflare | 2026-10-01T00:00:00 | Increased Errors for Durable Objects and R2 | MEDIUM | [
"Durable Objects",
"R2",
"Cloudflare Edge",
"DNS"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [2026-10-01 21:18:42 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-10-01 21:06:14 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-10-01 20:59:56 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating issues causing an increase of e... | 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 ... | # Incident architectural state during Increased Errors for Durable Objects and R2
service_cluster:
provider: "Cloudflare"
impacted_components: ["Durable Objects", "R2", "Cloudflare Edge", "DNS"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/hyv5p7wn1c8v | {
"raw_id": "hyv5p7wn1c8v",
"status": "resolved",
"resolved_at": "2026-10-01T21:18:42.733Z"
} |
INC-2026-CLOUDFLARE-4c842mwy | Cloudflare | 2026-10-01T00:00:00 | Intermittent network connectivity issues in Mumbai | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during Intermittent network connectivity issues in Mumbai
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/4c842mwy6z4l | {
"raw_id": "4c842mwy6z4l",
"status": "resolved",
"resolved_at": "2026-10-01T19:30:00.000Z"
} |
INC-2026-CLOUDFLARE-n2645m15 | Cloudflare | 2026-10-01T00:00:00 | Network Performance Issues in Columbus colo in Ohio | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during Network Performance Issues in Columbus colo in Ohio
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/n2645m15vwc9 | {
"raw_id": "n2645m15vwc9",
"status": "resolved",
"resolved_at": "2026-10-01T15:30:00.000Z"
} |
INC-2026-CLOUDFLARE-mq69fw5y | Cloudflare | 2026-09-30T00:00:00 | Network Performance Issues in Los Angeles (LAX) | MEDIUM | [
"Containers",
"Durable Objects",
"Hyperdrive",
"R2"
] | [
"NETWORK_CONNECTIVITY"
] | [2026-09-30 19:18:41 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-30 14:39:04 UTC] Cloudflare SRE (Investigating): We are continuing to investigate this issue.
[2026-09-30 13:49:25 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating possible network congestion in Los Angeles (L... | 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... | # Incident architectural state during Network Performance Issues in Los Angeles (LAX)
service_cluster:
provider: "Cloudflare"
impacted_components: ["Containers", "Durable Objects", "Hyperdrive", "R2"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/mq69fw5ykdwb | {
"raw_id": "mq69fw5ykdwb",
"status": "resolved",
"resolved_at": "2026-09-30T19:18:41.309Z"
} |
INC-2026-CLOUDFLARE-2h896759 | Cloudflare | 2026-09-30T00:00:00 | Membership Permission Change Delays | MEDIUM | [
"API",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY",
"API_ERROR_SPIKE"
] | [2026-09-30 18:10:55 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-30 18:04:02 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-30 13:36:42 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating delays in applying changes to a... | 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... | # Incident architectural state during Membership Permission Change Delays
service_cluster:
provider: "Cloudflare"
impacted_components: ["API", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/2h896759fg2f | {
"raw_id": "2h896759fg2f",
"status": "resolved",
"resolved_at": "2026-09-30T18:10:55.604Z"
} |
INC-2026-CLOUDFLARE-0dq5fbp2 | Cloudflare | 2026-09-30T00:00:00 | WARP connectivity in Newark, NJ | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during WARP connectivity in Newark, NJ
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/0dq5fbp2xwbj | {
"raw_id": "0dq5fbp2xwbj",
"status": "resolved",
"resolved_at": "2026-09-30T00:45:00.000Z"
} |
INC-2026-CLOUDFLARE-8wmvkv5j | Cloudflare | 2026-09-23T00:00:00 | Network Performance Degradation — Asia-Pacific | MEDIUM | [
"Network",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"NETWORK_CONNECTIVITY"
] | [2026-09-29 23:01:27 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[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.
[2026-09-23 18:... | 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 implem... | # Incident architectural state during Network Performance Degradation — Asia-Pacific
service_cluster:
provider: "Cloudflare"
impacted_components: ["Network", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/8wmvkv5jkf15 | {
"raw_id": "8wmvkv5jkf15",
"status": "resolved",
"resolved_at": "2026-09-29T23:01:27.182Z"
} |
INC-2026-CLOUDFLARE-vcstgt8g | Cloudflare | 2026-09-29T00:00:00 | OTP Deliverability Errors | MEDIUM | [
"Access",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"AUTHENTICATION_FAILURE"
] | [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.
[2026-09-29 20:11:20 UTC] Cloudflare SRE (Investigating): We are investigating an iss... | 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 ... | # Incident architectural state during OTP Deliverability Errors
service_cluster:
provider: "Cloudflare"
impacted_components: ["Access", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/vcstgt8gqkyk | {
"raw_id": "vcstgt8gqkyk",
"status": "resolved",
"resolved_at": "2026-09-29T20:50:35.186Z"
} |
INC-2026-CLOUDFLARE-32sg73xw | Cloudflare | 2026-09-28T00:00:00 | Network Performance Issues in Eastern North America | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY",
"API_ERROR_SPIKE"
] | [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. | 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. | # Incident architectural state during Network Performance Issues in Eastern North America
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/32sg73xwyq89 | {
"raw_id": "32sg73xwyq89",
"status": "resolved",
"resolved_at": "2026-09-28T20:36:00.227Z"
} |
INC-2026-CLOUDFLARE-smn1d93z | Cloudflare | 2026-09-28T00:00:00 | Replicate Flux Hotswap Models Stuck | MEDIUM | [
"Replicate",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [2026-09-28 20:28:58 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[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. | 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. | # Incident architectural state during Replicate Flux Hotswap Models Stuck
service_cluster:
provider: "Cloudflare"
impacted_components: ["Replicate", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/smn1d93zd3hr | {
"raw_id": "smn1d93zd3hr",
"status": "resolved",
"resolved_at": "2026-09-28T20:28:58.448Z"
} |
INC-2026-CLOUDFLARE-6m2w2ls1 | Cloudflare | 2026-09-26T00:00:00 | R2 Service Issues in Western North America (WNAM) | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during R2 Service Issues in Western North America (WNAM)
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/6m2w2ls1gv75 | {
"raw_id": "6m2w2ls1gv75",
"status": "resolved",
"resolved_at": "2026-09-26T16:00:00.000Z"
} |
INC-2026-CLOUDFLARE-39dzwkhz | Cloudflare | 2026-09-26T00:00:00 | Cloudflare Cloud Access Security Broker (CASB) Issues | MEDIUM | [
"Cloud Access Security Broker (CASB)",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY"
] | [2026-09-26 10:58:05 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-26 10:47:41 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-26 10:44:49 UTC] Cloudflare SRE (Investigating): We are continuing to investigate this issue.
[2026-09-26 10... | 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 ... | # Incident architectural state during Cloudflare Cloud Access Security Broker (CASB) Issues
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloud Access Security Broker (CASB)", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/39dzwkhzcvv5 | {
"raw_id": "39dzwkhzcvv5",
"status": "resolved",
"resolved_at": "2026-09-26T10:58:05.152Z"
} |
INC-2026-CLOUDFLARE-gv29fd07 | Cloudflare | 2026-09-25T00:00:00 | Issues with Durable Objects | MEDIUM | [
"Durable Objects",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY"
] | [2026-09-25 14:49:01 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-25 08:48:52 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-25 02:32:19 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating issues causing an increase of e... | 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 fo... | # Incident architectural state during Issues with Durable Objects
service_cluster:
provider: "Cloudflare"
impacted_components: ["Durable Objects", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/gv29fd076q2t | {
"raw_id": "gv29fd076q2t",
"status": "resolved",
"resolved_at": "2026-09-25T14:49:01.414Z"
} |
INC-2026-CLOUDFLARE-drq3pdx1 | Cloudflare | 2026-09-25T00:00:00 | Edit Compression Rule Issue | MEDIUM | [
"Rules",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [2026-09-25 06:31:10 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-25 06:26:47 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-25 05:58:40 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
... | 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.
Customers may see e... | # Incident architectural state during Edit Compression Rule Issue
service_cluster:
provider: "Cloudflare"
impacted_components: ["Rules", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/drq3pdx1f11y | {
"raw_id": "drq3pdx1f11y",
"status": "resolved",
"resolved_at": "2026-09-25T06:31:10.232Z"
} |
INC-2026-CLOUDFLARE-7dt6f0ch | Cloudflare | 2026-09-25T00:00:00 | Secondary DNS Update Delays | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"QUEUE_DELAY",
"NETWORK_CONNECTIVITY"
] | [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 ... | 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... | # Incident architectural state during Secondary DNS Update Delays
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/7dt6f0chnclh | {
"raw_id": "7dt6f0chnclh",
"status": "resolved",
"resolved_at": "2026-09-25T01:52:00.000Z"
} |
INC-2026-CLOUDFLARE-mltthh0j | Cloudflare | 2026-09-24T00:00:00 | Browser isolation session data sync issues | MEDIUM | [
"Browser Isolation",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"STORAGE_SUBSYSTEM"
] | [2026-09-24 22:37:13 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-24 17:28:20 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-24 17:26:03 UTC] Cloudflare SRE (Identified): Cloudflare is investigating issues with Browser Isolation's se... | 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... | # Incident architectural state during Browser isolation session data sync issues
service_cluster:
provider: "Cloudflare"
impacted_components: ["Browser Isolation", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/mltthh0jxxpz | {
"raw_id": "mltthh0jxxpz",
"status": "resolved",
"resolved_at": "2026-09-24T22:37:13.982Z"
} |
INC-2026-CLOUDFLARE-2x4qt2q2 | Cloudflare | 2026-09-24T00:00:00 | Intermittent 500 errors for backend services on Replicate | MEDIUM | [
"Replicate",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY",
"PIPELINE_EXECUTION_FAILURE"
] | [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.
[2026-09-24 20:40:47 UTC] Cloudflare SRE (Investigating): We have a backend component that enter... | 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... | # Incident architectural state during Intermittent 500 errors for backend services on Replicate
service_cluster:
provider: "Cloudflare"
impacted_components: ["Replicate", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/2x4qt2q2ds9x | {
"raw_id": "2x4qt2q2ds9x",
"status": "resolved",
"resolved_at": "2026-09-24T22:34:56.071Z"
} |
INC-2026-CLOUDFLARE-dwfzz0bw | Cloudflare | 2026-09-24T00:00:00 | Delays Starting Cloudflare Workers Builds | MEDIUM | [
"Workers Builds",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY",
"PIPELINE_EXECUTION_FAILURE"
] | [2026-09-24 20:52:46 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-24 19:54:48 UTC] Cloudflare SRE (Monitoring): Queue levels & latency are returning to normal
[2026-09-24 17:33:57 UTC] Cloudflare SRE (Monitoring): Customers may experience delays starting Cloudflare Workers builds. | 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. | # Incident architectural state during Delays Starting Cloudflare Workers Builds
service_cluster:
provider: "Cloudflare"
impacted_components: ["Workers Builds", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/dwfzz0bwhmsq | {
"raw_id": "dwfzz0bwhmsq",
"status": "resolved",
"resolved_at": "2026-09-24T20:52:46.358Z"
} |
INC-2026-CLOUDFLARE-xbgbb80y | Cloudflare | 2026-09-24T00:00:00 | Cloudflare Access updates delayed | MEDIUM | [
"Access",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY",
"AUTHENTICATION_FAILURE"
] | [2026-09-24 18:25:30 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-24 15:31:57 UTC] Cloudflare SRE (Monitoring): We have applied a fix and are actively monitoring.
[2026-09-24 15:20:39 UTC] Cloudflare SRE (Investigating): Cloudflare engineering is investigating an issue causing a delay in co... | 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 enfo... | # Incident architectural state during Cloudflare Access updates delayed
service_cluster:
provider: "Cloudflare"
impacted_components: ["Access", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/xbgbb80yw0jh | {
"raw_id": "xbgbb80yw0jh",
"status": "resolved",
"resolved_at": "2026-09-24T18:25:30.401Z"
} |
INC-2026-CLOUDFLARE-gwrzznc9 | Cloudflare | 2026-09-24T00:00:00 | Customers using BYOIP can have issues updating their BGP prefixes, including advertising or withdrawing prefixes. | MEDIUM | [
"Bring Your Own IP (BYOIP)",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY",
"NETWORK_CONNECTIVITY"
] | [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.
[2026-09-24 10:22:34 UTC] Cl... | 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 curren... | # Incident architectural state during Customers using BYOIP can have issues updating their BGP prefixes, including advertising or withdrawing prefixes.
service_cluster:
provider: "Cloudflare"
impacted_components: ["Bring Your Own IP (BYOIP)", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circui... | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/gwrzznc9f642 | {
"raw_id": "gwrzznc9f642",
"status": "resolved",
"resolved_at": "2026-09-24T10:25:52.106Z"
} |
INC-2026-CLOUDFLARE-jg6ys8sb | Cloudflare | 2026-09-23T00:00:00 | Intermittent authentication errors for API and R2 | MEDIUM | [
"R2",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"API_ERROR_SPIKE",
"AUTHENTICATION_FAILURE"
] | [2026-09-23 20:59:35 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-23 20:09:18 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-23 09:08:53 UTC] Cloudflare SRE (Identified): A known issue affected authentication for a small percentage o... | 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.
The issue was identified on Sep 22 at 13:30 UTC, and major impact... | # Incident architectural state during Intermittent authentication errors for API and R2
service_cluster:
provider: "Cloudflare"
impacted_components: ["R2", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/jg6ys8sbd6ny | {
"raw_id": "jg6ys8sbd6ny",
"status": "resolved",
"resolved_at": "2026-09-23T20:59:35.579Z"
} |
INC-2026-CLOUDFLARE-f8wg5htd | Cloudflare | 2026-09-23T00:00:00 | Elevated Errors with any / all in http_response_cache_settings | MEDIUM | [
"Rules",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"API_ERROR_SPIKE",
"PIPELINE_EXECUTION_FAILURE"
] | [2026-09-23 18:08:18 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[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.
This issue strict... | 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.
This issue strictly affects API operations; existing acti... | # Incident architectural state during Elevated Errors with any / all in http_response_cache_settings
service_cluster:
provider: "Cloudflare"
impacted_components: ["Rules", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/f8wg5htd3zz4 | {
"raw_id": "f8wg5htd3zz4",
"status": "resolved",
"resolved_at": "2026-09-23T18:08:18.013Z"
} |
INC-2026-CLOUDFLARE-tl0vrgjy | Cloudflare | 2026-09-22T00:00:00 | Cloudflare One Clients are incorrectly challenged on some sites | MEDIUM | [
"Cloudflare One Client",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [2026-09-23 11:02:41 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
[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. | 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. | # Incident architectural state during Cloudflare One Clients are incorrectly challenged on some sites
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare One Client", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/tl0vrgjy99r0 | {
"raw_id": "tl0vrgjy99r0",
"status": "identified",
"resolved_at": null
} |
INC-2026-CLOUDFLARE-78c19w4x | Cloudflare | 2026-09-23T00:00:00 | Increased Errors for Durable Objects | MEDIUM | [
"Durable Objects",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [2026-09-23 10:00:09 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-23 09:20:17 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-23 08:35:32 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
... | 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 impac... | # Incident architectural state during Increased Errors for Durable Objects
service_cluster:
provider: "Cloudflare"
impacted_components: ["Durable Objects", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/78c19w4xw4z2 | {
"raw_id": "78c19w4xw4z2",
"status": "resolved",
"resolved_at": "2026-09-23T10:00:09.478Z"
} |
INC-2026-CLOUDFLARE-x86v1qk8 | Cloudflare | 2026-09-23T00:00:00 | Elevated number of R2 503 errors in Australian Eastern Coast region | MEDIUM | [
"Sydney, NSW, Australia - (SYD)",
"R2",
"Cloudflare Edge",
"DNS"
] | [
"API_ERROR_SPIKE"
] | [2026-09-23 04:25:51 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-23 04:22:07 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-23 04:09:54 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
... | 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. | # Incident architectural state during Elevated number of R2 503 errors in Australian Eastern Coast region
service_cluster:
provider: "Cloudflare"
impacted_components: ["Sydney, NSW, Australia - (SYD)", "R2", "Cloudflare Edge", "DNS"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold... | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/x86v1qk8yp5v | {
"raw_id": "x86v1qk8yp5v",
"status": "resolved",
"resolved_at": "2026-09-23T04:25:51.870Z"
} |
INC-2026-CLOUDFLARE-rcjbfb0l | Cloudflare | 2026-09-23T00:00:00 | Issues with 1.1.1.1 for Families | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY",
"AUTHENTICATION_FAILURE"
] | [2026-09-23 01:26:28 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-23 01:21:02 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-23 00:55:34 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
... | 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.... | # Incident architectural state during Issues with 1.1.1.1 for Families
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/rcjbfb0lyn65 | {
"raw_id": "rcjbfb0lyn65",
"status": "resolved",
"resolved_at": "2026-09-23T01:26:28.629Z"
} |
INC-2026-CLOUDFLARE-zpkwd9fx | Cloudflare | 2026-09-22T00:00:00 | Network Performance Issues in Taipei | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during Network Performance Issues in Taipei
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/zpkwd9fxsby5 | {
"raw_id": "zpkwd9fxsby5",
"status": "resolved",
"resolved_at": "2026-09-22T21:41:05.884Z"
} |
INC-2026-CLOUDFLARE-c2f7zj7f | Cloudflare | 2026-09-22T00:00:00 | Bot Management Configuration Propagation Issues | MEDIUM | [
"Bot Management",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [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.
[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... | 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 issu... | # Incident architectural state during Bot Management Configuration Propagation Issues
service_cluster:
provider: "Cloudflare"
impacted_components: ["Bot Management", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/c2f7zj7fs8l8 | {
"raw_id": "c2f7zj7fs8l8",
"status": "resolved",
"resolved_at": "2026-09-22T16:35:19.676Z"
} |
INC-2026-CLOUDFLARE-pvvq3811 | Cloudflare | 2026-09-22T00:00:00 | Elevated error rates for Stream Live LL-HLS | MEDIUM | [
"Stream",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"API_ERROR_SPIKE"
] | [2026-09-22 15:38:50 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-22 14:44:18 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-22 14:37:45 UTC] Cloudflare SRE (Investigating): We are investigating an issue where some Stream Live custom... | 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. | # Incident architectural state during Elevated error rates for Stream Live LL-HLS
service_cluster:
provider: "Cloudflare"
impacted_components: ["Stream", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/pvvq3811tpyq | {
"raw_id": "pvvq3811tpyq",
"status": "resolved",
"resolved_at": "2026-09-22T15:38:50.535Z"
} |
INC-2026-CLOUDFLARE-z84lp04f | Cloudflare | 2026-09-22T00:00:00 | Connectivity issues in Los Angeles (LAX) | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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 tra... | 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 ad... | # Incident architectural state during Connectivity issues in Los Angeles (LAX)
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/z84lp04f9sht | {
"raw_id": "z84lp04f9sht",
"status": "resolved",
"resolved_at": "2026-09-22T14:49:00.000Z"
} |
INC-2026-CLOUDFLARE-dcmwvjwf | Cloudflare | 2026-09-22T00:00:00 | Partial visibility of Workers and Durable Objects analytics for Fedramp High customers | MEDIUM | [
"Analytics",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"API_ERROR_SPIKE"
] | [2026-09-22 12:51:46 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-22 10:08:10 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-22 09:36:11 UTC] Cloudflare SRE (Identified): Cloudflare is monitoring the restoration of Workers and Durabl... | 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 remain... | # Incident architectural state during Partial visibility of Workers and Durable Objects analytics for Fedramp High customers
service_cluster:
provider: "Cloudflare"
impacted_components: ["Analytics", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold:... | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/dcmwvjwfyhjg | {
"raw_id": "dcmwvjwfyhjg",
"status": "resolved",
"resolved_at": "2026-09-22T12:51:46.718Z"
} |
INC-2026-CLOUDFLARE-g4vvd0xr | Cloudflare | 2026-09-22T00:00:00 | Network Performance Issues in San Jose (SJC-A) | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"QUEUE_DELAY",
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during Network Performance Issues in San Jose (SJC-A)
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/g4vvd0xrc2m8 | {
"raw_id": "g4vvd0xrc2m8",
"status": "resolved",
"resolved_at": "2026-09-22T08:20:00.000Z"
} |
INC-2026-CLOUDFLARE-nhf2kr8q | Cloudflare | 2026-09-22T00:00:00 | Network connectivity issues in LHR, London | MEDIUM | [
"London, United Kingdom - (LHR)",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"NETWORK_CONNECTIVITY"
] | [2026-09-22 03:36:56 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-22 02:26:27 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
[2026-09-22 02:25:45 UTC] Cloudflare SRE (Investigating): Cloudflare is observing network connectivity issues in LHR,... | 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 | # Incident architectural state during Network connectivity issues in LHR, London
service_cluster:
provider: "Cloudflare"
impacted_components: ["London, United Kingdom - (LHR)", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/nhf2kr8q3nfw | {
"raw_id": "nhf2kr8q3nfw",
"status": "resolved",
"resolved_at": "2026-09-22T03:36:56.633Z"
} |
INC-2026-CLOUDFLARE-mrqb4d6q | Cloudflare | 2026-09-21T00:00:00 | Increased Cache Failures | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during Increased Cache Failures
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/mrqb4d6q0y26 | {
"raw_id": "mrqb4d6q0y26",
"status": "resolved",
"resolved_at": "2026-09-21T18:15:16.618Z"
} |
INC-2026-CLOUDFLARE-rxmmx07y | Cloudflare | 2026-09-21T00:00:00 | Unable to start containers in Asia-Pacific | MEDIUM | [
"Containers",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [2026-09-21 13:23:38 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-21 13:21:57 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-21 13:15:02 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
... | 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 | # Incident architectural state during Unable to start containers in Asia-Pacific
service_cluster:
provider: "Cloudflare"
impacted_components: ["Containers", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/rxmmx07ys7qg | {
"raw_id": "rxmmx07ys7qg",
"status": "resolved",
"resolved_at": "2026-09-21T13:23:38.015Z"
} |
INC-2026-CLOUDFLARE-lb5514cv | Cloudflare | 2026-09-21T00:00:00 | Unable to register certain domains | MEDIUM | [
"Registrar",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"PIPELINE_EXECUTION_FAILURE",
"STORAGE_SUBSYSTEM"
] | [2026-09-21 09:49:13 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[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):
"audio", "baby", "build", "cam", "ceo", "christmas", "college", "dealer", "d... | 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):
"audio", "baby", "build", "cam", "ceo", "christmas", "college", "dealer", "diet", "fans", "flowers", "fm", "game", "... | # Incident architectural state during Unable to register certain domains
service_cluster:
provider: "Cloudflare"
impacted_components: ["Registrar", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/lb5514cvngd7 | {
"raw_id": "lb5514cvngd7",
"status": "resolved",
"resolved_at": "2026-09-21T09:49:13.586Z"
} |
INC-2026-CLOUDFLARE-3rjsfq4q | Cloudflare | 2026-09-19T00:00:00 | Elevated errors in Ashburn, VA (IAD) | MEDIUM | [
"Network",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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 res... | # Incident architectural state during Elevated errors in Ashburn, VA (IAD)
service_cluster:
provider: "Cloudflare"
impacted_components: ["Network", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/3rjsfq4q663b | {
"raw_id": "3rjsfq4q663b",
"status": "resolved",
"resolved_at": "2026-09-19T01:36:49.241Z"
} |
INC-2026-CLOUDFLARE-3czg2lc9 | Cloudflare | 2026-09-18T00:00:00 | Network Performance Issues in Ashburn | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during Network Performance Issues in Ashburn
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/3czg2lc9y1t8 | {
"raw_id": "3czg2lc9y1t8",
"status": "resolved",
"resolved_at": "2026-09-18T17:15:12.000Z"
} |
INC-2026-CLOUDFLARE-jds6b1j6 | Cloudflare | 2026-09-18T00:00:00 | Cloudflare Dashboard Workers KV Issue | MEDIUM | [
"Dashboard",
"Workers KV",
"Cloudflare Edge",
"DNS"
] | [
"INFRASTRUCTURE_DEGRADATION",
"SERVICE_OUTAGE"
] | [2026-09-18 08:15:41 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-18 08:04:48 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-18 07:24:20 UTC] Cloudflare SRE (Identified): The issue has been identified and a fix is being implemented.
... | 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 att... | # Incident architectural state during Cloudflare Dashboard Workers KV Issue
service_cluster:
provider: "Cloudflare"
impacted_components: ["Dashboard", "Workers KV", "Cloudflare Edge", "DNS"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/jds6b1j6dj8q | {
"raw_id": "jds6b1j6dj8q",
"status": "resolved",
"resolved_at": "2026-09-18T08:15:41.658Z"
} |
INC-2026-CLOUDFLARE-n3n98pb4 | Cloudflare | 2026-09-17T00:00:00 | Increased Errors for Durable Objects and Downstream Services in Asia Pacific (APAC) Region | MEDIUM | [
"AI Search",
"Artifacts",
"Containers",
"D1"
] | [
"API_ERROR_SPIKE"
] | [2026-09-18 00:54:03 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-18 00:45:48 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-17 23:37:18 UTC] Cloudflare SRE (Investigating): Cloudflare is investigating an issue causing elevated error... | 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 m... | # Incident architectural state during Increased Errors for Durable Objects and Downstream Services in Asia Pacific (APAC) Region
service_cluster:
provider: "Cloudflare"
impacted_components: ["AI Search", "Artifacts", "Containers", "D1"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_thresh... | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/n3n98pb4x9f4 | {
"raw_id": "n3n98pb4x9f4",
"status": "resolved",
"resolved_at": "2026-09-18T00:54:03.781Z"
} |
INC-2026-CLOUDFLARE-823rbdm2 | Cloudflare | 2026-09-17T00:00:00 | Replicate Pruna issue | MEDIUM | [
"Replicate",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"QUEUE_DELAY"
] | [2026-09-17 21:51:43 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[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. | 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. | # Incident architectural state during Replicate Pruna issue
service_cluster:
provider: "Cloudflare"
impacted_components: ["Replicate", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/823rbdm2k25x | {
"raw_id": "823rbdm2k25x",
"status": "resolved",
"resolved_at": "2026-09-17T21:51:43.704Z"
} |
INC-2026-CLOUDFLARE-l3t86mb1 | Cloudflare | 2026-09-17T00:00:00 | Network Performance Issues in Vancouver, Canada | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during Network Performance Issues in Vancouver, Canada
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/l3t86mb1xdxc | {
"raw_id": "l3t86mb1xdxc",
"status": "resolved",
"resolved_at": "2026-09-17T20:42:03.416Z"
} |
INC-2026-CLOUDFLARE-rhmpng7k | Cloudflare | 2026-09-17T00:00:00 | Network Performance Issues in Ashburn, VA, United States | MEDIUM | [
"Ashburn, VA, United States - (IAD)",
"Cloudflare Edge",
"DNS",
"WAF"
] | [
"NETWORK_CONNECTIVITY"
] | [2026-09-17 19:58:13 UTC] Cloudflare SRE (Resolved): This incident has been resolved.
[2026-09-17 18:32:36 UTC] Cloudflare SRE (Monitoring): A fix has been implemented and we are monitoring the results.
[2026-09-17 18:29:43 UTC] Cloudflare SRE (Investigating): Cloudflare identified an issue affecting network performanc... | 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. | # Incident architectural state during Network Performance Issues in Ashburn, VA, United States
service_cluster:
provider: "Cloudflare"
impacted_components: ["Ashburn, VA, United States - (IAD)", "Cloudflare Edge", "DNS", "WAF"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/rhmpng7klcqw | {
"raw_id": "rhmpng7klcqw",
"status": "resolved",
"resolved_at": "2026-09-17T19:58:13.245Z"
} |
INC-2026-CLOUDFLARE-83kl8stz | Cloudflare | 2026-09-17T00:00:00 | Increased HTTP Errors in GIG (Rio de Janeiro) | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"NETWORK_CONNECTIVITY"
] | [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. | 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. | # Incident architectural state during Increased HTTP Errors in GIG (Rio de Janeiro)
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/83kl8stzw5zn | {
"raw_id": "83kl8stzw5zn",
"status": "resolved",
"resolved_at": "2026-09-17T14:00:00.000Z"
} |
INC-2026-CLOUDFLARE-k4crxsx8 | Cloudflare | 2026-09-16T00:00:00 | Hyperdrive Elevated Origin Connection Failure Rates | MEDIUM | [
"Cloudflare Edge",
"DNS",
"WAF",
"Workers"
] | [
"DATABASE_DEGRADATION",
"NETWORK_CONNECTIVITY"
] | [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.
... | 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 n... | # Incident architectural state during Hyperdrive Elevated Origin Connection Failure Rates
service_cluster:
provider: "Cloudflare"
impacted_components: ["Cloudflare Edge", "DNS", "WAF", "Workers"]
health_check_status: DEGRADED
circuit_breaker: OPEN
observed_error_threshold: 0.05 | # Remediation mitigation applied by Cloudflare SRE
deployment_mitigation:
action: "Drain degraded node pool and scale healthy replicas"
traffic_rerouting: ENABLED
rate_limiting_tier: STRICT
status: RESOLVED | [
"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"
] | https://www.cloudflarestatus.com/incidents/k4crxsx8xk36 | {
"raw_id": "k4crxsx8xk36",
"status": "resolved",
"resolved_at": "2026-09-16T22:30:00.000Z"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.