A widespread internet disruption on Monday, June 22, 2026, left millions of users unable to access some of the world's most popular online platforms. Reports flooded in that X (formerly Twitter), Reddit, Fortnite, and Zoom were effectively unreachable, with thousands of complaints spiking on outage tracking services just before 3 p.m. Eastern Time. The culprit, according to early analysis by network monitoring firms, was a routing error at Zayo, a major internet backbone provider whose infrastructure carries a significant portion of global traffic.

The scale of the incident became apparent within minutes. Downdetector recorded over 50,000 reports for X alone in the first half hour, while Reddit, Fortnite, and Zoom each saw surges of tens of thousands of complaints. Users took to alternative platforms like Signal and Discord to ask a simple question: "Is the internet down?" The answer, it turned out, was not a simple yes or no. The internet was very much alive, but critical pathways that connect users to these services had been severed by a misconfiguration deep inside Zayo's network.

What Actually Happened

At the heart of the outage was a routing issue, a term that encompasses a range of technical failures but often boils down to one thing: data packets were sent down the wrong path. Service providers like Zayo maintain massive routing tables that tell network equipment how to forward traffic. When these tables contain incorrect information, traffic can be dropped, sent in loops, or directed into dead ends. Cloudflare, one of the world's largest content delivery and DNS providers, reported seeing a dramatic spike in network errors at the same time the outage reports began. The company's monitoring systems observed a sudden increase in timeouts and connection failures targeting the affected services.

Zayo operates one of the most extensive fiber optic networks globally, spanning over 18 million fiber miles and serving as a transit provider for countless ISPs, data centers, and cloud platforms. When a BGP (Border Gateway Protocol) misconfiguration or a faulty route advertisement occurs at such a critical juncture, the ripple effects can be immediate and severe. In this case, traffic destined for specific IP ranges belonging to X, Reddit, Fortnite servers, and Zoom's infrastructure was effectively blackholed, meaning it disappeared into a void and never reached its intended destination.

Ripple Effects Across Services

For the average user, the symptoms were unmistakable. Attempting to load a Reddit thread resulted in a blank page or a timeout error. X timelines refused to refresh, and direct messages failed to send. Fortnite players found themselves disconnected mid-match, with the game launcher showing server connection errors. Zoom meetings abruptly ended, disrupting businesses, online classes, and telehealth appointments. The outage underscored how deeply these platforms are woven into daily life; for many, it felt as though a vital utility had been shut off.

Businesses that rely on these platforms for customer engagement, marketing, and operations scrambled to communicate via alternative channels. Social media managers, unable to post updates on X or respond to customers on Reddit, turned to LinkedIn and Mastodon. Gamers vented on game-centric forums, while remote workers resorted to plain phone calls. The incident, while temporary, highlighted the fragility of an internet ecosystem where a single point of failure can cascade into a major disruption.

Cloudflare's Perspective

Cloudflare, which provides DNS, CDN, and DDoS protection services to many of the impacted companies, issued a statement confirming the external nature of the problem. "We are observing a significant increase in network errors to multiple destinations," the company noted on its public status page shortly after the outage began. "This is not an issue with Cloudflare's infrastructure but rather an upstream routing problem affecting connectivity." The company's own DNS resolver, 1.1.1.1, continued to function normally, but it could not help when data packets simply could not find a viable path after the DNS lookup had succeeded.

This distinction is crucial for troubleshooting. Many users, conditioned to think DNS is the first culprit in any connectivity problem, tried switching resolvers to Google's 8.8.8.8 or Cloudflare's 1.1.1.1, only to find the outage persisted. The issue was not about name resolution; it was about routing—the actual delivery of data. Cloudflare's monitoring provided a real-time view that pointed squarely at Zayo's network.

A Brief History of Routing Outages

