Infrastructure status, live.
Real-time uptime, ISP reputation trends, regional node capacity, and full incident history with post-mortems. Most offshore providers do not publish a status page; we do, because operators deserve to see what they are paying for.
System Components
Each component is independently monitored. The 90-day uptime bar shows daily status; hover any day for details.
ISP Delivery Performance
Inbox placement, spam rate, time-to-inbox, and deferral rate measured across all client sending pools. Updated daily via seed network and postmaster integrations.
| ISP / Provider | Inbox Placement | Spam Rate | Time to Inbox | Avg Deferral | Status |
|---|
Placement measured via seed network across client-representative content. Spam rate reflects Google Postmaster Tools domain reputation averaged across managed domains in Good standing. Individual results vary by list hygiene and content.
Sender Reputation Health · 12 months
Domain reputation score across the four major ISPs, averaged across managed domains in Good standing. We publish the trend, not just today's snapshot, because reputation lives in the trajectory — not in any single day.
Score derived from Google Postmaster Tools (Gmail), Microsoft SNDS (Outlook), Yahoo Sender Hub (Yahoo) and Apple's iCloud sender feedback. Higher is better. A score below 90 typically corresponds to placement degradation on the corresponding ISP.
Detection & Resolution Times — annual evolution since 2024
Mean Time to Detect (MTTD) and Mean Time to Resolve (MTTR) per year. The trend is the point: we get faster every year because we learn from every incident. SaaS providers rarely publish this data — we do, because the slope of these two lines is the truth about whether an operator is actually improving.
MTTD = time from incident occurrence to first internal alert. MTTR = time from first alert to full resolution. Calculated annually across all incidents on record. Chart shows completed years; the current year is added to this chart at year end.
Where Incidents Originate
—
Categorisation based on root-cause analysis of every incident on record. "Our infrastructure" includes all incidents where the failure originated in code, configuration or operational decisions on our side. "Third-party services" includes upstream registries, certificate authorities, payment processors and external API providers.
Sending Volume Distribution by Node
Live distribution across the four jurisdiction-aware nodes. Volume splits dynamically based on client location, jurisdiction preference and ISP routing.
Capacity Headroom by Node
—
Capacity utilisation = current monthly throughput as a percentage of the engineered ceiling for each node. Headroom is what protects you when something fails elsewhere; we keep every node well below 80% so cross-region failover does not throttle on arrival.
Regional Node Status
All four nodes operate independently with automatic cross-region failover. Volume shown for the current calendar month.
Volume vs. Incidents — annual record since 2024
Two metrics, one chart, one story. Bars show our average monthly sending volume in billions of emails for each completed year. The line shows how many incidents we recorded that year. Volume has grown year after year; incident count has stayed flat. Scaling without breaking is the engineering work most providers do not show.
Volume growth modelled at 18% YoY from a 2.1B emails/month baseline. Incident counts include both degraded and outage classes. Only completed years and the current year appear on this chart; future years are added as they happen.
90-Day Availability Record — Primary SMTP Relay
Each bar represents one day. Hover for details.
Incident History
Public post-mortems for every incident on record. We disclose root cause, impact and resolution because operators learn from real failures, not from marketing copy.
Why we publish a status page
Most offshore and DMCA-tolerant providers do not publish a status page. The reasoning is straightforward: a status page is a public record of every time something went wrong. It is also a public commitment to transparency. Many operators in this space prefer to handle incidents quietly because the customer base does not always demand visibility — and visibility is uncomfortable.
We publish ours because the alternative is asking customers to trust us on faith. Faith does not scale. A status page does. When something goes wrong, you should not have to email support to find out; you should be able to read what happened, what we did, and what we are changing so it does not happen again. Every incident on this page has a written post-mortem with the same level of detail.
The dataset behind this page covers ten years of operations and is updated continuously. The infrastructure has grown from a few hundred IPs in 2015 to more than 80,000 IPs across four jurisdictions in 2026. The numbers above are not aspirational — they are what we measure today, every day, on production traffic.
If something looks wrong here that matters to your operation, our status page comments are not the place to raise it. Email support or open a ticket through your dashboard and we will engage immediately.