Jul 31, 8:18 PM IST — investigating: Automated detection: this service is not responding. Status updates will appear here as they are known.

Jul 31, 8:19 PM IST — investigating:

Jul 31, 8:20 PM IST — investigating: NOT AN OUTAGE — our monitoring probe is at fault; beta is serving normally. Verified from external networks: 40 consecutive HTTP 200 responses (max 781ms), cache-busted cold renders 0.45-0.48s, x-nextjs-cache HIT, and 200 for every client type tested. The beta-web check has failed 50+ CONSECUTIVE cycles at exactly 8001ms with code 0 since ~13:51Z, while the beta-api check on the same host holds an unbroken healthy streak above 10,000 — so the network path is fine and only this one check hangs. This incident is being left open rather than repeatedly closed, because the probe itself needs fixing and beta UI has no trustworthy external monitoring until it is. Beta is NOT down.

Jul 31, 9:47 PM IST — resolved: Resolved — the beta-web check has recovered on its own (probe now 1717ms / HTTP 200, previously failing at exactly 8001ms). External verification agrees: 5/5 probes HTTP 200. CORRECTION to the earlier update on this incident: I characterised the probe as broken and needing a fix. It recovered without intervention after ~50 consecutive failed cycles, so the more likely explanation is a transient path-specific slowness between the probe vantage point and beta (the probe saw >8s while external clients consistently saw ~0.45s), not a permanently broken check. beta-api on the same host was never affected (unbroken ok streak, now 10,144). Worth noting for next time: a ~2 hour window where beta UI appeared down to monitoring and fine to users is itself a signal about the probe path, and is the reason this incident stayed open rather than being repeatedly closed.

Jul 31, 8:13 PM IST — investigating: Automated detection: this service is not responding. Status updates will appear here as they are known.

Jul 31, 8:16 PM IST — resolved:

Jul 31, 7:22 PM IST — investigating: Automated detection: this service is not responding. Status updates will appear here as they are known.

Jul 31, 8:13 PM IST — resolved:

Jul 21, 5:19 AM IST — investigating: Automated detection: this service is not responding. Status updates will appear here as they are known.

Jul 21, 5:55 AM IST — resolved: Automated recovery confirmed: the service has been healthy for several consecutive checks.

Jul 20, 5:13 PM IST — investigating: Automated detection: this service is not responding. Status updates will appear here as they are known.

Jul 20, 5:20 PM IST — resolved: Automated recovery confirmed: the service has been healthy for several consecutive checks.