No incidents to report.
Pre-launch — no production services to monitor yet. Real status.mails.ai ships at Phase 1 launch with live uptime, latency, and incident history.
No production services to monitor yet. Once Phase 1 ships, this card becomes a real pinger updated every 30 seconds with current uptime, p50/p99 latency, and any active incidents per surface.
What we will monitor
Five surfaces. Each gets uptime + p50/p99 latency + error-rate per region.
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, outbound pool + 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 before public signup opens — it requires the uptime monitor + on-call rotation that ship with Phase 1. During closed beta 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. (Closed beta: 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 at every volume.
Public API opens Q3 2026. Drop ~6 lines into your agent and ship.
$ npm install @mailsai/sdk