Skip to content

Outage tracker / Postman

Is Postman down?

I'm having a problem

Vendor reports no incidentWhat Postman reports

Postman reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:48 UTC.

Postman's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

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

As of Oct 22, 2026, 9:50 PM UTC, RealUptime's checks of Postman passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:50 PM UTC
US-East1166 msChecks passing
US-West1264 msChecks passing
Europe651 msChecks passing
Asia-Pacific2329 msChecks passing
US-Central646 msChecks passing
Canada873 msChecks passing
UK1262 msChecks passing
Southeast Asia2532 msChecks passing
Australia1891 msChecks passing
South America1722 msChecks passing
their status pagetheir claim, not our reading

Postman reports: All systems operational (“All Systems Operational”)

from Postman's own status page, checked Oct 22, 2026, 9:32 PM UTC
Postman's own status page shows no incident, and our checks of Postman pass right now.

Postman's own component breakdown, as they publish it

  • Postman Platform on DesktopOperational
  • Postman Platform on DesktopOperational
  • Postman Platform on BrowserOperational
  • Postman Platform on BrowserOperational
  • Postman LoginOperational
  • Postman LoginOperational
  • Postman MocksOperational
  • Postman MonitorsOperational
  • Postman APIOperational
  • Postman MocksOperational
  • Postman APIOperational
  • Postman SearchOperational
  • Postman API Network (API Explore)Operational
  • Run ButtonOperational
  • Postman SearchOperational
  • Public Collection DocumentationOperational
  • NewmanOperational
  • Postman Learning Center and DocumentationOperational
  • Postman Support and Community ForumOperational
  • Postman IntegrationsOperational
  • Postman InterceptorOperational
  • Marketing WebsiteOperational
  • PostbotOperational
  • Postman VS Code extensionOperational
  • API BuilderOperational
  • API SpecificationsOperational
  • Collection RunnerOperational
  • Postman CLIOperational
  • Agent ModeOperational

These are Postman's components, named and scored by Postman. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Postman's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Postman response time, by region

US-East
1.6sp95 · 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 838ms2026-09-24 UTC: p95 850ms2026-09-25 UTC: p95 682ms2026-09-26 UTC: p95 672ms2026-09-27 UTC: p95 708ms2026-09-28 UTC: p95 626ms2026-09-29 UTC: p95 700ms2026-09-30 UTC: p95 652ms2026-10-01 UTC: p95 917ms2026-10-02 UTC: p95 893ms2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 930ms2026-10-05 UTC: p95 916ms2026-10-06 UTC: p95 929ms2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 994ms2026-10-09 UTC: p95 991ms2026-10-10 UTC: p95 968ms2026-10-11 UTC: p95 959ms2026-10-12 UTC: p95 953ms2026-10-13 UTC: p95 854ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 983ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.6s
Sep 23Oct 7Oct 22
US-West
1.8sp95 · 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 582ms2026-09-24 UTC: p95 594ms2026-09-25 UTC: p95 611ms2026-09-26 UTC: p95 581ms2026-09-27 UTC: p95 516ms2026-09-28 UTC: p95 661ms2026-09-29 UTC: p95 808ms2026-09-30 UTC: p95 844ms2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 912ms2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.8s
Sep 23Oct 7Oct 22
Europe
989msp95 · 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 755ms2026-09-24 UTC: p95 654ms2026-09-25 UTC: p95 627ms2026-09-26 UTC: p95 713ms2026-09-27 UTC: p95 650ms2026-09-28 UTC: p95 655ms2026-09-29 UTC: p95 532ms2026-09-30 UTC: p95 590ms2026-10-01 UTC: p95 700ms2026-10-02 UTC: p95 780ms2026-10-03 UTC: p95 838ms2026-10-04 UTC: p95 755ms2026-10-05 UTC: p95 740ms2026-10-06 UTC: p95 834ms2026-10-07 UTC: p95 810ms2026-10-08 UTC: p95 813ms2026-10-09 UTC: p95 684ms2026-10-10 UTC: p95 661ms2026-10-11 UTC: p95 445ms2026-10-12 UTC: p95 605ms2026-10-13 UTC: p95 612ms2026-10-14 UTC: p95 624ms2026-10-15 UTC: p95 676ms2026-10-16 UTC: p95 694ms2026-10-17 UTC: p95 862ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 997ms2026-10-22 UTC: p95 989ms
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.7s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.9s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.8s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 2s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.5s2026-10-18 UTC: p95 2.9s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.5s
Sep 23Oct 7Oct 22
US-Central
948msp95 · 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 517ms2026-09-24 UTC: p95 595ms2026-09-25 UTC: p95 464ms2026-09-26 UTC: p95 577ms2026-09-27 UTC: p95 558ms2026-09-28 UTC: p95 584ms2026-09-29 UTC: p95 495ms2026-09-30 UTC: p95 568ms2026-10-01 UTC: p95 474ms2026-10-02 UTC: p95 499ms2026-10-03 UTC: p95 516ms2026-10-04 UTC: p95 576ms2026-10-05 UTC: p95 579ms2026-10-06 UTC: p95 667ms2026-10-07 UTC: p95 574ms2026-10-08 UTC: p95 532ms2026-10-09 UTC: p95 554ms2026-10-10 UTC: p95 749ms2026-10-11 UTC: p95 568ms2026-10-12 UTC: p95 589ms2026-10-13 UTC: p95 580ms2026-10-14 UTC: p95 544ms2026-10-15 UTC: p95 563ms2026-10-16 UTC: p95 566ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 948ms
Sep 23Oct 7Oct 22
Canada
1.3sp95 · 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 673ms2026-09-24 UTC: p95 840ms2026-09-25 UTC: p95 633ms2026-09-26 UTC: p95 730ms2026-09-27 UTC: p95 512ms2026-09-28 UTC: p95 630ms2026-09-29 UTC: p95 598ms2026-09-30 UTC: p95 582ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 659ms2026-10-04 UTC: p95 702ms2026-10-05 UTC: p95 668ms2026-10-06 UTC: p95 680ms2026-10-07 UTC: p95 791ms2026-10-08 UTC: p95 550ms2026-10-09 UTC: p95 692ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 652ms2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 962ms2026-10-16 UTC: p95 920ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
UK
1.5sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 457ms2026-09-24 UTC: p95 624ms2026-09-25 UTC: p95 555ms2026-09-26 UTC: p95 429ms2026-09-27 UTC: p95 529ms2026-09-28 UTC: p95 622ms2026-09-29 UTC: p95 599ms2026-09-30 UTC: p95 529ms2026-10-01 UTC: p95 612ms2026-10-02 UTC: p95 743ms2026-10-03 UTC: p95 532ms2026-10-04 UTC: p95 466ms2026-10-05 UTC: p95 361ms2026-10-06 UTC: p95 370ms2026-10-07 UTC: p95 350ms2026-10-08 UTC: p95 398ms2026-10-09 UTC: p95 463ms2026-10-10 UTC: p95 436ms2026-10-11 UTC: p95 391ms2026-10-12 UTC: p95 424ms2026-10-13 UTC: p95 378ms2026-10-14 UTC: p95 454ms2026-10-15 UTC: p95 355ms2026-10-16 UTC: p95 446ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 979ms2026-10-22 UTC: p95 1.5s
Sep 23Oct 7Oct 22
Southeast Asia
3.1sp95 · 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 1.7s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 2.2s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 2.1s2026-10-05 UTC: p95 2.2s2026-10-06 UTC: p95 2.0s2026-10-07 UTC: p95 2.1s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.2s2026-10-10 UTC: p95 2.3s2026-10-11 UTC: p95 2.5s2026-10-12 UTC: p95 2.0s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.9s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.7s2026-10-19 UTC: p95 2.6s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 3.1s
Sep 23Oct 7Oct 22
Australia
2.3sp95 · 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.6s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.8s2026-10-18 UTC: p95 3.0s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 2.8s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.3s
Sep 23Oct 7Oct 22
South America
2.7sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 993ms2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 3.1s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.7s
Sep 23Oct 7Oct 22

