Provider trouble · Oct 22, 2026
12 companies' status pages showed trouble at Cloudflare
The first page showed it at Oct 22, 16:30 UTC, the last 34 minutes later. No company wrote about it in its own words; 12 pages carried Cloudflare's own status showing trouble.
Cloudflare posted on its own status page at 15:33 UTC, 57 minutes before the first company.
671 companies in our directory rely on Cloudflare.
When they first posted
Companies by when their status page first showed it, 10 minutes a column. The most, 10, in Oct 22, 17:00–17:10 UTC.
What they said
Quoted from their status pages. Times are UTC.
Cloudflare's own status, shown on their pages
Parts on these companies' status pages that carry Cloudflare's status, showing it in trouble. They repeat Cloudflare rather than report in their own words.
- CloudCannon: “Analytics / Cloudflare Cloudflare Logs: degraded”
- Expo: “Third-Party Services / Cloudflare Logs: degraded”
- Doppler: “Vendors / Cloudflare Cloudflare Workers: degraded”
- Anaconda: “Cloudflare Ashburn, VA, United States - (IAD): degraded”
- ReadMe: “Upstream Providers / Cloudflare CDN/Cache: degraded”
- Gather: “Cloudflare (third party) / Cloudflare CDN/Cache: degraded”
- CodeSignal: “Cloudflare CDN/Cache: degraded”
- Kilo: “Service Provider / Cloudflare Workers: degraded”
- Marketplacer: “Cloudflare CDN/Cache: degraded”
- Gusto: “Provider: Cloudflare / Cloudflare CDN/Cache: degraded”
- Instapage: “Cloudflare / Cloudflare CDN/Cache: degraded”
- Released: “Cloudflare CDN/Cache: degraded”
Find out when the next one touches your vendors
Start with your domain. We read its DNS for the services it uses, you add the rest of your vendors, and we email you when one of them posts trouble on its status page, or when trouble like this reaches them.
Start with your domainMore moments
Caught as it happened, by reading companies' status pages. Status pages say what each company chose to post; a company not listed may have had the same trouble and said nothing.