Status

System status

A scripted client connects to the public MCP endpoint every five minutes, lists the tools, lists an inbox and reads a message. Everything below is counted from what those checks recorded.

All systems operational

The most recent check passed.

Last check Oct 13, 2026, 06:40 UTC

Uptime, last 30 days

99.83%

8,431 checks, one every 5 minutes. 14 of them failed.

Continuous monitoring started Aug 3, 2026.

Last 30 days

  • Sep 14, 2026: 288 checks, all passed
  • Sep 15, 2026: 288 checks, all passed
  • Sep 16, 2026: 288 checks, all passed
  • Sep 17, 2026: 288 checks, all passed
  • Sep 18, 2026: 287 checks, all passed
  • Sep 19, 2026: 288 checks, 1 failed
  • Sep 20, 2026: 288 checks, all passed
  • Sep 21, 2026: 288 checks, all passed
  • Sep 22, 2026: 288 checks, all passed
  • Sep 23, 2026: 288 checks, all passed
  • Sep 24, 2026: 288 checks, 1 failed
  • Sep 25, 2026: 288 checks, 2 failed
  • Sep 26, 2026: 288 checks, all passed
  • Sep 27, 2026: 288 checks, 1 failed
  • Sep 28, 2026: 288 checks, all passed
  • Sep 29, 2026: 287 checks, 1 failed
  • Sep 30, 2026: 288 checks, all passed
  • Oct 1, 2026: 288 checks, all passed
  • Oct 2, 2026: 288 checks, all passed
  • Oct 3, 2026: 288 checks, 2 failed
  • Oct 4, 2026: 288 checks, 1 failed
  • Oct 5, 2026: 288 checks, 1 failed
  • Oct 6, 2026: 288 checks, all passed
  • Oct 7, 2026: 288 checks, 1 failed
  • Oct 8, 2026: 288 checks, all passed
  • Oct 9, 2026: 288 checks, 1 failed
  • Oct 10, 2026: 288 checks, all passed
  • Oct 11, 2026: 288 checks, 2 failed
  • Oct 12, 2026: 288 checks, all passed
  • Oct 13, 2026: 81 checks, all passed
30 days agoToday
All checks passedOne check recoveredSome checks failedNo data

What is checked

One pass through the four steps, in this order. A run stops at its first failure, so each step is scored only against the checks that reached it.

Incidents

A single failed check that passes again five minutes later is counted against uptime above but is not listed here as an incident. That is the same line the pager draws: two consecutive failures, or one failure of a kind that cannot be somebody else's network.

No incident in the last 30 days.

14 single failed checks in this window, each of which passed again on the next run.

What this page does and does not tell you

  • The check runs from one place on a five minute cron, so an outage shorter than five minutes can pass unrecorded, and the timestamps here are accurate to the check that caught it rather than to the second.
  • It exercises four code paths. Sending, scheduling, drafts and folder operations are not on this page because nothing measures them on a schedule, and a figure covering them would be a guess.
  • It reads one real mailbox at one provider. A failure attributed to the mail provider is that provider having a bad minute, not necessarily anything you would have noticed on yours.
  • Nothing here is derived from customer traffic. No account, workspace or message is counted, sampled or shown.

Every number on this page is counted from the monitor's own recorded runs at read time. Nothing is entered by hand.

How we handle your mail and credentials

Something wrong that this page says is fine? Write to hello@mcpemails.com.