Time in transit.
How quickly mail sent through Postboi reaches the receiving server, per inbox provider, and how much of the time our API and database were answering. Every figure on this page is read from our own sends and our own heartbeats, and none of it is typed in by hand.
The last 30 days
How fast it arrives
Of 2 deliveries in the last 30 days, 100% reached the receiving server within five seconds of Postboi handing them to Amazon SES.
| Inbox provider | Delivered | Within 1 second | Within 5 seconds | Within 30 seconds | Within 1 minute | Within 5 minutes |
|---|---|---|---|---|---|---|
| All mail | 2 | 0% | 100% | 100% | 100% | 100% |
A provider gets its own row once it has taken 50 deliveries in the window. "All mail" counts every delivery, including companies on Google Workspace or Microsoft 365, which are filed under their own domains rather than as Gmail or Outlook.
The last 90 days
Uptime
Heartbeats
- Uptime
- 100%
- Minutes on record
- 192 since 2026-09-25 17:35 UTC
- Minutes missed
- 0
- 25 Sept: 100%
One mark per UTC day, oldest first. A red mark is a day with at least one minute missed.
Nothing asserted
How it's measured
- Delivery time is Amazon SES's own figure from its delivery event: the time from SES accepting the message to the receiving mail server accepting it. What happens inside the recipient's mailbox after that, such as spam filtering, is the provider's and isn't in the figure.
- Which provider is read from the recipient's domain when the event arrives. Only the provider is kept, never the address.
- Uptime is the share of minutes with a heartbeat. Once a minute a scheduled job runs the Worker that serves Postboi's API, which writes a row to the database. A minute with a row is a minute both answered. The job runs inside Cloudflare rather than calling in over the internet, so it measures the Worker and the database, not the network in front of them. A minute without one counts as down, even when the cause was the scheduler rather than us.
- Only mail sent through Postboi's own sending counts. Mail relayed through a customer's own provider, and sandboxed sends that never leave, are left out.
- The page recalculates every few minutes. Last measured 2026-09-25 20:47 UTC. The live check of each part of the service is on the status page.
Under the hood
What delivers it
Postboi's mail is delivered by Amazon SES in the EU (Stockholm, eu-north-1). Each team sends
as its own SES tenant, so when a team's bounces or complaints run high, SES pauses that team
and nobody else. Your own domain is signed with DKIM and gets its own return path, bounce. on your domain, so SPF and DMARC line up with the address you send from.
What we do to keep that reputation clean, from warm-up limits to nightly blocklist checks, is in the deliverability docs.
ALSO The rest of the small print
- PB-01 What we keep, and what we don't. What we collect, who touches it, and how to get it back. Privacy policy
- PB-02 Conditions of carriage. The rules of sending through Postboi, and what happens when they're broken. Terms of service
- PB-03 Chain of custody. Where your data lives, how it's sealed, and the whole subprocessor list. Security & data
- PB-04 Every lane is open. Live checks against the real dependencies, every time the page loads. Service status
- PB-05 Rates of postage. Every plan and what a month costs at your volume, in plain figures. Pricing
- PB-06 Postboi or Resend? Setup, price at every volume, and what comes in the box, side by side. Comparison