Skip to content

Outage tracker / Postmark

Is Postmark down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of Postmark pass from all 10 regions we check.

As of Oct 22, 2026, 11:37 PM UTC, RealUptime's checks of Postmark passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Postmark did not fail from two or more distant regions in the 61 days we have checked it (since Aug 22, 2026). This does not show Postmark works for users.

our check readinglive · checked Oct 22, 2026, 11:37 PM UTC
US-East899 msChecks passing
US-West1611 msChecks passing
Europe1050 msChecks passing
Asia-Pacific2328 msChecks passing
US-Central753 msChecks passing
Canada636 msChecks passing
UK594 msChecks passing
Southeast Asia1408 msChecks passing
Australia2473 msChecks passing
South America1700 msChecks passing
their status pagetheir claim, not our reading

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

Postmark response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 432ms2026-09-24 UTC: p95 439ms2026-09-25 UTC: p95 346ms2026-09-26 UTC: p95 370ms2026-09-27 UTC: p95 360ms2026-09-28 UTC: p95 498ms2026-09-29 UTC: p95 383ms2026-09-30 UTC: p95 397ms2026-10-01 UTC: p95 562ms2026-10-02 UTC: p95 488ms2026-10-03 UTC: p95 491ms2026-10-04 UTC: p95 483ms2026-10-05 UTC: p95 506ms2026-10-06 UTC: p95 431ms2026-10-07 UTC: p95 491ms2026-10-08 UTC: p95 484ms2026-10-09 UTC: p95 490ms2026-10-10 UTC: p95 560ms2026-10-11 UTC: p95 608ms2026-10-12 UTC: p95 588ms2026-10-13 UTC: p95 583ms2026-10-14 UTC: p95 970ms2026-10-15 UTC: p95 723ms2026-10-16 UTC: p95 521ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
US-West
1.5sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 462ms2026-09-24 UTC: p95 516ms2026-09-25 UTC: p95 501ms2026-09-26 UTC: p95 475ms2026-09-27 UTC: p95 420ms2026-09-28 UTC: p95 439ms2026-09-29 UTC: p95 467ms2026-09-30 UTC: p95 393ms2026-10-01 UTC: p95 611ms2026-10-02 UTC: p95 403ms2026-10-03 UTC: p95 634ms2026-10-04 UTC: p95 651ms2026-10-05 UTC: p95 619ms2026-10-06 UTC: p95 675ms2026-10-07 UTC: p95 658ms2026-10-08 UTC: p95 670ms2026-10-09 UTC: p95 618ms2026-10-10 UTC: p95 673ms2026-10-11 UTC: p95 585ms2026-10-12 UTC: p95 591ms2026-10-13 UTC: p95 629ms2026-10-14 UTC: p95 638ms2026-10-15 UTC: p95 611ms2026-10-16 UTC: p95 631ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s
Sep 23Oct 7Oct 22
Europe
1.0sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 705ms2026-09-24 UTC: p95 803ms2026-09-25 UTC: p95 994ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 911ms2026-09-28 UTC: p95 968ms2026-09-29 UTC: p95 776ms2026-09-30 UTC: p95 768ms2026-10-01 UTC: p95 808ms2026-10-02 UTC: p95 782ms2026-10-03 UTC: p95 713ms2026-10-04 UTC: p95 706ms2026-10-05 UTC: p95 683ms2026-10-06 UTC: p95 696ms2026-10-07 UTC: p95 662ms2026-10-08 UTC: p95 589ms2026-10-09 UTC: p95 624ms2026-10-10 UTC: p95 597ms2026-10-11 UTC: p95 565ms2026-10-12 UTC: p95 644ms2026-10-13 UTC: p95 644ms2026-10-14 UTC: p95 605ms2026-10-15 UTC: p95 558ms2026-10-16 UTC: p95 531ms2026-10-17 UTC: p95 726ms2026-10-18 UTC: p95 864ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 878ms2026-10-21 UTC: p95 894ms2026-10-22 UTC: p95 1.0s
Sep 23Oct 7Oct 22
Asia-Pacific
2.5sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 940ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.5s
Sep 23Oct 7Oct 22
US-Central
1.0sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 701ms2026-09-24 UTC: p95 666ms2026-09-25 UTC: p95 654ms2026-09-26 UTC: p95 887ms2026-09-27 UTC: p95 736ms2026-09-28 UTC: p95 620ms2026-09-29 UTC: p95 644ms2026-09-30 UTC: p95 644ms2026-10-01 UTC: p95 564ms2026-10-02 UTC: p95 550ms2026-10-03 UTC: p95 604ms2026-10-04 UTC: p95 690ms2026-10-05 UTC: p95 556ms2026-10-06 UTC: p95 528ms2026-10-07 UTC: p95 565ms2026-10-08 UTC: p95 459ms2026-10-09 UTC: p95 418ms2026-10-10 UTC: p95 530ms2026-10-11 UTC: p95 582ms2026-10-12 UTC: p95 583ms2026-10-13 UTC: p95 476ms2026-10-14 UTC: p95 607ms2026-10-15 UTC: p95 601ms2026-10-16 UTC: p95 642ms2026-10-17 UTC: p95 821ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.0s
Sep 23Oct 7Oct 22
Canada
935msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 531ms2026-09-24 UTC: p95 519ms2026-09-25 UTC: p95 526ms2026-09-26 UTC: p95 521ms2026-09-27 UTC: p95 564ms2026-09-28 UTC: p95 484ms2026-09-29 UTC: p95 599ms2026-09-30 UTC: p95 633ms2026-10-01 UTC: p95 451ms2026-10-02 UTC: p95 530ms2026-10-03 UTC: p95 512ms2026-10-04 UTC: p95 441ms2026-10-05 UTC: p95 481ms2026-10-06 UTC: p95 494ms2026-10-07 UTC: p95 543ms2026-10-08 UTC: p95 559ms2026-10-09 UTC: p95 489ms2026-10-10 UTC: p95 406ms2026-10-11 UTC: p95 618ms2026-10-12 UTC: p95 577ms2026-10-13 UTC: p95 511ms2026-10-14 UTC: p95 561ms2026-10-15 UTC: p95 511ms2026-10-16 UTC: p95 545ms2026-10-17 UTC: p95 769ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 935ms
Sep 23Oct 7Oct 22
UK
868msp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 698ms2026-09-24 UTC: p95 734ms2026-09-25 UTC: p95 743ms2026-09-26 UTC: p95 744ms2026-09-27 UTC: p95 774ms2026-09-28 UTC: p95 734ms2026-09-29 UTC: p95 775ms2026-09-30 UTC: p95 775ms2026-10-01 UTC: p95 583ms2026-10-02 UTC: p95 610ms2026-10-03 UTC: p95 585ms2026-10-04 UTC: p95 492ms2026-10-05 UTC: p95 637ms2026-10-06 UTC: p95 585ms2026-10-07 UTC: p95 611ms2026-10-08 UTC: p95 554ms2026-10-09 UTC: p95 666ms2026-10-10 UTC: p95 629ms2026-10-11 UTC: p95 678ms2026-10-12 UTC: p95 639ms2026-10-13 UTC: p95 435ms2026-10-14 UTC: p95 3.8s2026-10-15 UTC: p95 3.4s2026-10-16 UTC: p95 867ms2026-10-17 UTC: p95 665ms2026-10-18 UTC: p95 745ms2026-10-19 UTC: p95 857ms2026-10-20 UTC: p95 867ms2026-10-21 UTC: p95 698ms2026-10-22 UTC: p95 868ms
Sep 23Oct 7Oct 22
Southeast Asia
1.9sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 2.7s2026-09-24 UTC: p95 2.4s2026-09-25 UTC: p95 2.4s2026-09-26 UTC: p95 2.5s2026-09-27 UTC: p95 2.3s2026-09-28 UTC: p95 2.4s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.7s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.9s
Sep 23Oct 7Oct 22
Australia
2.9sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.9s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 893ms2026-10-06 UTC: p95 896ms2026-10-07 UTC: p95 971ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 946ms2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 2.6s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 3.0s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 3.1s2026-10-22 UTC: p95 2.9s
Sep 23Oct 7Oct 22
South America
1.8sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 2.2s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22

