Skip to content

Outage tracker / Postmark

Is Postmark down?

Short linkrlup.io/down/postmark

I'm having a problem

Operationalchecked 20 minutes ago

We reached Postmark from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 10 days we have measured Postmark (since Aug 22, 2026).

our independent probeslive · checked Sep 1, 2026, 3:45 AM UTC
US-East358 msOperational
US-West219 msOperational
Europe501 msOperational
Asia-Pacific990 msOperational
their status pagetheir claim, not our reading

Postmark publishes no status feed we can read, so the only independent reading here is ours on the left.

Postmark response time, by region

US-East
414msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 540ms2026-08-23 UTC: p95 183ms2026-08-24 UTC: p95 663ms2026-08-25 UTC: p95 448ms2026-08-26 UTC: p95 445ms2026-08-27 UTC: p95 423ms2026-08-28 UTC: p95 354ms2026-08-29 UTC: p95 416ms2026-08-30 UTC: p95 459ms2026-08-31 UTC: p95 423ms2026-09-01 UTC: p95 414ms
Aug 3Aug 17Sep 1
US-West
542msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 773ms2026-08-23 UTC: p95 608ms2026-08-24 UTC: p95 341ms2026-08-25 UTC: p95 552ms2026-08-26 UTC: p95 570ms2026-08-27 UTC: p95 903ms2026-08-28 UTC: p95 560ms2026-08-29 UTC: p95 544ms2026-08-30 UTC: p95 557ms2026-08-31 UTC: p95 468ms2026-09-01 UTC: p95 542ms
Aug 3Aug 17Sep 1
Europe
588msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 543ms2026-08-23 UTC: p95 542ms2026-08-24 UTC: p95 713ms2026-08-25 UTC: p95 647ms2026-08-26 UTC: p95 575ms2026-08-27 UTC: p95 735ms2026-08-28 UTC: p95 534ms2026-08-29 UTC: p95 625ms2026-08-30 UTC: p95 503ms2026-08-31 UTC: p95 625ms2026-09-01 UTC: p95 588ms
Aug 3Aug 17Sep 1
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 890ms2026-08-23 UTC: p95 913ms2026-08-24 UTC: p95 914ms2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.0s2026-08-29 UTC: p95 1.2s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.2s2026-09-01 UTC: p95 1.1s
Aug 3Aug 17Sep 1

Is it Postmark, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Postmark -- it cannot diagnose Postmark's own systems.

What we measured, function by function

Postmark answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 358msstatus code: 401checked: Sep 1, 2026, 3:36 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Postmark normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 219msstatus code: 401checked: Sep 1, 2026, 3:44 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Postmark normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 501msstatus code: 401checked: Sep 1, 2026, 3:37 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Postmark normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 990msstatus code: 401checked: Sep 1, 2026, 3:45 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Postmark normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionPostmark is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionPostmark is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionPostmark is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionPostmark is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionPostmark is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionPostmark is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Postmark, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Postmark yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Postmark.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Postmark since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Postmark covering any window you pick, with our measurements and Postmark's own claim at the time, side by side.

Full availability history for Postmark: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Postmark, and again when they can reach it again. That is our own measurement from ten regions, not Postmark's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Postmark uptime measured by RealUptimeLive, from this page's own readings.
[![Postmark uptime measured by RealUptime](https://realuptime.io/outages/postmark/badge.svg?days=30)](https://realuptime.io/outages/postmark)
<a href="https://realuptime.io/outages/postmark"><img src="https://realuptime.io/outages/postmark/badge.svg?days=30" alt="Postmark uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Postmark's SLA implies, from our measurement

At or above your target

We measured none of downtime for Postmark over the 244h 5m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 14 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Postmark's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.postmarkapp.com/server
secondary
https://postmarkapp.com/
RealUptime is not affiliated with Postmark; the name identifies what we measured, and nothing here speaks for Postmark's own team. We send a single web request to Postmark from 4 regions on our own schedule and time the response. We do not see inside Postmark's systems, do not use an account or real transaction, and are not the same signal Postmark's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Postmark is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Postmark operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 22, 2026 (10 of 14 days so far, 3364 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

AkamaiAmplitudeAnthropicAuth0AWS (Amazon Web Services)