Skip to content

Outage tracker / PagerDuty

Is PagerDuty down?

I'm having a problem

Operationalchecked 1 minute ago

We reached PagerDuty from all 10 regions we check.

As of Oct 5, 2026, 9:03 PM UTC, PagerDuty answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured PagerDuty (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 9:03 PM UTC
US-East783 msOperational
US-West1059 msOperational
Europe1000 msOperational
Asia-Pacific934 msOperational
US-Central491 msOperational
Canada563 msOperational
UK724 msOperational
Southeast Asia1201 msOperational
Australia1697 msOperational
South America1127 msOperational
their status pagetheir claim, not our reading

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

PagerDuty 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-06 UTC: p95 886ms2026-09-07 UTC: p95 816ms2026-09-08 UTC: p95 859ms2026-09-09 UTC: p95 826ms2026-09-10 UTC: p95 861ms2026-09-11 UTC: p95 876ms2026-09-12 UTC: p95 826ms2026-09-13 UTC: p95 818ms2026-09-14 UTC: p95 845ms2026-09-15 UTC: p95 877ms2026-09-16 UTC: p95 869ms2026-09-17 UTC: p95 852ms2026-09-18 UTC: p95 878ms2026-09-19 UTC: p95 923ms2026-09-20 UTC: p95 861ms2026-09-21 UTC: p95 889ms2026-09-22 UTC: p95 871ms2026-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.1s
Sep 6Sep 20Oct 5
US-West
1.2sp95 · 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 706ms2026-09-07 UTC: p95 744ms2026-09-08 UTC: p95 787ms2026-09-09 UTC: p95 375ms2026-09-10 UTC: p95 418ms2026-09-11 UTC: p95 366ms2026-09-12 UTC: p95 281ms2026-09-13 UTC: p95 354ms2026-09-14 UTC: p95 337ms2026-09-15 UTC: p95 407ms2026-09-16 UTC: p95 317ms2026-09-17 UTC: p95 415ms2026-09-18 UTC: p95 399ms2026-09-19 UTC: p95 431ms2026-09-20 UTC: p95 494ms2026-09-21 UTC: p95 514ms2026-09-22 UTC: p95 524ms2026-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.2s
Sep 6Sep 20Oct 5
Europe
1.1sp95 · 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 1.0s2026-09-07 UTC: p95 942ms2026-09-08 UTC: p95 860ms2026-09-09 UTC: p95 969ms2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-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.1s
Sep 6Sep 20Oct 5
Asia-Pacific
1.7sp95 · 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.3s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.5s2026-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.7s
Sep 6Sep 20Oct 5
US-Central
775msp95 · 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-06 UTC: p95 775ms2026-09-07 UTC: p95 732ms2026-09-08 UTC: p95 808ms2026-09-09 UTC: p95 662ms2026-09-10 UTC: p95 753ms2026-09-11 UTC: p95 804ms2026-09-12 UTC: p95 634ms2026-09-13 UTC: p95 834ms2026-09-14 UTC: p95 930ms2026-09-15 UTC: p95 809ms2026-09-16 UTC: p95 770ms2026-09-17 UTC: p95 532ms2026-09-18 UTC: p95 426ms2026-09-19 UTC: p95 410ms2026-09-20 UTC: p95 379ms2026-09-21 UTC: p95 441ms2026-09-22 UTC: p95 1.3s2026-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 775ms
Sep 6Sep 20Oct 5
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-06 UTC: p95 928ms2026-09-07 UTC: p95 977ms2026-09-08 UTC: p95 797ms2026-09-09 UTC: p95 891ms2026-09-10 UTC: p95 775ms2026-09-11 UTC: p95 808ms2026-09-12 UTC: p95 796ms2026-09-13 UTC: p95 775ms2026-09-14 UTC: p95 815ms2026-09-15 UTC: p95 811ms2026-09-16 UTC: p95 800ms2026-09-17 UTC: p95 854ms2026-09-18 UTC: p95 896ms2026-09-19 UTC: p95 868ms2026-09-20 UTC: p95 838ms2026-09-21 UTC: p95 861ms2026-09-22 UTC: p95 812ms2026-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.3s
Sep 6Sep 20Oct 5
UK
832msp95 · 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-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 980ms2026-09-18 UTC: p95 875ms2026-09-19 UTC: p95 872ms2026-09-20 UTC: p95 899ms2026-09-21 UTC: p95 900ms2026-09-22 UTC: p95 900ms2026-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 832ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.8s2026-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.2s
Sep 6Sep 20Oct 5
Australia
1.8sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.9s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.8s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 2.0s2026-09-14 UTC: p95 2.0s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 2.1s2026-09-18 UTC: p95 2.2s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 2.0s2026-09-22 UTC: p95 2.1s2026-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.8s
Sep 6Sep 20Oct 5
South America
1.4sp95 · 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-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 1.7s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.9s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 1.9s2026-09-17 UTC: p95 2.3s2026-09-18 UTC: p95 2.0s2026-09-19 UTC: p95 2.0s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 2.0s2026-09-22 UTC: p95 1.8s2026-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.4s
Sep 6Sep 20Oct 5

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

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

Get told when we measure this

We will tell you when our probes stop reaching PagerDuty, and again when they can reach it again. That is our own measurement from ten regions, not PagerDuty'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: 783msstatus code: 401checked: Oct 5, 2026, 8:55 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
      Operationallatency: 1059msstatus code: 401checked: Oct 5, 2026, 9:03 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
      Operationallatency: 491msstatus code: 401checked: Oct 5, 2026, 9:02 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
      Operationallatency: 563msstatus code: 401checked: Oct 5, 2026, 8:47 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
    Operationallatency: 1127msstatus code: 401checked: Oct 5, 2026, 8:52 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 1000msstatus code: 401checked: Oct 5, 2026, 8:56 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
      Operationallatency: 724msstatus code: 401checked: Oct 5, 2026, 9:02 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 934msstatus code: 401checked: Oct 5, 2026, 9:00 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
      Operationallatency: 1201msstatus code: 401checked: Oct 5, 2026, 9:02 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
      Operationallatency: 1697msstatus code: 401checked: Oct 5, 2026, 8:46 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 outages

No outages on record yet for PagerDuty.

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

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

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

At or above your target

We measured none of downtime for PagerDuty 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 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/
RealUptime is not affiliated with PagerDuty; the name identifies what we measured, 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 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.