Check your own site while you wait on Postmark

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of Postmark fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Postmark fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Postmark's official status.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 899msstatus code: 401checked: Oct 22, 2026, 11:21 PM 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
      Checks passinglatency: 1611msstatus code: 401checked: Oct 22, 2026, 11:28 PM 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.
    • US-Central
      Checks passinglatency: 753msstatus code: 401checked: Oct 22, 2026, 11:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Postmark normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 636msstatus code: 401checked: Oct 22, 2026, 10:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Postmark normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1700msstatus code: 401checked: Oct 22, 2026, 11:13 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Postmark normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1050msstatus code: 401checked: Oct 22, 2026, 11:20 PM 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.
    • UK
      Checks passinglatency: 594msstatus code: 401checked: Oct 22, 2026, 11:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Postmark normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2328msstatus code: 401checked: Oct 22, 2026, 11:37 PM 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.
    • Southeast Asia
      Checks passinglatency: 1408msstatus code: 401checked: Oct 22, 2026, 11:28 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Postmark normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2473msstatus code: 401checked: Oct 22, 2026, 11:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Postmark normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

No probe events on record yet for Postmark.

check 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 check readings and Postmark's own claim at the time, side by side.

Full check history for Postmark: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Postmark uptime by RealUptime's checksLive, from this page's own readings.
[![Postmark uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Postmark down?", https://realuptime.io/outages/postmark. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Postmark's stated SLA

At or above your target

Our checks of Postmark failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.postmarkapp.com

RealUptime is not affiliated with Postmark; the name identifies what we checked, and nothing here speaks for Postmark's own team. We send a single web request to Postmark from 10 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.