Skip to content

Outage tracker / PagerDuty

Is PagerDuty down?

I'm having a problem

Checks passingchecked 2 minutes ago

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

As of Oct 22, 2026, 7:04 PM UTC, RealUptime's checks of PagerDuty passed in all 10 regions that returned a reading.

Front-door and live API checks

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

our check readinglive · checked Oct 22, 2026, 7:04 PM UTC
US-East1469 msChecks passing
US-West1128 msChecks passing
Europe1304 msChecks passing
Asia-Pacific2306 msChecks passing
US-Central522 msChecks passing
Canada993 msChecks passing
UK1400 msChecks passing
Southeast Asia1832 msChecks passing
Australia2148 msChecks passing
South America2675 msChecks passing
their status pagetheir claim, not our reading

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

PagerDuty response time, by region

US-East
1.7sp95 · 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 1.0s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 972ms2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 970ms2026-09-28 UTC: p95 982ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 901ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
US-West
1.7sp95 · 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 482ms2026-09-24 UTC: p95 538ms2026-09-25 UTC: p95 522ms2026-09-26 UTC: p95 587ms2026-09-27 UTC: p95 550ms2026-09-28 UTC: p95 563ms2026-09-29 UTC: p95 626ms2026-09-30 UTC: p95 666ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 938ms2026-10-14 UTC: p95 704ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s
Sep 23Oct 7Oct 22
Europe
1.4sp95 · 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 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
Asia-Pacific
2.4sp95 · 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.6s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.7s2026-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.6s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2.5s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.4s
Sep 23Oct 7Oct 22
US-Central
771msp95 · 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 1.3s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 916ms2026-09-29 UTC: p95 855ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 972ms2026-10-02 UTC: p95 957ms2026-10-03 UTC: p95 898ms2026-10-04 UTC: p95 838ms2026-10-05 UTC: p95 766ms2026-10-06 UTC: p95 825ms2026-10-07 UTC: p95 850ms2026-10-08 UTC: p95 900ms2026-10-09 UTC: p95 798ms2026-10-10 UTC: p95 822ms2026-10-11 UTC: p95 861ms2026-10-12 UTC: p95 791ms2026-10-13 UTC: p95 802ms2026-10-14 UTC: p95 796ms2026-10-15 UTC: p95 950ms2026-10-16 UTC: p95 798ms2026-10-17 UTC: p95 869ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 771ms
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 851ms2026-09-24 UTC: p95 926ms2026-09-25 UTC: p95 958ms2026-09-26 UTC: p95 848ms2026-09-27 UTC: p95 818ms2026-09-28 UTC: p95 820ms2026-09-29 UTC: p95 917ms2026-09-30 UTC: p95 934ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 944ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 989ms2026-10-13 UTC: p95 622ms2026-10-14 UTC: p95 862ms2026-10-15 UTC: p95 834ms2026-10-16 UTC: p95 750ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.3s
Sep 23Oct 7Oct 22
UK
1.1sp95 · 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 1.0s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 966ms2026-09-29 UTC: p95 830ms2026-09-30 UTC: p95 936ms2026-10-01 UTC: p95 917ms2026-10-02 UTC: p95 932ms2026-10-03 UTC: p95 917ms2026-10-04 UTC: p95 931ms2026-10-05 UTC: p95 870ms2026-10-06 UTC: p95 878ms2026-10-07 UTC: p95 764ms2026-10-08 UTC: p95 805ms2026-10-09 UTC: p95 893ms2026-10-10 UTC: p95 862ms2026-10-11 UTC: p95 869ms2026-10-12 UTC: p95 835ms2026-10-13 UTC: p95 877ms2026-10-14 UTC: p95 702ms2026-10-15 UTC: p95 682ms2026-10-16 UTC: p95 643ms2026-10-17 UTC: p95 934ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 998ms2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
Southeast Asia
3.2sp95 · 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.8s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.2s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 3.2s
Sep 23Oct 7Oct 22
Australia
2.7sp95 · 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 2.1s2026-09-24 UTC: p95 2.1s2026-09-25 UTC: p95 1.8s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 2.3s2026-09-28 UTC: p95 2.2s2026-09-29 UTC: p95 2.5s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 2.1s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.8s2026-10-06 UTC: p95 2.0s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 2.0s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.8s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 3.0s2026-10-19 UTC: p95 3.1s2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 2.7s
Sep 23Oct 7Oct 22
South America
3.0sp95 · 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.7s2026-09-24 UTC: p95 2.0s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 2.0s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 2.2s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 2.0s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 2.0s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 3.4s2026-10-19 UTC: p95 3.2s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 3.0s
Sep 23Oct 7Oct 22

Check your own site while you wait on PagerDuty

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

Get an email when our checks of PagerDuty 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 PagerDuty 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 PagerDuty'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: 1469msstatus code: 401checked: Oct 22, 2026, 7:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach PagerDuty normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1128msstatus code: 401checked: Oct 22, 2026, 6:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach PagerDuty normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 522msstatus code: 401checked: Oct 22, 2026, 6:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach PagerDuty normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 993msstatus code: 401checked: Oct 22, 2026, 7:02 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach PagerDuty normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2675msstatus code: 401checked: Oct 22, 2026, 6:53 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach PagerDuty 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: 1304msstatus code: 401checked: Oct 22, 2026, 7:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach PagerDuty normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 1400msstatus code: 401checked: Oct 22, 2026, 7:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach PagerDuty 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: 2306msstatus code: 401checked: Oct 22, 2026, 7:04 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach PagerDuty normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1832msstatus code: 401checked: Oct 22, 2026, 7:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach PagerDuty normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2148msstatus code: 401checked: Oct 22, 2026, 7:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach PagerDuty 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 PagerDuty, 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 PagerDuty yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for PagerDuty.

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

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

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

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

At or above your target

Our checks of PagerDuty 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 PagerDuty'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
https://api.pagerduty.com/incidents
secondary
https://status.pagerduty.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.pagerduty.com

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