Hacker News Reader

Not even the fact that it's simple - it's the obvious and de facto way that a status page should be run: an architecture that is entirely separate from the main product so that an outage of the main service doesn't affect the status page itself

Part of the company culture is managers forcing the engineers to use the technology built in-house, even when it's not appropriate.

Which seems to be a rather common trait for the bigger tech companies.

So far looks like some internal DNS issue, so unsure how your comment is relevant.