4 ms·
Seems pretty dumb to host a status page in a way that it could go down, when it should be a static page that is trivially hosted on CDN's worldwide.
by julianeon 6y ago
Seems pretty dumb to host a status page in a way that it could go down, when it should be a static page that is trivially hosted on CDN's worldwide.
- koolba 6y agoYou can’t cache it for that long though. A better approach is to have it hosted on a different cloud platform. If you really care, you’ll set it up on a different domain and nameserver as well with a long lived redirect (cached on CDNs) from the usual status.example.com or example.com/status.
- julianeon 6y agoThanks; you're right - the caching would be a problem, so your solution makes more sense.
- syshum 6y agoOver confident in their own Cloud "Our cloud can never go completely down We are IBM, we have Watson..."
- sky_rw 6y agoTheir status page also seems integrated into their internal support ticketing system. It's not a traditional status page. They wanted to maintain a consistent garbage interface to keep it inline with the rest of their administrative service.