System status.
The API and dashboard are serving production traffic. Live per-service uptime and incident history are published at status.mails.ai.
The API, dashboard, and website are checked continuously from four regions, with live per-service uptime and 90-day incident history published at status.mails.ai. Latency percentiles per surface follow as the remaining surfaces come under monitoring.
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.
Send + receive + reply events
Auth, agents, usage, settings
npm-distributed, runs client-side
Public site, blog, comparisons, glossary
Delivery confirmation, retry queue health
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
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.
Subscribe to /changelog for status-page launch notification at Phase 1.
Built for agents.
Self-serve in minutes.
The API is live and self-serve. Drop ~6 lines into your agent and ship.
$ npm install @mailsai/sdk