KapoMail Status

Overall status

Components

• Sending API ●Operational
• SMTP submission ●Operational
• Dashboard ●Operational
• Webhook delivery ●Operational

We seed real Gmail, Outlook and Yahoo mailboxes and check where each message actually lands — inbox, promotions or spam — separately from whether the receiving server accepted it. A message can get a 250 OK at the SMTP layer and still be silently filed into spam; the components above would show green while your customers still never see the email. This is the check that catches that.

• Gmail ●Operational
• Outlook / Hotmail ●Operational
• Yahoo ●Operational

90-day uptime

Each bar is one day. Hover or focus a bar for its date and status; the pattern, not just the colour, tells you which is which.

Past incidents

We publish a write-up like the one above after every incident, including the ones that make us look less than perfect. An unblemished status page nobody can verify is worth nothing; a specific, checkable account of what broke and what we changed is worth quite a lot.

Get notified

Subscriber emails are sent by an independent third-party provider, not by KapoMail's own Sending API or SMTP submission — deliberately, so a KapoMail outage cannot also silence the notification that tells you about it.

Why this page isn't on our own infrastructure

If this status page shared a server, a database or a DNS zone with KapoMail itself, it would go down at exactly the moment it is needed most — during a KapoMail incident — and silence at that moment generates more support tickets than the incident itself. So this page is static, hosted on a separate provider, and reachable through a DNS record that deliberately points away from our platform. Full reasoning and hosting comparison: operations documentation.