Hacker News Reader

Comment by aeyes | Hacker News Reader

Their comment regarding the late update here: https://news.ycombinator.com/item?id=23878496

> Because of the way we securely connect to StatusPage.io from most locations where our team is based. The traffic got blackholed in ATL, keeping us from updating it.

View on HN

Circular dependencies like this are not a good look when the core of your business is networking...

Yep, I was joking with our rep that them using Cloudflare Access for their internal services sounds like a problem waiting to happen.

Guess I wasn't wrong, they might even have lost access to internal monitoring systems which is pretty unfortunate in such a situation. If you ask them about Cloudflare Access they will happily tell you that it was built for internal tool access and that they use it for everything, later they went on to sell it as a product.

An example of dogfooding your own product is actually a bad idea?

While they could dogfood the product, status monitoring systems should be separated from your bread-and-butter product's failures. If you are in the business of messing with BGP, then the BGP that controls the routes that let you report outages should not be the same one you are messing with regularly, or at least, there should be redundancy.

When Google Cloud went down a few years ago, they were unable to access internal monitoring because the bad bgp change overloaded their networks if i remember correctly.

They could add a deadman switch to their status page.

A meta status page

Soon you'll need status pages for the status pages.

already exists ;)

https://metastatuspage.com/

(it's statuspage.io's status page)

Isn’t it status page 101 that you host it in the competition, so it stays up when you’re down? :-/

Reply on news.ycombinator.com