Skip to content

Outage tracker / Postmark

Is Postmark down?

I'm having a problem

Operationalchecked 8 minutes ago

We reached Postmark from all 10 regions we check.

As of Oct 5, 2026, 8:07 PM UTC, Postmark answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 8:07 PM UTC
US-East429 msOperational
US-West377 msOperational
Europe581 msOperational
Asia-Pacific735 msOperational
US-Central321 msOperational
Canada449 msOperational
UK587 msOperational
Southeast Asia951 msOperational
Australia740 msOperational
South America1279 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
534msp95 · 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-09-06 UTC: p95 366ms2026-09-07 UTC: p95 355ms2026-09-08 UTC: p95 324ms2026-09-09 UTC: p95 343ms2026-09-10 UTC: p95 298ms2026-09-11 UTC: p95 374ms2026-09-12 UTC: p95 346ms2026-09-13 UTC: p95 339ms2026-09-14 UTC: p95 367ms2026-09-15 UTC: p95 367ms2026-09-16 UTC: p95 426ms2026-09-17 UTC: p95 414ms2026-09-18 UTC: p95 445ms2026-09-19 UTC: p95 460ms2026-09-20 UTC: p95 446ms2026-09-21 UTC: p95 406ms2026-09-22 UTC: p95 471ms2026-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 534ms
Sep 6Sep 20Oct 5
US-West
633msp95 · 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-09-06 UTC: p95 599ms2026-09-07 UTC: p95 530ms2026-09-08 UTC: p95 565ms2026-09-09 UTC: p95 351ms2026-09-10 UTC: p95 301ms2026-09-11 UTC: p95 390ms2026-09-12 UTC: p95 276ms2026-09-13 UTC: p95 386ms2026-09-14 UTC: p95 282ms2026-09-15 UTC: p95 369ms2026-09-16 UTC: p95 448ms2026-09-17 UTC: p95 519ms2026-09-18 UTC: p95 401ms2026-09-19 UTC: p95 418ms2026-09-20 UTC: p95 500ms2026-09-21 UTC: p95 508ms2026-09-22 UTC: p95 472ms2026-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 633ms
Sep 6Sep 20Oct 5
Europe
676msp95 · 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-06 UTC: p95 697ms2026-09-07 UTC: p95 621ms2026-09-08 UTC: p95 664ms2026-09-09 UTC: p95 635ms2026-09-10 UTC: p95 715ms2026-09-11 UTC: p95 679ms2026-09-12 UTC: p95 679ms2026-09-13 UTC: p95 658ms2026-09-14 UTC: p95 710ms2026-09-15 UTC: p95 769ms2026-09-16 UTC: p95 706ms2026-09-17 UTC: p95 712ms2026-09-18 UTC: p95 660ms2026-09-19 UTC: p95 664ms2026-09-20 UTC: p95 660ms2026-09-21 UTC: p95 683ms2026-09-22 UTC: p95 732ms2026-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 676ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.2sp95 · 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-09-06 UTC: p95 982ms2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 910ms2026-09-11 UTC: p95 856ms2026-09-12 UTC: p95 995ms2026-09-13 UTC: p95 962ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.0s2026-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.2s
Sep 6Sep 20Oct 5
US-Central
567msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 610ms2026-09-07 UTC: p95 621ms2026-09-08 UTC: p95 672ms2026-09-09 UTC: p95 594ms2026-09-10 UTC: p95 643ms2026-09-11 UTC: p95 735ms2026-09-12 UTC: p95 547ms2026-09-13 UTC: p95 627ms2026-09-14 UTC: p95 763ms2026-09-15 UTC: p95 564ms2026-09-16 UTC: p95 513ms2026-09-17 UTC: p95 568ms2026-09-18 UTC: p95 701ms2026-09-19 UTC: p95 598ms2026-09-20 UTC: p95 656ms2026-09-21 UTC: p95 686ms2026-09-22 UTC: p95 721ms2026-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 567ms
Sep 6Sep 20Oct 5
Canada
479msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 485ms2026-09-07 UTC: p95 483ms2026-09-08 UTC: p95 554ms2026-09-09 UTC: p95 577ms2026-09-10 UTC: p95 468ms2026-09-11 UTC: p95 577ms2026-09-12 UTC: p95 593ms2026-09-13 UTC: p95 627ms2026-09-14 UTC: p95 476ms2026-09-15 UTC: p95 527ms2026-09-16 UTC: p95 555ms2026-09-17 UTC: p95 574ms2026-09-18 UTC: p95 485ms2026-09-19 UTC: p95 548ms2026-09-20 UTC: p95 599ms2026-09-21 UTC: p95 545ms2026-09-22 UTC: p95 580ms2026-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 479ms
Sep 6Sep 20Oct 5
UK
648msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 612ms2026-09-07 UTC: p95 540ms2026-09-08 UTC: p95 560ms2026-09-09 UTC: p95 641ms2026-09-10 UTC: p95 737ms2026-09-11 UTC: p95 629ms2026-09-12 UTC: p95 680ms2026-09-13 UTC: p95 644ms2026-09-14 UTC: p95 596ms2026-09-15 UTC: p95 632ms2026-09-16 UTC: p95 666ms2026-09-17 UTC: p95 653ms2026-09-18 UTC: p95 649ms2026-09-19 UTC: p95 656ms2026-09-20 UTC: p95 687ms2026-09-21 UTC: p95 818ms2026-09-22 UTC: p95 712ms2026-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 648ms
Sep 6Sep 20Oct 5
Southeast Asia
1.7sp95 · 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-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.8s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 2.2s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 2.5s2026-09-22 UTC: p95 2.4s2026-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.7s
Sep 6Sep 20Oct 5
Australia
929msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.3s2026-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 929ms
Sep 6Sep 20Oct 5
South America
2.0sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 848ms2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 968ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 907ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.3s2026-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 2.0s
Sep 6Sep 20Oct 5

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: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Postmark go down, and when it is back

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.

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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 429msstatus code: 401checked: Oct 5, 2026, 7:50 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
      Operationallatency: 377msstatus code: 401checked: Oct 5, 2026, 8:07 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
      Operationallatency: 321msstatus code: 401checked: Oct 5, 2026, 7:20 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
      Operationallatency: 449msstatus code: 401checked: Oct 5, 2026, 7:32 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
    Operationallatency: 1279msstatus code: 401checked: Oct 5, 2026, 8:00 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 581msstatus code: 401checked: Oct 5, 2026, 7:51 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
      Operationallatency: 587msstatus code: 401checked: Oct 5, 2026, 7:55 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 735msstatus code: 401checked: Oct 5, 2026, 8:06 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
      Operationallatency: 951msstatus code: 401checked: Oct 5, 2026, 7:20 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
      Operationallatency: 740msstatus code: 401checked: Oct 5, 2026, 7:56 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 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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.