outages.live
Live
P

Postmark

Postmark is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

8

Days with an incident

9

Median duration

2 h 43 min

Longest incident

31 h 39 min

Components

15

API

General Operational
90 days agoNo incidentsToday
Sending Operational
90 days agoNo incidentsToday
Receiving Operational
90 days agoNo incidentsToday
Sandbox Operational
90 days agoNo incidentsToday

SMTP

General Operational
90 days agoNo incidentsToday
Sending Operational
90 days agoNo incidentsToday
Receiving Operational
90 days agoNo incidentsToday
Inbound Operational
90 days agoNo incidentsToday
Webhooks Operational
90 days agoNo incidentsToday

Web App

General Operational
90 days agoNo incidentsToday
Login Operational
90 days agoNo incidentsToday
Billing & Subscriptions Operational
90 days agoNo incidentsToday

Analytics

General Operational
90 days agoNo incidentsToday
Statistics Operational
90 days agoNo incidentsToday
Link Tracking Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 27, 2026

Duration1 h 43 min17:19 to 19:02SMS codes for two-factor authentication may not arriveDegraded

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.

Sep 28, 2026

Duration2 h 6 min15:55 to 18:00Delayed Inbound Message ProcessingDegraded

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

Duration3 h 59 min13:49 to 17:47Delayed Message DeliveryDegraded

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.

Sep 22, 2026

Duration20 min18:15 to 18:35Delayed Message DeliveryDegraded

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.

Sep 17, 2026

Duration1 h 33 min20:12 to 21:45Web-App Page Loading IssuesDegraded

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 support@postmarkapp.com.

Aug 24, 2026

Duration3 h 21 min17:44 to 21:05Delays in Stats DataDegraded

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.

Aug 18, 2026

Duration31 h 39 min14:34 to 22:12Open Webhook DelaysDegraded

The issue is now fully resolved. We are continuing to improve our systems, observability, and monitoring to prevent future occurrences. Thank you for your patience. Starting August 18th at ~9:34am CT (~14:34 UTC), Postmark experienced delays in delivering open webhook events. New open events resumed delivery on August 19th at ~8:47am CT (~13:47 UTC), and all backlogged events completed re-delivery at ~4:52pm CT (~21:52 UTC).

Aug 14, 2026

Duration16 h 51 min20:34 to 13:25Sending DelaysDegraded

The issue has been resolved after additional monitoring into the early morning. Thank you for your patience.

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.

Prompt
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.cc/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.

RSS
https://outages.cc/feed.xml?providers=postmark
Slack
/feed subscribe https://outages.cc/feed.xml?providers=postmark

Go from tracking outages to fixing production issues with Polylane.

Try Polylane