Check your own site while you wait on Postman

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 Postman. It cannot diagnose Postman's own systems.

What we measured, function by function

Postman 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

Email me when Postman reports an incident on its status page, and again when it reports it resolved.

Get an email when Postman reports an incident

Email me when Postman reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Postman's own statement from its status page, with our regional reading beside it.

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: 1166msstatus code: 401checked: Oct 22, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Postman normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1264msstatus code: 401checked: Oct 22, 2026, 9:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Postman normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 646msstatus code: 401checked: Oct 22, 2026, 9:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Postman normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 873msstatus code: 401checked: Oct 22, 2026, 9:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Postman normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1722msstatus code: 401checked: Oct 22, 2026, 9:33 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Postman 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: 651msstatus code: 401checked: Oct 22, 2026, 9:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Postman normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 1262msstatus code: 401checked: Oct 22, 2026, 9:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Postman 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: 2329msstatus code: 401checked: Oct 22, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Postman normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2532msstatus code: 401checked: Oct 22, 2026, 9:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Postman normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1891msstatus code: 401checked: Oct 22, 2026, 9:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Postman 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 Postman, 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 Postman yet, which is not evidence that nothing is wrong.

Recent probe events

Api Builder flows are affected for US customers, 25mdeclared on their status page2026-09-10
postman site is having issues, 23mdeclared on their status page2026-08-13
Marketing website, 30mdeclared on their status page2026-07-22
Collections and Environments view scenarios are degraded, 2h 16mdeclared on their status page2026-07-17
Infrastructural issues for Flows running in the cloud, 37mdeclared on their status page2026-07-06
Elevated error rates for Agent Mode, 30mdeclared on their status page2026-06-19
Error in downloading unclaimed account reports, 6h 40mdeclared on their status page2026-06-10
Flows logic blocks report an error when running locally in the app, 2h 45mdeclared on their status page2026-04-25

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

We have been measuring Postman 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 Postman covering any window you pick, with our check readings and Postman's own claim at the time, side by side.

Full check history for Postman: 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

Postman uptime by RealUptime's checksLive, from this page's own readings.
[![Postman uptime by RealUptime's checks](https://realuptime.io/outages/postman/badge.svg?days=30)](https://realuptime.io/outages/postman)
<a href="https://realuptime.io/outages/postman"><img src="https://realuptime.io/outages/postman/badge.svg?days=30" alt="Postman 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 Postman down?", https://realuptime.io/outages/postman. 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.

What we check

primaryfunctional: live API
https://api.getpostman.com/me
secondary
https://www.postman.com/
secondary
https://status.postman.com/api/v2/status.json

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.getpostman.com

RealUptime is not affiliated with Postman; the name identifies what we checked, and nothing here speaks for Postman's own team. We send a single web request to Postman from 10 regions on our own schedule and time the response. We do not see inside Postman's systems, do not use an account or real transaction, and are not the same signal Postman's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Postman 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.