Is Postmark down?

We are currently investigating reports of delayed inbound message delays as of 10:25 CDT. Messages are being queued and will be processed once the issue is resolved. No messages have been lost. We will provide an update as soon as we have more information.

We've applied a fix and inbound message processing is now recovering. Delayed messages are being worked through, and processing times are returning to normal. No messages have been lost. We're continuing to monitor to confirm full recovery.

This has been resolved. All inbound webhooks processing have been caught up. No messages have been lost.

We identified an issue that caused delays in outbound message sending between 9:49 AM and 10:07 AM CT. Messages were queued and are not lost. We are actively working on a mitigation and will provide an update as soon as we have more information.

We've identified and resolved the underlying issue that caused the delay in outbound message sending between 9:49 AM and 10:07 AM CT. New messages since 10:07 AM CT are processing normally. We are now working through the backlog of messages queued during that window and will post a final update once all queued messages have been delivered. No messages were lost.

This incident has been resolved. The backlog of messages queued during the delay between 9:49 AM and 10:07 AM CT (10:49–11:07 AM ET) has been fully processed and delivered. New messages continue to be accepted and delivered normally. No messages were lost. If you have questions about a specific message, please reach out to us at [email protected].

A subset of messages accepted between 2:15 pm and 2:35 pm EDT on September 22 (18:15 – 18:35 UTC) were held in queue due to a processing issue instead of being delivered immediately. Those messages were fully processed and delivered at 3:38 pm EDT on September 24 (19:38 UTC). No messages were lost. Messages accepted outside of this 20-minute window were not affected and were delivered normally. If you have questions about a specific message, please reach out to us at [email protected].

Some users were experiencing problems with our service from 4:15 pm to 5:25 pm EDT, resulting in a page titled "Something went wrong". We have identified the root of the issue and have applied a remediating solution. If you are still encountering this page after clearing your site data, cache & cookies, please reach out to us at [email protected].

We're seeing delays of approximately 30 minutes in the data underlying the Stats API. This does not affect the Stats API endpoint itself, which is fully operational. Stats data is currently catching up and no data is being lost. We're monitoring closely and will update here as it resolves.

We've now resolved the incident. Stats data has caught up and is now displaying in real time. This issue occurred from approximately 13:45 EDT to 16:25 EDT on August 24, 2026. Thank you for your patience.