PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if PagerDuty is down?

PulseWatch evaluates user reports and replay-approved automated evidence for PagerDuty. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported PagerDuty issues today?

As of Oct 12, 2026 21:59 UTC, 0 users had reported issues with PagerDuty in the previous 24 hours.

How can I report a PagerDuty outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is PagerDuty down right now?

NormalOfficial status last polled Oct 12, 2026 21:55 UTCwww.pagerduty.com Official status page

PagerDuty incident response and on-call

Are you on the PagerDuty team and see something inaccurate? Report it to us. We respond within one business day.

Is PagerDuty down right now?

No. PagerDuty has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 21:59 UTC

Normal

PagerDuty is operating normally

As of Oct 12, 2026 21:59 UTC

No elevated reports in the last 15 minutes. Baseline 4 reports/hour.

Reports 24h

Last incident

Apr 29, 2026 21:03 UTC

Trend

0/15m

Baseline

4/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for PagerDuty.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for PagerDuty. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

PagerDuty outage on April 29 — 33-minute disruption

Apr 29, 08:29 PM → Apr 29, 09:03 PM · 33 minutes · high

On April 29, 2026, PagerDuty experienced a service disruption. This incident was detected by user reports and third-party monitoring. The issue was resolved after 33 minutes at 21:03 UTC.

Peak reports

in 15 min

Total reports

during the incident

Duration

33 minutes

tracked by PulseWatch

Impact

Users experienced difficulty accessing the PagerDuty website. The primary issue reported by users was 'Website down.' While no specific regional impact was recorded, a total of 4 user reports were received during the incident, with monitoring systems grouping 6 related alerts. The incident was classified as high severity.

Top reported issues

Website down4

Incident timeline

Apr 29, 08:29 PM
PulseWatch detected elevated report volume (high severity)
Apr 29, 08:30 PM
Peak of 0 reports in 15 minutes (baseline 1.0)
Apr 29, 09:03 PM
Report volume returned to baseline — incident resolved

Official updates

Apr 29, 08:29 PM
PagerDuty status page acknowledged the incident.
View official source
Apr 29, 09:03 PM
Website down clustered from 3 sources across 6 signals. Suppressed 5 redundant alerts and flagged flapping behavior.

Reliability

Detected by PulseWatch

30-day uptime

99.99%

90-day uptime

99.99%

Calculated from PagerDuty's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.