2026-09-10 13:44 UTCIncidents Detected

Copilot Outage Resolved

No widespread internet disruption today. The notable item is a Microsoft Copilot outage that ran overnight and has since been fixed.

Microsoft Copilot (resolved). The Copilot website was unreachable from 22:25 UTC on September 9 until 00:05 UTC on September 10, about an hour and 40 minutes. Users got a Cloudflare Error 1016 instead of the chat interface. Downdetector logged a peak of roughly 4,200 reports. Microsoft traced it to an affected network flow and applied a configuration fix. Separately, and at the same time, an internal Microsoft 365 resilience drill removed the suggested-prompt pills in Copilot Chat. Microsoft halted the drill once it spotted the impact. Both issues are resolved.

Still open, all minor:

Cloudflare has two low-impact incidents on its board: Workers Cron Triggers degraded (opened September 9, fix being implemented) and a WARP geolocation issue open since August 27. Scheduled datacenter maintenance is running in Amsterdam, Los Angeles, Phoenix and Saint Petersburg, which may add latency in those metros.

Twilio reports SMS delivery receipt delays from a subset of long codes to Iliad subscribers in Italy, opened this morning. Messages are being delivered; it is the receipts that lag. An MMS delay issue in Australia has been open since September 4.

OpenAI is monitoring recovery on a bug that blocked opening shared ChatGPT Projects from a direct link. Mitigation is applied. Core ChatGPT and API service is normal.

Slack still has an incident open since August 13 affecting workspaces with custom data retention policies, where older messages may fail to load.

Operating normally: AWS, Google Cloud, Microsoft Azure, Cloudflare core network, GitHub, Akamai, Anthropic, Discord, Atlassian, Zoom, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, Cohere and Stability AI. We found no BGP hijacks, route leaks or DNS failures of note.

Recently resolved (past 72 hours). AT&T had an internet disruption on September 7 that peaked near 5,900 reports and affected Dallas, Phoenix, New York, Philadelphia, Chicago and Los Angeles. AT&T attributed the Dallas portion to a fiber equipment issue and confirmed service returned to normal the same day. On September 4, GitHub resolved a Copilot code review failure and a repository contents API degradation, and Akamai resolved a load balancer issue plus an Atlanta network component failure that affected certificate provisioning.

A note on sources. Several search results circulating today describe Red Sea submarine cable cuts near Jeddah affecting the SMW4 and IMEWE systems. Those reports date from September 2025, not this week, and we found no evidence of a new break. AWS public RSS feed also continues to carry long-running Middle East regional entries that have not been updated in months, so treat that feed timestamps with care.

Overall: incidents detected, none widespread. The internet is up.

Sources: Microsoft Copilot outage coverage via The Register (theregister.com) and GV Wire (gvwire.com); AT&T via Newsweek (newsweek.com); provider status pages at https://www.cloudflarestatus.com/, https://status.twilio.com/, https://status.openai.com/, https://slack-status.com/, https://www.githubstatus.com/, https://www.akamaistatus.com/, https://status.cloud.google.com/ and https://azure.status.microsoft/.

← Home View all history

Copilot Outage Resolved

Last 30 Days