The June 22 incident is the latest in a long line of high-profile routing disruptions. In 2021, a misconfiguration at Fastly, a CDN provider, knocked out Reddit, Twitch, Amazon, and the UK government's website for an hour. In 2020, a BGP leak by a small ISP led to a widespread Cloudflare outage. And in 2019, a similar incident involving a Russian ISP caused major disruptions across Europe. These events share a common thread: human error or software bugs in the complex system that governs how internet traffic flows.

The Border Gateway Protocol (BGP), the aged but essential glue of the internet, was designed in an era when trust among network operators was assumed. Despite decades of incremental improvements and the introduction of security mechanisms like RPKI (Resource Public Key Infrastructure), misconfigurations still happen. When they do, the impact can be global. In Zayo's case, the exact nature of the error—whether it was a faulty route leak, an accidental withdrawal, or an internal software bug—remains unclear, but the consequences were immediate and widespread.

How the Outage Was Resolved

According to multiple sources, Zayo's network engineering team identified the erroneous routing announcement and began rolling it back within 45 minutes of the first reports. Service restoration was gradual, as ISPs around the world picked up the corrected routes and traffic started flowing again. By 4:30 p.m. ET, most users reported that X, Reddit, Fortnite, and Zoom were accessible once more, though some lingering issues persisted for another hour as cached routes expired.

Zayo has not released a detailed post-mortem as of this writing, but industry experts expect the company to publish an incident report in the coming days. Such reports typically explain the sequence of events, the root cause, and the steps being taken to prevent recurrence. For customers and partners—which include many cloud providers and ISPs—the report will be essential reading.

What Windows Users Should Do During an Outage Like This

For the millions of Windows users who found themselves staring at error messages and buffering icons, the instinct to troubleshoot can be overwhelming. However, in the case of an internet-wide routing problem, no amount of rebooting routers or flushing DNS caches will help. The issue lies far beyond the home network. Still, there are steps Windows users can take to diagnose and mitigate the impact of such incidents.

First, use the built-in command-line tools to verify where the connection fails. Open Command Prompt or PowerShell and run tracert (trace route) to the affected service. For example, tracert reddit.com will show the path packets take. If the trace dies out after a specific hop, especially one belonging to a major transit provider like Zayo (look for domains ending in zayo.com or zayo.net), you can confirm the problem is external. Similarly, ping can show whether the destination is reachable, though many services block ICMP for security.

Second, check online status pages. Cloudflare's status page, Zayo's network status (if publicly available), and aggregator sites like Downdetector can provide real-time confirmation that the problem is widespread. Third, while changing DNS won't fix a routing issue, it's still good practice to have an alternative DNS configured. In Windows, you can set your preferred DNS server in the network adapter properties. During the outage, many users who relied on Cloudflare's 1.1.1.1 or Google's 8.8.8.8 found that at least DNS resolution worked, even if the subsequent routing failed. This turned out to be a useful diagnostic: if DNS worked but the site didn't load, it pointed to a routing problem.

Finally, Windows users should be aware of the concept of "network resilience." In the future, as the industry deploys stronger routing security measures like RPKI validation and BGP monitoring, such outages may become less frequent. Until then, patience and a basic understanding of internet plumbing can help avoid unnecessary frustration.

The Bigger Picture: Internet Infrastructure Still Fragile

The June 22 outage is a reminder that despite the internet's reputation as a decentralized, robust system, it still relies on a relatively small number of backbone providers. Zayo is one of them, alongside Lumen (formerly CenturyLink), Cogent, and NTT. When one of these giants hiccups, the impact can be enormous. The incident has renewed calls for greater investment in route filtering, automated anomaly detection, and faster propagation of route updates.

Security researchers have long warned that BGP is vulnerable to both accidents and malicious attacks. While RPKI adoption is growing, it is not yet universal. Until all major providers implement and enforce strict origin validation, the internet will remain susceptible to such disruptions. For now, the only certainty is that the next routing outage is not a matter of "if" but "when."