Outages and root causes.

Two years of public outages, and what each company said caused them. Every entry links to the company's own write-up; nothing here is our speculation.

Status pages re-read 18 min ago

Incidents with a published root cause

By month, last two years · Cloudflare

Peak 0 · December 2024

  • Total: 0
  • December 2024: 0
  • January 2025: 0
  • February 2025: 0
  • March 2025: 0
  • April 2025: 0
  • May 2025: 0
  • June 2025: 0
  • July 2025: 0
  • August 2025: 0
  • September 2025: 0
  • October 2025: 0
  • November 2025: 0
  • December 2025: 0
  • January 2026: 0
  • February 2026: 0
  • March 2026: 0
  • April 2026: 0
  • May 2026: 0
  • June 2026: 0
  • July 2026: 0
  • August 2026: 0
  • September 2026: 0
  • October 2026: 0
  • November 2026: 0
Incidents listed
0
With a published RCA
Official write-ups
0
Linked from the incident
Major outages
0
As graded by each company
Services
0
With at least one entry

Notable outages, summarised

Read from each company's published analysis and summarised in our own words. Follow the link for the full account.

  • Cloudflare

    Feb 20, 2026

    BYOIP prefixes unintentionally withdrawn

    Around a quarter of customer bring-your-own-IP prefixes were withdrawn from the internet, making affected customers' services on CDN, Spectrum, Magic Transit and Dedicated Egress unreachable; Cloudflare puts the incident at just over six hours.

    Root cause, as stated by Cloudflare

    A new automated cleanup task sent an API query with an empty parameter that the Addressing API interpreted as matching all BYOIP prefixes, so it began deleting them.

    Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

  • Cloudflare

    Dec 5, 2025

    HTTP 500 errors for about 28% of traffic

    Sites served through Cloudflare's older proxy with the managed WAF ruleset returned HTTP 500 errors for about 25 minutes, affecting roughly 28% of HTTP traffic.

    Root cause, as stated by Cloudflare

    Turning off an internal WAF testing tool through the global configuration system, as part of a request-body buffer increase, triggered a latent bug in the older proxy's rules module.

    Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

  • Cloudflare

    Nov 18, 2025

    Global network outage from oversized Bot Management file

    Cloudflare's core proxy returned 5xx errors for a large share of traffic worldwide, also breaking Turnstile, Workers KV, Access and dashboard logins. Main impact eased after about three hours and everything was normal after nearly six.

    Root cause, as stated by Cloudflare

    A database permissions change made a query emit duplicate rows, doubling the size of a Bot Management feature file beyond a hard limit in the proxy software, which then crashed.

    Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

  • Cloudflare

    Jun 12, 2025

    Workers KV failure takes down Access, WARP and more

    Workers KV failed almost completely for about two and a half hours, which cascaded into Access, WARP, Gateway, Turnstile, dashboard logins, Workers AI, Images and other products globally.

    Root cause, as stated by Cloudflare

    Part of the storage infrastructure behind Workers KV, hosted with a third-party cloud provider that had its own outage, failed and KV lacked sufficient redundancy to absorb it.

    Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

  • Cloudflare

    Mar 21, 2025

    R2 object storage write outage

    All writes and about a third of reads to R2 failed globally for a little over an hour. Products built on R2 were hit too: Images and Stream uploads failed and their delivery degraded, while Cache Reserve sent more requests back to customer origins.

    Root cause, as stated by Cloudflare

    During a credential rotation, the new credentials were deployed to the wrong environment, so the production R2 gateway lost access once the old credentials were removed.

    Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

  • Cloudflare

    Jun 20, 2024

    Elevated errors and latency across the CDN

    For just under two hours many Cloudflare data centers showed higher error rates and latency; during the half-hour peak, tail latency roughly tripled and around 2% of CDN requests got an error page.

    Root cause, as stated by Cloudflare

    Cloudflare cites two independent events: automated traffic re-routing briefly congested its backbone, and then, with larger effect, a newly deployed DDoS mitigation rule exposed a latent bug in the rate-limiting system that sent request-handling processes into an infinite loop.

    Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

From the status pages

With a published RCAPartial and major outagesBoth
RegionAnyus-east-1 52us-west-2 16us-central1 15eu-central-1 12me-central-1 9me-south-1 6eu-west-1 5us-east-2 5europe-west2 4ap-northeast-1 4europe-west4 4eu-west-2 3nam5 2ap-northeast-2 2ap-southeast-2 2eu-central-2 2eu-west-3 2us-east4 2ap-southeast-1 2sgp 1us-east1 1europe-west3 1us-west-1 1asia-southeast1 1us-south1 1us-east-01 1australia-southeast2 1northamerica-northeast1 1eu-south-1 1us-central-0 1

Showing incidents whose vendor named me-central-1. Incidents with no stated region are not included, though they may have affected it too.

All servicesPagerDuty 120Smartsheet 49SAP Concur 48Harness 48Sauce Labs 48Box 43Snowflake 40Kustomer 39Authorize.net 39KnowBe4 38Delinea 36Auvik 34Wasabi 26Onfido 23Linode (Akamai) 23Asana 20Bandwidth 19JumpCloud 18LiveKit 18Lever 17Google Workspace 17Jira 15Bitbucket 15Upstash 15Jira Service Management 15CircleCI 15Confluence 14Autodesk 14Keeper 13Close 131Password 13DocuSign 11Trello 11Yext 10InfluxDB Cloud 10Buildkite 8Google Cloud 7monday.com 7Duo Security 6imgix 6

Nothing matches these filters.

Who publishes root causes

Write-ups posted on status pages, last two years

  1. PagerDuty120
  2. Smartsheet49
  3. SAP Concur48
  4. Harness48
  5. Sauce Labs48
  6. Box43
  7. Snowflake40
  8. Kustomer39
  9. Authorize.net39
  10. KnowBe438
  11. Delinea36
  12. Auvik34

Public information only

Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.

Sources

  • Official status pages: incident titles, severity, times and the link to each published root-cause analysis, exactly as each company posted them
  • Company engineering blogs and incident reports: the basis for the notable-outage summaries, each linked from its card

How fresh it is

  • Incidents and RCA links: re-read from every status page about once an hour; last run 18 min ago
  • Notable-outage summaries: written by hand and last checked against their sources on Nov 10, 2026

Titles, severity and times are as published on each company's status page. "Published RCA" means the company posted a postmortem on that incident's official page; we link to it and do not reproduce it. Many companies publish root causes on a blog instead, or not at all, so the absence of a link is not evidence that no analysis exists. Severity grading differs between companies and is not comparable across them. This is not a complete record of every outage.

statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.