Postmark: Sending Delays
Timeline of updates
- resolved
[UPDATE] On April 2nd starting at ~07:00pm UTC, Postmark experienced an incident that resulted in delayed message delivery and webhook notifications for some customers. The issue was caused by an infrastructure configuration change that disrupted internal mail routing. While messages were safely queued in a "Processing" state, they were not delivered until the routing configuration was restored.
Service was restored on April 3rd at ~4:20am UTC and the backlog of queued messages began sending immediately. No data was lost during this event.
We have since implemented additional monitoring on our internal routing and surrounding sending services to ensure our teams are alerted to processing bottlenecks immediately. We sincerely apologize for the delay and will continue to improve.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
5dcfa7e4fa34f39b…
Impact, status and times are the vendor’s own, as last archived. View on status.postmarkapp.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Postmark, started 2026-04-02 19:00 UTC, resolved after 10 h, 1 update(s).
- Title
- Sending Delays
- Vendor
- Postmark
- Date
- URL
- https://rewindex.com/company/postmark/incidents/491225
Postmark profileRecent Postmark incidentsAll outages on April 2, 2026Postmark in April 2026MarkdownJSON