Delays in activity data
Postmark reports slow load times in the Postmark UI and delays in activity data in the UI and API. Some messages stay in "Processed" longer than expected. Requests to the Messages API return errors or briefly fail to connect. Postmark is investigating. Sending is not affected.
State
Investigating
Started
Ongoing for
28 min
Worst impact
Degraded
Timeline
1 updateInvestigating
28 min 100%
Updates
Times in UTCAs posted by Postmark
You may see slower load times in the Postmark UI, and some activity data in the UI and API may be delayed. We’re investigating. Here’s what you might notice: - Recent activity (deliveries, bounces, opens, and clicks) takes longer to appear - Some messages stay in “Processed” longer than expected - Requests to the Messages API return errors, or briefly fail to connect **Sending isn’t affected. Your emails are still going out, and no activity data is lost.** We’ll update this page as soon as we know more.
Postmark in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
11
Median duration
2 h 6 min
This incident
78% shorter than the median
Other Postmark incidents
All incidents
Postmark·Delays processing Inbound messages
Postmark Inbound messages were delayed before they reached webhooks. Sending was not affected. Postmark reports that the incident is resolved. It lasted about 66 minutes.
Postmark·SMS codes for two-factor authentication may not arrive
Resolved We've identified and resolved the issue affecting SMS two-factor authentication codes. Codes should now arrive as expected when you log in to your Postmark account. Sending email through Postmark wasn't affected. If you still don't receive a code, please contact support: https://postmarkapp.com/support Resolved at 14:50 EDT (18:50 UTC) - 27 October 2026.
Postmark·Delayed Inbound Message Processing
This has been resolved. All inbound webhooks processing have been caught up. No messages have been lost.
Postmark·Delayed Message Delivery
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 support@postmarkapp.com.
Postmark·Delayed Message Delivery
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 support@postmarkapp.com.
Follow Postmark
Your coding agent knows when Postmark is down, and tells you when a failure is theirs, not yours. You can also get Postmark incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "postmark" and tell me if Postmark has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=postmark/feed subscribe https://outages.live/feed.xml?providers=postmarkFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane