Q: Can I just host my status page on my own server to save money?
A: Please don't, and here's why it backfires. The whole point of a status page is to communicate during an outage. If it lives on the same infrastructure as the thing that's down, it goes down with it, exactly when users need it most.
The popular shortcut, a /status route inside your main app, fails the one scenario it exists for. Your database dies, the app 500s, and now your status page 500s too.
Recommendation: host the status page on completely separate infrastructure, a managed status provider, a static page on a different CDN, anything outside your blast radius.
Follow-up: also put it on a different DNS provider, so a DNS outage doesn't take both down.
Got a question? Drop it in the comments.
Pingback Clinic
@PingbackClinic
Q: Can I just host my status page on my own server to save money?
Этот пост опубликован в Telegram-канале Pingback Clinic. Подписаться можно по ссылке: @PingbackClinic.