Hacker News Reader

Comment by llama052 | Hacker News Reader

We use Cloudflare to serve ~20-30TB of traffic a month where I work. Was the SRE on call when I got paged on our blackbox monitoring/third party web checks failing..

It was very pleasant to find the cloudflare status page pointing me to the issue right away (minutes after our alerts triggered), even though I couldn't replicate the issue myself yet.

I wish more companies would take note of the transparency and sense of urgency on updating their status page. (Looking at you Azure)

View on HN

Your experience is different to mine. Here in Australia the status page was inaccessible. Which immediately leads to common wisdom on monitoring systems - the monitor must always be separate to the monitored.

> Here in Australia the status page was inaccessible.

Me and a bunch of my colleagues were all able to access it (different ISPs) on the east coast.

It seemed like ISPs with east coast Vocus backhaul (going to SYD rather than MEL/PER POPs - TIL there's also CBR/BNE/ADL) had it worst trying to get to the status page but as the timeline shows, cloudflare was probably already recovering as we were triaging.

I was also able to access it, and my primary DNS was 1.1.1.1, though I use 8.8.8.8 as secondary so that might've saved me if primary wasn't working.

Also in Australia and had no issues with the status page from the very beginning of the outage.

Are you using Cloudflare DNS? I couldn't access it either during the outage and I just came to the realisation it might be because I switched to 1.1.1.1 a while ago.

Cloudflare's status page is one of the very few services of Cloudflare that are hosted elsewhere precisely for the reason it needs to be available if something isn't working.

> I wish more companies would take note of the transparency and sense of urgency on updating their status page.

Looking at you Twilio...

Looking at you, AWS

Looking at you zoom?

Reply on news.ycombinator.com