Skip to main content

Discord was down due to Cloudflare and Verizon issues

Discord was down due to Cloudflare and Verizon issues

/

Cloudflare had to deal with Verizon creating a mess

Share this story

Photo by Amelia Holowaty Krales / The Verge

Popular chat service Discord experienced issues today due to network problems at Cloudflare and a wider internet issue caused by Verizon. The app was inaccessible for its millions of users, and even Discord’s website and status pages were struggling. Discord’s problems could be traced to problems at Cloudflare, a content delivery network. Cloudflare started experiencing issues at 7:43AM ET, and this caused Discord, Feedly, Crunchyroll, and many other sites that rely on its services to have partial outages.

Cloudflare said it was working on a “possible route leak” affecting some of its network, but services like Discord were inaccessible for more than an hour. “Discord is affected by the general internet outage,” said a Discord statement on the company’s status site. “Hang tight. Pet your cats.”

While Cloudflare didn’t originally name the network involved, Cloudflare’s CEO took to Twitter to blast Verizon for the issues. “The teams at Verizon and Noction should be incredibly embarrassed at their failings this morning which impacted Cloudflare and other large chunks of the Internet,” said Matthew Prince, Cloudflare CEO. “It’s absurd BGP is so fragile. It’s more absurd Verizon would blindly accept routes without basic filters.”

Cloudfare explained the outage in an additional statement, commenting that “Earlier today, a widespread BGP routing leak affected a number of Internet services and a portion of traffic to Cloudflare. All of Cloudflare’s systems continued to run normally, but traffic wasn’t getting to us for a portion of our domains. At this point, the network outage has been fixed and traffic levels are returning to normal.”

Update, June 24th 5PM ET: Article updated with more information from Cloudflare about the general route leak. Added additional statement from Cloudflare, and Cloudflare’s CEO explaining the outage.