2026-08-28 09:12 UTCIncidents Detected

Twitch Outage Resolved Overnight

Early-day report (published 09:00 UTC). No internet-wide outage is in progress. The most notable event of the past 24 hours was a roughly six-hour disruption at Twitch, which has been resolved. A minor Cloudflare WARP issue remains open. Core cloud platforms, DNS, and global routing show no problems.

Twitch (resolved). Twitch confirmed an incident beginning at 20:09 UTC on August 27 in which chat, login, and search were impaired for many users; Downdetector reports climbed past 13,000 within minutes. A fix was implemented at 22:03 UTC and Twitch declared all known impact resolved at 02:31 UTC on August 28. Sources: https://status.twitch.com/ and https://gvwire.com/2026/08/27/twitch-down-for-thousands-of-users-downdetector-shows/

Cloudflare (minor, ongoing). Cloudflare is still working on a fix for incorrect geolocation affecting some WARP users, open since 18:46 UTC on August 27. Two other short incidents from yesterday, Turnstile challenge issues (resolved 19:29 UTC) and degraded Workers Builds (resolved 22:58 UTC), are closed. No Cloudflare data centers are marked degraded or re-routed. Source: https://www.cloudflarestatus.com/

Other items being tracked:

Akamai resolved a reporting-data issue at 03:30 UTC today; a separate data-availability problem in its Traffic by Hostname report, open since August 20, is still in monitoring. Neither affects content delivery. https://www.akamaistatus.com/

Zoom resolved a service degradation in Hong Kong yesterday (12:02 to 15:10 PDT). https://www.zoomstatus.com/

Twilio has six open carrier-level items: SMS delays to Megafon Tajikistan, Telefonica El Salvador, and I.C.E. Costa Rica; delivery-receipt delays to Liberty Puerto Rico; MMS delays to C-Spire in the US; and voice call issues to UK numbers. These are routine carrier-specific problems, not a platform outage. https://status.twilio.com/

Slack's issue with accessing historical messages in workspaces using custom data-retention policies, open since August 13, is still listed as unresolved. https://slack-status.com/

Crowd-sourced trackers show a modest rise in EA problem reports since about 00:45 UTC; EA has not confirmed an incident and the volume is small, so we are treating this as unconfirmed.

Recently resolved (past 72 hours). GitHub's three August 27 incidents (Copilot AI model providers, Actions and Pull Requests, and Billing) are all resolved and GitHub reports all systems operational today; its August 26 Actions incident (jobs failing to start from 15:02 to 15:45 UTC) was traced to database primary saturation. DigitalOcean's control panel and API 5xx errors (August 24 to 25) are resolved. Cursor's sign-in degradation on August 27 is resolved. Anthropic's August 24 elevated-error incidents are resolved. Google Cloud published its final incident report for the August 20 us-west1 (Oregon) degradation, attributing it to fiber maintenance that compromised inter-datacenter capacity when automated rerouting failed. https://www.githubstatus.com/ https://status.digitalocean.com/ https://status.cloud.google.com/

All clear today: AWS (apart from the long-running unavailability of the Middle East UAE and Bahrain regions dating to March), Google Cloud, Microsoft Azure, Azure DevOps, GitHub, OpenAI, Anthropic, Discord, Atlassian, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, Replicate, ElevenLabs, Cohere, and Stability AI all report normal operations. Meta's platforms are operating normally with user report volumes in the typical range. No BGP hijacks, leaks, or DNS root issues were reported.

Overall assessment: incidents detected, no widespread outage. This report was compiled early in the UTC day and reflects conditions as of 09:00 UTC.

← Home View all history

Twitch Outage Resolved Overnight

Last 30 Days