Skip to content

Outage tracker / PagerDuty

Is PagerDuty down?

I'm having a problem

Operationalchecked 23 minutes ago

We reached PagerDuty from all 4 regions we check.

Functional endpoints verified

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

our independent probeslive · checked Sep 3, 2026, 1:07 AM UTC
US-East1048 msOperational
US-West647 msOperational
Europe843 msOperational
Asia-Pacific1380 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.0sp95 · 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-08-20 UTC: p95 880ms2026-08-21 UTC: p95 748ms2026-08-22 UTC: p95 593ms2026-08-23 UTC: p95 760ms2026-08-24 UTC: p95 663ms2026-08-25 UTC: p95 764ms2026-08-26 UTC: p95 760ms2026-08-27 UTC: p95 542ms2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.0s2026-08-31 UTC: p95 944ms2026-09-01 UTC: p95 942ms2026-09-02 UTC: p95 1.4s2026-09-03 UTC: p95 1.0s
Aug 5Aug 19Sep 3
US-West
451msp95 · 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-08-20 UTC: p95 296ms2026-08-21 UTC: p95 422ms2026-08-22 UTC: p95 338ms2026-08-23 UTC: p95 483ms2026-08-24 UTC: p95 510ms2026-08-25 UTC: p95 433ms2026-08-26 UTC: p95 378ms2026-08-27 UTC: p95 515ms2026-08-28 UTC: p95 500ms2026-08-29 UTC: p95 354ms2026-08-30 UTC: p95 689ms2026-08-31 UTC: p95 444ms2026-09-01 UTC: p95 353ms2026-09-02 UTC: p95 588ms2026-09-03 UTC: p95 451ms
Aug 5Aug 19Sep 3
Europe
764msp95 · 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-08-20 UTC: p95 781ms2026-08-21 UTC: p95 1.1s2026-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 1.0s2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 996ms2026-08-26 UTC: p95 988ms2026-08-27 UTC: p95 916ms2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 915ms2026-08-30 UTC: p95 961ms2026-08-31 UTC: p95 984ms2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 764ms
Aug 5Aug 19Sep 3
Asia-Pacific
1.6sp95 · 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-08-20 UTC: p95 911ms2026-08-21 UTC: p95 1.2s2026-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.6s2026-09-02 UTC: p95 1.6s2026-09-03 UTC: p95 1.6s
Aug 5Aug 19Sep 3

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.

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

  • US-East
    Operationallatency: 1048msstatus code: 401checked: Sep 3, 2026, 1:07 AM 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: 647msstatus code: 401checked: Sep 3, 2026, 1:02 AM 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.
  • Europe
    Operationallatency: 843msstatus code: 401checked: Sep 3, 2026, 1:07 AM 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.
  • Asia-Pacific
    Operationallatency: 1380msstatus code: 401checked: Sep 3, 2026, 1:06 AM 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.
  • US-Central
    Not monitored from this regionPagerDuty is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionPagerDuty is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionPagerDuty is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionPagerDuty is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionPagerDuty is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionPagerDuty is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

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

Tell me when this goes down

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.

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 337h 30m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 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 4 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. PagerDuty operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.