Cloudflare outage — June 8, 2026
GraphQL API rate limit errors
Cloudflare’s Multiple services was disrupted for 46d 10h on June 8, 2026.
Key facts
| Detected | June 8, 2026 · 05:57 UTC |
| Confirmed | 05:57 UTC |
| Resolved | 16:54 UTC |
| Duration | 46d 10h |
| Service | Multiple services |
| Official record | https://stspg.io/l3fxf4wvk7vl |
Timeline
- 05:57Z
Detected · Signal
7 crowd signals for Multiple services on CLOUDFLARE crossed the signal threshold. - 05:57Z
Confirmed · Official
An official CLOUDFLARE status-page notice corroborated the event the same cycle. - 16:54Z
Resolved
Signal volume fell back below the threshold; the event was closed.
What people reported
“After ONE email managed to get through, I still need the second one And the InPost app gived cloudflare error 520 - I KNEW IT WASN'T ME They're having server i”bluesky_jetstream · 05:41 UTC
“a good reminder to put my new 20gb(!) website behind cloudflare. I did also choose a host where if usage goes crazy it just slows down, rather than charges me.”bluesky_jetstream · 06:42 UTC
“Must be CloudFlare? PSN is down lol”bluesky_jetstream · 11:05 UTC
“ℹ️ Minor outage at Cloudflare impacting network performance in Western North America. Investigation is ongoing. Monitor this incident at https://watchrr.app/ser”bluesky_jetstream · 11:26 UTC
“Cloudflare is interested that such pages are reported to them, so they can take them down”bluesky_jetstream · 13:22 UTC
“ℹ️ Minor outage at Cloudflare impacting GraphQL API rate limits in analytics dashboards. Monitor this incident at https://watchrr.app/service/cloudflare”@watchrrnews.bsky.social · 14:09 UTC
How this was detected
1 independent evidence class for Multiple services on CLOUDFLARE. 7 crowd reports across bluesky (single platform — not corroborating), z=+1.7σ vs the cell baseline. Official notice confirms it.