Skip to content

Outage tracker / Postman

Is Postman down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Postman from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Postman 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 Postman (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East646 msOperational
US-West1417 msOperational
Europe832 msOperational
Asia-Pacific1029 msOperational
US-Central677 msOperational
Canada308 msOperational
UK356 msOperational
Southeast Asia1567 msOperational
Australia942 msOperational
South America770 msOperational
their status pagetheir claim, not our reading

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

from Postman's own status page, checked Oct 5, 2026, 7:52 PM UTC
Our probes and Postman's own status page agree: both show Postman as reachable 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
946msp95 · 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-06 UTC: p95 449ms2026-09-07 UTC: p95 467ms2026-09-08 UTC: p95 447ms2026-09-09 UTC: p95 532ms2026-09-10 UTC: p95 573ms2026-09-11 UTC: p95 743ms2026-09-12 UTC: p95 553ms2026-09-13 UTC: p95 560ms2026-09-14 UTC: p95 578ms2026-09-15 UTC: p95 690ms2026-09-16 UTC: p95 663ms2026-09-17 UTC: p95 753ms2026-09-18 UTC: p95 668ms2026-09-19 UTC: p95 707ms2026-09-20 UTC: p95 638ms2026-09-21 UTC: p95 735ms2026-09-22 UTC: p95 703ms2026-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 946ms
Sep 6Sep 20Oct 5
US-West
1.3sp95 · 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-06 UTC: p95 526ms2026-09-07 UTC: p95 504ms2026-09-08 UTC: p95 538ms2026-09-09 UTC: p95 419ms2026-09-10 UTC: p95 406ms2026-09-11 UTC: p95 453ms2026-09-12 UTC: p95 394ms2026-09-13 UTC: p95 427ms2026-09-14 UTC: p95 357ms2026-09-15 UTC: p95 545ms2026-09-16 UTC: p95 660ms2026-09-17 UTC: p95 621ms2026-09-18 UTC: p95 642ms2026-09-19 UTC: p95 589ms2026-09-20 UTC: p95 587ms2026-09-21 UTC: p95 664ms2026-09-22 UTC: p95 619ms2026-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.3s
Sep 6Sep 20Oct 5
Europe
699msp95 · 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-09-06 UTC: p95 424ms2026-09-07 UTC: p95 471ms2026-09-08 UTC: p95 414ms2026-09-09 UTC: p95 571ms2026-09-10 UTC: p95 680ms2026-09-11 UTC: p95 604ms2026-09-12 UTC: p95 657ms2026-09-13 UTC: p95 623ms2026-09-14 UTC: p95 665ms2026-09-15 UTC: p95 628ms2026-09-16 UTC: p95 658ms2026-09-17 UTC: p95 742ms2026-09-18 UTC: p95 685ms2026-09-19 UTC: p95 707ms2026-09-20 UTC: p95 696ms2026-09-21 UTC: p95 721ms2026-09-22 UTC: p95 724ms2026-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 699ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.8sp95 · 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 1.5s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 988ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.6s2026-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.8s
Sep 6Sep 20Oct 5
US-Central
565msp95 · 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 500ms2026-09-07 UTC: p95 539ms2026-09-08 UTC: p95 593ms2026-09-09 UTC: p95 573ms2026-09-10 UTC: p95 545ms2026-09-11 UTC: p95 761ms2026-09-12 UTC: p95 760ms2026-09-13 UTC: p95 657ms2026-09-14 UTC: p95 673ms2026-09-15 UTC: p95 742ms2026-09-16 UTC: p95 583ms2026-09-17 UTC: p95 470ms2026-09-18 UTC: p95 487ms2026-09-19 UTC: p95 490ms2026-09-20 UTC: p95 518ms2026-09-21 UTC: p95 471ms2026-09-22 UTC: p95 493ms2026-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 565ms
Sep 6Sep 20Oct 5
Canada
669msp95 · 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-06 UTC: p95 948ms2026-09-07 UTC: p95 886ms2026-09-08 UTC: p95 799ms2026-09-09 UTC: p95 779ms2026-09-10 UTC: p95 765ms2026-09-11 UTC: p95 485ms2026-09-12 UTC: p95 711ms2026-09-13 UTC: p95 606ms2026-09-14 UTC: p95 653ms2026-09-15 UTC: p95 643ms2026-09-16 UTC: p95 558ms2026-09-17 UTC: p95 505ms2026-09-18 UTC: p95 470ms2026-09-19 UTC: p95 536ms2026-09-20 UTC: p95 559ms2026-09-21 UTC: p95 557ms2026-09-22 UTC: p95 579ms2026-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 669ms
Sep 6Sep 20Oct 5
UK
365msp95 · 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 455ms2026-09-07 UTC: p95 337ms2026-09-08 UTC: p95 317ms2026-09-09 UTC: p95 448ms2026-09-10 UTC: p95 449ms2026-09-11 UTC: p95 508ms2026-09-12 UTC: p95 524ms2026-09-13 UTC: p95 521ms2026-09-14 UTC: p95 452ms2026-09-15 UTC: p95 388ms2026-09-16 UTC: p95 401ms2026-09-17 UTC: p95 427ms2026-09-18 UTC: p95 426ms2026-09-19 UTC: p95 399ms2026-09-20 UTC: p95 422ms2026-09-21 UTC: p95 466ms2026-09-22 UTC: p95 563ms2026-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 365ms
Sep 6Sep 20Oct 5
Southeast Asia
2.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 2.0s2026-09-22 UTC: p95 1.7s2026-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.1s
Sep 6Sep 20Oct 5
Australia
1.7sp95 · 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 605ms2026-09-07 UTC: p95 659ms2026-09-08 UTC: p95 748ms2026-09-09 UTC: p95 682ms2026-09-10 UTC: p95 775ms2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.6s2026-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.7s
Sep 6Sep 20Oct 5
South America
1.1sp95 · 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 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.8s2026-09-18 UTC: p95 1.8s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.6s2026-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.1s
Sep 6Sep 20Oct 5

Is it Postman, 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 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: 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 Postman go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Postman, and again when they can reach it again. That is our own measurement from ten regions, not Postman'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: 646msstatus code: 401checked: Oct 5, 2026, 8:15 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
      Operationallatency: 1417msstatus code: 401checked: Oct 5, 2026, 8:13 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
      Operationallatency: 677msstatus code: 401checked: Oct 5, 2026, 8:14 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
      Operationallatency: 308msstatus code: 401checked: Oct 5, 2026, 8:09 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
    Operationallatency: 770msstatus code: 401checked: Oct 5, 2026, 8:12 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 832msstatus code: 401checked: Oct 5, 2026, 8:06 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
      Operationallatency: 356msstatus code: 401checked: Oct 5, 2026, 8:02 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1029msstatus code: 401checked: Oct 5, 2026, 8:10 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
      Operationallatency: 1567msstatus code: 401checked: Oct 5, 2026, 8:03 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
      Operationallatency: 942msstatus code: 401checked: Oct 5, 2026, 8:06 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 outages

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

measured 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 measurements and Postman's own claim at the time, side by side.

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

Postman uptime measured by RealUptimeLive, from this page's own readings.
[![Postman uptime measured by RealUptime](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 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 Postman's SLA implies, from our measurement

At or above your target

We measured none of downtime for Postman 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 Postman'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.getpostman.com/me
secondary
https://www.postman.com/
secondary
https://status.postman.com/api/v2/status.json
RealUptime is not affiliated with Postman; the name identifies what we measured, 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 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.