Service Status
The API and email pipeline are monitored from inside the production Worker. A synthetic message exercises storage, parsing, OTP extraction, and read-back every five minutes.
Email ingestion is degraded
| Component | Status | Evidence |
|---|---|---|
| Website and API | Operational | This page was rendered by the production Worker. |
| Inbound email pipeline | Degraded | Last probe: ; path: inline; 104 ms. |
| OTP extraction | Degraded | The ingestion probe must parse and read back a known OTP before it passes. |
What this proves
Status pages are most useful when they explain the evidence behind the green light. TempMailGrab checks the website/API render path, inbound message processing, storage, OTP extraction, and read-back. That makes the status page a real product-health signal rather than a decorative uptime badge.
For the full trust picture, pair this page with privacy explained, security, and the compatibility dataset.
Monitoring scope
The probe covers message staging, MIME parsing, database storage, OTP extraction, and API read-back. It cannot originate a public SMTP message, so Cloudflare Email Routing itself is monitored separately from this synthetic check.
Machine-readable status is available at /health. Security issues should be reported through security.txt; service questions belong on the contact page.