System status.
Live — serving production traffic
Monitored from four regions, with 90 days of history at status.mails.ai.
Current status by service
- Operational
API (api.mails.ai)
100% uptime - Operational
Dashboard (app.mails.ai)
100% uptime - Operational
Website (mails.ai)
99.885% uptime
Read from status.mails.ai at 03:11 UTC on Oct 12, 2026.
SLA commitments and incident response
What we monitor
The API, dashboard, and website are monitored today and reported live at status.mails.ai. Here’s the full surface list and what our SLA commitments are.
Five surfaces. Three are monitored today from four regions (US, EU, Asia, Australia); the remaining two come under monitoring as they ship. Latency percentiles per surface follow as the remaining surfaces come under monitoring.
API (api.mails.ai)
Send + receive + reply events
Live — monitored
Dashboard (app.mails.ai)
Auth, agents, usage, settings
Live — monitored
MCP server (@mailsai/mcp-server)
npm-distributed, runs client-side
Phase 1
Marketing site (mails.ai)
Public site, blog, comparisons, glossary
Live — monitored
Webhooks (customer endpoints)
Delivery confirmation, retry queue health
Phase 1
SLA commitments
Per-tier uptime targets and miss-credit policy. Documented at signup, enforced by the billing system.
| Tier | Uptime target | On miss |
|---|---|---|
| Phase 1 (Q3 2026) | 99.9% | Pro-rated billing credit on miss |
| Phase 2 (Q4 2026, Scale+ — roadmap) | 99.95% | Pro-rated credit + waived next-month overage |
| Phase 3 (Q1 2027, high-volume) | 99.99% | Custom SLA addendum on request |
Incident response
Phase 1 launch target
The cadence below is what we build to — it requires the uptime monitor + on-call rotation that ship with Phase 1. Today we respond best-effort during business hours (UTC+8 primary) and within 24h off-hours.
Detect — uptime monitor probes each surface on a fixed cadence (target: every 30–60 seconds). Alert fires on two consecutive failures.
Acknowledge — named on-call rotation acknowledges severity-1 within minutes, severity-2 within 15 minutes, severity-3 within an hour. (Today: best-effort, no named rotation yet — if you need a hard ack SLA, email support@mails.ai before relying on us for a launch.)
Update — status page updates at least every 15 minutes during active incidents until resolved.
Resolve — recovery confirmed via 5 consecutive successful probes across all affected surfaces.
Postmortem — severity-1 incidents get a public postmortem within 1 week, archived at /incidents.