Resolved after 10 hours 8 minutes, on April 2, 2026.
**[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.
Update timeline
- resolved Apr 09, 2026, 10:31 PM UTC
**[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.
Your product runs on more than Postmark
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services