Status
Service status.
Checked every 10 minutes from outside the service, by a monitor on a different provider. What it is seeing now, and what it saw over the last 90 days.
- Checked Every 10 minutes
- From Outside the service
- History 90 days
Live
Right now
-
https://mcp.mailbox-mcp.com/healthzok -
https://mcp.mailbox-mcp.com/db/healthzok
Checked every 10 minutes from outside the service, by a monitor on a different provider. If the service were down and this website were not, this line would say so; if this website were down too, the monitor's own page would still be up, because it shares a provider with neither.
History
The last 90 days
One cell per day, oldest first and today last. Degraded: the service answered but reported a stale self-check, such as last night's backup marker; we are alerted, nothing customer-facing is off. Down: the monitor could not get a healthy answer. A day takes the worst thing that happened in it: red for any failed check, amber for degraded checks and no failures, green for neither.
- No failures
- Degraded
- Down
- No data yet
2 of 90 days recorded: 2 with no failures, 0 degraded, 0 down.
Incidents
No incidents in the last 90 days.
Method
What the monitor checks
Every 10 minutes a small program on Cloudflare, chosen because it is
neither the provider that runs the service nor the one that serves this
website, requests the service's 2 public health endpoints,
mcp.mailbox-mcp.com/healthz and
mcp.mailbox-mcp.com/db/healthz: one for each of the 2
servers customers can reach, the second being the one every customer
connection runs through and the one that also checks its database.
Each answers in
status words and nothing else, with no filenames, counts or mailbox
addresses: whether the database answered, whether the nightly backup ran
and verified, whether its off-site copy landed, whether the job that
deletes rows on schedule ran, and whether the running code is a clean
checkout. Both endpoints are public, carry no customer data, and are the
same addresses anybody can request.
Down means the monitor could not get a healthy answer: an endpoint did not answer, or answered with an error. Degraded means the service answered but reported a stale self-check, such as last night's backup marker being older than it should be, or the off-site copy not landing; we are alerted, and nothing customer-facing is off. The monitor alerts on both, by design, and records them apart: a degraded check is the service telling on itself rather than the monitor guessing, a customer's mail keeps working through it, and it is on this page because a backup that quietly stopped is exactly the kind of thing a status page is for. The headline chip carries the same 2 words for right now, and says since when if the service is degraded at the moment you read it.
The monitor keeps 90 days of checks and the incidents derived from them, and this page is drawn from that record with a 60-second cache in front of it. When the monitor cannot be reached, the page says so rather than showing the last thing it saw as though it were current. The monitor's own page shows the same history and is the fallback if this website is the thing that is down.
There is no service level agreement and the terms say so plainly. What there is instead is this page, an alert to the person who runs the service when the monitor sees consecutive failures, and a page for IT and security teams that says where the service runs, what is backed up and how an incident is notified.