If you are visiting a website and it is displaying “502 Bad Gateway” error it is not your fault but an issue with Cloudflare.
Update: July 12th, 2019 – Cloudflare has published a detailed report explaining why the service went down. While Cloudflare’s transparency is exemplary, other companies should follow the same path. Cloudflare’s report is available here.
Cloudflare, the world’s largest “Content Delivery Network” (CDN) on the internet has suffered a service disruption causing “502 Bad Gateway” error on thousands of Cloudflare-proxied domains since this morning including CoinDesk. On the other hand, CoinDesk confirmed in a tweet that their website has been down due to Cloudfare outage.
ALERT: Due to a cloudflare outage, we're getting bad data from our providers, which is showing incorrect crypto prices. Calm down everyone, Bitcoin is not $26.
— CoinDesk (@coindesk) July 2, 2019
Cloudflare provides security and other services to over 16 million online businesses. The problem surfaced at 1342 UTC today when users took it to social media complaining that they couldn’t access several websites including Down Detector, a service that keeps track of online platforms facing connectivity issues.
Who detects when the down detector is down? 🤔
— Jake (@0xJAKE) July 2, 2019
Although, the issue has now been resolved, earlier, Cloudflare confirmed on its status page that there were “performance problems” on the network which were being investigated. Furthermore, in a blog post, Cloudflare’s CTO John Graham-Cumming blamed the outage on bad software deploy.
“For about 30 minutes today, visitors to Cloudflare sites received 502 errors (502 Bad Gateway) caused by a massive spike in CPU utilization on our network.”
“This CPU spike was caused by a bad software deploy that was rolled back. Once rolled back the service returned to normal operation and all domains using Cloudflare returned to normal traffic levels. This was not an attack (as some have speculated) and we are incredibly sorry that this incident occurred. Internal teams are meeting as I write performing a full post-mortem to understand how this occurred and how we prevent this from ever occurring again,” wrote Cumming.
Appear to have mitigated the issue causing the outage. Traffic restored. Working now to restore all services globally. More details to come as we have them.
— Matthew Prince 🌥 (@eastdakota) July 2, 2019
At the time of publishing this article; the issue was successfully resolved however the list of countries affected by the outage is still available on Cloudflare’s status page.