If you are wondering if a kill switch exists, we may have just seen evidence that the same thing could be accomplished by whatever it was that happened to Cloudflare on Tuesday morning when literally millions of websites just would not come up. Among those were SonsOfLibertyMedia.com.
For about 30 minutes sites throughout the US and around the world simple went down.
— Russian Gryphon🔞 (@SpottySTC) June 24, 2019
Trending: Islam in America’s Schools: The Plan
— Jamie McGrory (@jmcgroryuk) July 2, 2019
— Alvin Wong (@alvinwong_1234) July 2, 2019
The full list of areas affected were:
“North America (Ashburn, VA, United States – (IAD), Atlanta, GA, United States – (ATL), Boston, MA, United States – (BOS), Buffalo, NY, United States – (BUF), Calgary, AB, Canada – (YYC), Charlotte, NC, United States – (CLT), Chicago, IL, United States – (ORD), Columbus, OH, United States – (CMH), Dallas, TX, United States – (DFW), Denver, CO, United States – (DEN), Detroit, MI, United States – (DTW), Houston, TX, United States – (IAH), Indianapolis, IN, United States – (IND), Jacksonville, FL, United States – (JAX), Kansas City, MO, United States – (MCI), Las Vegas, NV, United States – (LAS), Los Angeles, CA, United States – (LAX), McAllen, TX, United States – (MFE), Memphis, TN, United States – (MEM), Miami, FL, United States – (MIA), Minneapolis, MN, United States – (MSP), Montgomery, AL, United States – (MGM), Montréal, QC, Canada – (YUL), Nashville, TN, United States – (BNA), Newark, NJ, United States – (EWR), Norfolk, VA, United States – (ORF), Omaha, NE, United States – (OMA), Phoenix, AZ, United States – (PHX), Pittsburgh, PA, United States – (PIT), Portland, OR, United States – (PDX), Queretaro, MX, Mexico – (QRO), Richmond, Virginia – (RIC), Sacramento, CA, United States – (SMF), Salt Lake City, UT, United States – (SLC), San Diego, CA, United States – (SAN), San Jose, CA, United States – (SJC), Saskatoon, SK, Canada – (YXE), Seattle, WA, United States – (SEA), St. Louis, MO, United States – (STL), Tampa, FL, United States – (TPA), Toronto, ON, Canada – (YYZ), Vancouver, BC, Canada – (YVR), Tallahassee, FL, United States – (TLH), Winnipeg, MB, Canada – (YWG)), Asia (Bangkok, Thailand – (BKK), Cebu, Philippines – (CEB), Chengdu, China – (CTU), Chennai, India – (MAA), Colombo, Sri Lanka – (CMB), Dongguan, China – (SZX), Foshan, China – (FUO), Fuzhou, China – (FOC), Guangzhou, China – (CAN), Hangzhou, China – (HGH), Hanoi, Vietnam – (HAN), Hengyang, China – (HNY), Ho Chi Minh City, Vietnam – (SGN), Hong Kong – (HKG), Hyderabad, India – (HYD), Islamabad, Pakistan – (ISB), Jinan, China – (TNA), Karachi, Pakistan – (KHI), Kathmandu, Nepal – (KTM), Kuala Lumpur, Malaysia – (KUL), Lahore, Pakistan – (LHE), Langfang, China – (NAY), Luoyang, China – (LYA), Macau – (MFM), Manila, Philippines – (MNL), Mumbai, India – (BOM), Nanning, China – (NNG), New Delhi, India – (DEL), Osaka, Japan – (KIX), Phnom Penh, Cambodia – (PNH), Qingdao, China – (TAO), Seoul, South Korea – (ICN), Shanghai, China – (SHA), Shenyang, China – (SHE), Shijiazhuang, China – (SJW), Singapore, Singapore – (SIN), Suzhou, China – (SZV), Taipei – (TPE), Tianjin, China – (TSN), Tokyo, Japan – (NRT), Ulaanbaatar, Mongolia – (ULN), Wuhan, China – (WUH), Wuxi, China – (WUX), Xi’an, China – (XIY), Yerevan, Armenia – (EVN), Zhengzhou, China – (CGO), Zuzhou, China – (CSX)), Africa (Cairo, Egypt – (CAI), Casablanca, Morocco – (CMN), Cape Town, South Africa – (CPT), Dar Es Salaam, Tanzania – (DAR), Djibouti City, Djibouti – (JIB), Durban, South Africa – (DUR), Johannesburg, South Africa – (JNB), Lagos, Nigeria – (LOS), Luanda, Angola – (LAD), Maputo, MZ – (MPM), Mombasa, Kenya – (MBA), Port Louis, Mauritius – (MRU), Réunion, France – (RUN), Kigali, Rwanda – (KGL)), Oceania (Auckland, New Zealand – (AKL), Brisbane, QLD, Australia – (BNE), Melbourne, VIC, Australia – (MEL), Perth, WA, Australia – (PER), Sydney, NSW, Australia – (SYD)), Latin America & the Caribbean (Asunción, Paraguay – (ASU), Bogotá, Colombia – (BOG), Buenos Aires, Argentina – (EZE), Curitiba, Brazil – (CWB), Fortaleza, Brazil – (FOR), Lima, Peru – (LIM), Medellín, Colombia – (MDE), Mexico City, Mexico – (MEX), Panama City, Panama – (PTY), Porto Alegre, Brazil – (POA), Quito, Ecuador – (UIO), Rio de Janeiro, Brazil – (GIG), São Paulo, Brazil – (GRU), Santiago, Chile – (SCL), Willemstad, Curaçao – (CUR)), Middle East (Amman, Jordan – (AMM), Baghdad, Iraq – (BGW), Baku, Azerbaijan – (GYD), Beirut, Lebanon – (BEY), Doha, Qatar – (DOH), Dubai, United Arab Emirates – (DXB), Kuwait City, Kuwait – (KWI), Manama, Bahrain – (BAH), Muscat, Oman – (MCT), Ramallah – (ZDM), Riyadh, Saudi Arabia – (RUH), Tel Aviv, Israel – (TLV)), and Europe (Amsterdam, Netherlands – (AMS), Athens, Greece – (ATH), Barcelona, Spain – (BCN), Belgrade, Serbia – (BEG), Berlin, Germany – (TXL), Brussels, Belgium – (BRU), Bucharest, Romania – (OTP), Budapest, Hungary – (BUD), Chișinău, Moldova – (KIV), Copenhagen, Denmark – (CPH), Dublin, Ireland – (DUB), Düsseldorf, Germany – (DUS), Edinburgh, United Kingdom – (EDI), Frankfurt, Germany – (FRA), Geneva, Switzerland – (GVA), Gothenburg, Sweden – (GOT), Hamburg, Germany – (HAM), Helsinki, Finland – (HEL), Istanbul, Turkey – (IST), Kyiv, Ukraine – (KBP), Lisbon, Portugal – (LIS), London, United Kingdom – (LHR), Luxembourg City, Luxembourg – (LUX), Madrid, Spain – (MAD), Manchester, United Kingdom – (MAN), Marseille, France – (MRS), Milan, Italy – (MXP), Moscow, Russia – (DME), Munich, Germany – (MUC), Nicosia, Cyprus – (LCA), Oslo, Norway – (OSL), Paris, France – (CDG), Prague, Czech Republic – (PRG), Reykjavík, Iceland – (KEF), Riga, Latvia – (RIX), Rome, Italy – (FCO), Saint Petersburg, Russia – (LED), Sofia, Bulgaria – (SOF), Stockholm, Sweden – (ARN), Tallinn, Estonia – (TLL), Thessaloniki, Greece – (SKG), Vienna, Austria – (VIE), Vilnius, Lithuania – (VNO), Warsaw, Poland – (WAW), Zagreb, Croatia – (ZAG), Zürich, Switzerland – (ZRH)).”
According to Cloudflare CEO Matthew Prince, “Aware of major Cloudflare issues impacting us network wide. Team is working on getting to the bottom of what’s going on. Will continue to update.”
Aware of major @Cloudflare issues impacting us network wide. Team is working on getting to the bottom of what’s going on. Will continue to update.
— Matthew Prince 🌥 (@eastdakota) July 2, 2019
Data Center Dynamics added:
Network services provider Cloudflare is down for the majority of its users, bringing services like Discord, Marketo, Down Detector and DigitalOcean offline.
The full cause of the outage is unknown, with Cloudflare’s support page simply noting: “Cloudflare is observing network performance issues. Customers may be experiencing 502 errors while accessing sites on Cloudflare.
“We are working to mitigate impact to Internet users in this region.”
Update, 14:15 UTC: “Cloudflare has implemented a fix for this issue and is currently monitoring the results.
“We will update the status once the issue is resolved.”
Update, 14:45 UTC: Services appear to be resuming. Cloudflare notes, however, that “Cloudflare Analytics processing is running behind. This affects timely delivery of customer data.
“We are working to mitigate impact.”
Update, 14:50 UTC:
Cloudflare explains: “We saw a massive spike in CPU that caused primary and secondary systems to fall over. We shut down the process that was causing the CPU spike. Service restored to normal within ~30 minutes. We’re now investigating the root cause of what happened.”
Update, 14:57 UTC:
“Cloudflare has resolved the issue and services have resumed normal operation.”
According to DigitalAttackMap, there was a lot of activity on the 1st, just ahead of Cloudflare tanking.
This is the second time in two weeks this has occurred. Again, from Data Center Dynamics:
A similar problem happened just last week, when Cloudflare was unavailable for roughly 1hr 42m.
That time, Cloudflare noted that the downtime was not its fault: “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.
“BGP acts as the backbone of the Internet, routing traffic through Internet transit providers and then to services like Cloudflare. There are more than 700k routes across the Internet. By nature, route leaks are localized and can be caused by error or through malicious intent. We’ve written extensively about BGP and how we’ve adopted RPKI to help further secure it.”
In a blog post for DCD, Alex Henthorne-Iwane, of network monitoring company ThousandEyes, explained: “Route leaks happen fairly regularly. Routing is complicated. Humans make configuration errors, as we saw with the MainOne Nigerian ISP route leak that caused the global rerouting of some of Google’s traffic. And sometimes automation systems can trigger service disruptions, as we saw in the recent Google outage.”
Both ThousandEyes and Cloudflare pointed the blame at Verizon. Henthorne-Iwane said: “The fact that Verizon accepted and propagated a huge set of leaked routes from a downstream enterprise eyeball network turned what could have been an isolated issue into a significant outage.
“There has been some heated commentary on this topic from Cloudflare and other Internet observers, who have commented that Verizon should have caught this issue with one of multiple possible filtering mechanisms. Those critiques are more than fair on their face.”
This time around, however, it is unclear what was the cause of the outage.
Fortunately, things are back to normal, for the time being.
Become an insider!
Sign up to get breaking alerts from Sons of Liberty Media.