Every check is passing
Five checks, run from the deployment itself against its own web app, API, MCP server, database, pipeline queue. Each one is a real request, timed.
Checked within the last minute. This page refreshes itself every 60 seconds while it is open.
The five checks
Green means the request came back the way it should. The time is how long it took from inside the deployment.
Checks
- Web apppassing
robots.txt answered 200
426 ms
- APIpassing
/v1 lists 11 endpoints
1298 ms
- MCP serverpassing
refuses GET with 405 and speaks 2025-06-18
1392 ms
- Databasepassing
select 1 answered
338 ms
- Pipeline workerspassing
no run has waited longer than 5 minutes
322 ms
Last run 2026-11-05 18:26:59 UTC. The same report is at /status.json, which answers 200 while every check passes and 503 when one does not, so a monitor can watch it.
What each check does
No third party pings from the outside. The deployment asks itself the questions a customer's script would ask, and reports the answers without editing.
Method
- Web app
- Fetches robots.txt from the site's own origin and expects a 200.
- API
- Fetches the discovery document at /v1 and expects the endpoint list.
- MCP server
- Sends a GET to /api/mcp and expects the 405 a stateless server returns, with the protocol version header.
- Database
- Runs select 1 on the primary database.
- Pipeline workers
- Counts runs that have sat in the queue for more than 5 minutes and expects none.
- The cache
- The report is kept for 60 seconds, so a busy status page never becomes load on the systems it watches. Add ?fresh=1 to the JSON address to force a new run.
No incidents recorded yet
This page started on Sep 25, 2026 and keeps no stored history. When something breaks, the entry goes here: what happened and for how long, and what changed so it does not happen again.