Domain Uptime Monitor

The failure this exists for

HTTP 200 is not proof a site is working:

• A suspended or payment-disabled deployment serves a billing page with 200.
• A broken build serves an empty shell with 200.
• A partial deploy serves the old page while the API behind it is gone.
• A misconfigured origin leaves the marketing page at 200 while every signed-in action fails.

A monitor that checks the status code reports all four as healthy. Every domain here declares what a working response actually contains.

Prerequisites