Cloudflare says it has resolved issues that caused outages at X, other apps

Cloudflare said it resolved an outage at 2:30 p.m. EST after a spike in “unusual traffic” beginning at 11:20 UTC caused widespread 500 errors that disrupted access to multiple customers—including X, League of Legends, Spotify, ChatGPT and others—with thousands of user reports on Downdetector; the company said services are now operating normally but the root cause remains unknown. As a provider of DNS and traffic-routing services that many platforms rely on, the incident—coming after a June Cloudflare glitch and recent prolonged outages at AWS and Azure—highlights concentration risk in internet infrastructure and the potential for cascading operational and economic impacts across dependent businesses.

Analysis

Cloudflare reported a resolved incident at 2:30 p.m. EST after a spike in "unusual traffic" beginning at 11:20 UTC produced widespread 500 errors that disrupted access to multiple customers including X, League of Legends, Spotify, ChatGPT and others, with thousands of user reports on Downdetector. The company stated services are operating normally and customer inquiry channels remain available, but it has not yet identified the root cause of the traffic spike.

Cloudflare's role as a DNS and traffic-routing provider means outages cascade to dependent platforms; this is the latest in a series of high-profile infrastructure failures following a June Cloudflare glitch and recent prolonged outages at Amazon Web Services and Microsoft Azure. Catchpoint's CEO highlighted that these incidents can produce cascading operational and economic impacts and underscore concentration risk in internet infrastructure.

For investors, the incident raises operational and reputational risk for Cloudflare (NET) and increases short-term volatility for major cloud-dependent platforms, while the unresolved root cause keeps recurrence risk elevated; key near-term indicators to watch are client churn, formal root-cause analysis, SLA credits, and any regulatory or contractual responses from large customers.

Key Decisions for Investors

• Temporarily reduce speculative exposure to Cloudflare (NET) or hedge positions until management publishes a clear root-cause analysis and quantifies customer impact and potential SLA liabilities
• Reassess portfolio concentration risk in companies that rely on single cloud/DNS providers and consider position sizing adjustments or hedges for names with high dependency on third-party routing services
• Monitor upcoming disclosures and customer-recovery metrics (client churn, credited refunds, contract renegotiations) for NET and major cloud providers as signals for long-term conviction,
• Expect near-term volatility in impacted platforms (AMZN, MSFT, GOOGL, SPOT) and use short-duration hedges or options to manage operational-risk-driven drawdowns rather than altering long-term fundamental positions