2026-08-25 10:31 UTCIncidents Detected

Cloudflare CDN Latency Ongoing

No internet-wide disruption today. Two provider incidents are worth knowing about, one still open and one recovering.

Cloudflare — increased CDN latency (ongoing, minor). Cloudflare opened an incident at 20:38 UTC on August 24 for latency increases affecting a subset of requests through its CDN/Cache service. The cause was identified by 22:24 UTC and a fix was being implemented; as of 08:50 UTC today the incident is still marked Identified with the fix in progress, so it has been open for roughly 14 hours. Cloudflare rates the impact as minor and there is no sign of widespread reachability failures — this is slower responses for some requests, not sites going dark. Source: https://www.cloudflarestatus.com/

DigitalOcean — Cloud Control Panel and API outage (recovering). Starting 17:14 UTC on August 24, DigitalOcean's public API returned elevated 5xx errors for all requests and cloud.digitalocean.com was unreachable for many users; Serverless Inference users also saw 403 and 503 errors. A mitigation at 19:14 UTC restored access, but the problem recurred at 22:27 UTC with elevated latency and intermittent errors. A further mitigation at 00:54 UTC today restored the panel and API, and the incident remains in monitoring. This was a control-plane outage: customers could not manage or create resources, but existing Droplets and workloads kept running. Source: https://status.digitalocean.com/

Recently resolved (past 72 hours):

Anthropic: a major incident with elevated errors on Claude Mythos 5, Fable 5 and Opus 5 ran from about 05:00 to 08:30 UTC on August 24 and cascaded downstream — GitHub Copilot and Cursor both logged degraded Claude model availability in the same window. Resolved. https://status.claude.com/

GitHub: Actions run-start delays on August 24 (3.8% of runs delayed more than 5 minutes, 1.25% failed outright), caused by a disk failure on a service node; resolved 14:04 UTC. https://www.githubstatus.com/

Akamai: edge delivery issues in India from August 22 to 24, attributed to a third-party connectivity provider; resolved 18:50 UTC on August 24. A separate reporting-data issue affecting the "Traffic by Hostname" report is still under mitigation. https://www.akamaistatus.com/

Zoom: short meeting-chat and AI API degradations on August 24, each resolved within about an hour.

Still open but narrow: Slack continues to work through an incident that began August 13 in which workspaces with custom data-retention policies could not load older messages; retention jobs are being gradually restored from backups. Twilio is tracking SMS delivery delays to several individual carriers (Costa Rica, Dominican Republic, El Salvador, Kosovo, and some small US carriers) — carrier-side issues affecting delivery to those networks only.

All clear at AWS, Google Cloud, Microsoft Azure, Azure DevOps, OpenAI, Discord, Atlassian, Vercel, Heroku, Stripe, and the AI platforms we checked (Cursor, Groq, Replicate, ElevenLabs, Cohere, Stability AI). Meta's products are operating normally. Crowd-sourced outage trackers show no elevated reports for any major platform, and we found no BGP, DNS or undersea-cable incidents today.

Overall status: incidents detected — none widespread.

← Home View all history

Cloudflare CDN Latency Ongoing

Last 30 Days