Is PagerDuty Down? How to Check PagerDuty Status Right Now

PagerDuty is the on-call and incident response platform that notifies engineers when production systems fail. When PagerDuty itself goes down, the irony is sharp: the system designed to tell you something is broken stops working — silently. On-call rotations go dark, alerts queue without delivery, and incidents escalate without human response. Here's how to confirm whether PagerDuty is down and how to protect yourself.

Is PagerDuty Down Right Now?

Check these in order:

1. Statusfield — PagerDuty status — real-time monitoring of PagerDuty's platform health.
2. PagerDuty's official status page — status.pagerduty.com shows active incidents and component health by region.
3. Twitter/X — search pagerduty down sorted by Latest. SREs and on-call engineers post quickly when alerts stop firing.
4. Slack — check your team's #oncall or #incidents channel; others on your team may have noticed before you did.

PagerDuty Components That Can Fail Independently

PagerDuty is a multi-region, multi-component platform. An outage can affect one area without taking down everything:

Component	What breaks when it fails
Event Routing	Incoming alerts from monitoring tools (Datadog, CloudWatch, Grafana) stop creating incidents
Notifications	SMS, phone calls, push notifications, and Slack messages stop delivering
Escalation Policies	Alerts trigger but don't escalate to the next responder when the first misses them
Web App / UI	Responders can't acknowledge, resolve, or view incidents via the dashboard
Mobile App	Push notifications stop arriving; app may show stale incident state
API	Programmatic alert creation and incident management stop working
Schedules	On-call rotation calculations break; wrong responder may be notified
Webhooks & Extensions	Integrations with Jira, Slack, ServiceNow, and other tools stop firing

Common Errors During a PagerDuty Outage

Symptom	Likely cause
Alerts firing in source tool but no PagerDuty incident created	Event routing or Events API degraded
Incident created but no SMS/call received	Notification delivery pipeline degraded
Acknowledged in app but team member says they never got the call	Notification service partial outage
PagerDuty app returns 503 or won't load	Web app or edge infrastructure degraded
API returns 503 Service Unavailable on POST /incidents	API gateway or incident creation service degraded
Escalation didn't happen after timeout	Escalation engine degraded
Mobile app shows "last updated 2 hours ago"	Mobile sync or push notification service degraded

The Core Problem: Your Alerting Tool Is the Single Point of Failure

An alerting platform outage creates a catch-22. You're relying on PagerDuty to tell you when systems fail — but if PagerDuty fails, nothing tells you. Engineering teams that depend entirely on a single alerting chain are exposed to this failure mode.

Mitigation strategies:

1. Secondary alerting path — subscribe to your critical services via Statusfield to receive notifications through a path independent of PagerDuty
2. Status page subscriptions — subscribe to status.pagerduty.com for email/SMS when PagerDuty itself has an incident
3. Redundant on-call rotation — keep a backup contact method (team Slack + SMS group) for your current on-call engineer that doesn't route through PagerDuty
4. Runbook: "PagerDuty is down" — write and distribute this runbook before you need it; document who to call, what Slack channel to use, and how long to wait before escalating manually
5. Smoke test your alerting — regularly send a test alert end-to-end (source tool → PagerDuty → notification) to confirm the whole chain is working before an incident

How PagerDuty Handles Its Own Outages

PagerDuty publishes post-incident reviews (PIRs) on its status page for significant outages. Historical patterns:

• 2019 (multi-hour global outage): Database failover failure caused widespread notification delays
• 2020 (notification delays): Traffic spike during a major cloud incident caused queuing in the notification delivery pipeline
• Regional vs global: Most PagerDuty outages affect specific regions (US, EU) while leaving others operational — if you're in the affected region, switching to manual processes may be the fastest path

When PagerDuty's status page is itself unavailable, check their Twitter/X account @PagerDuty for live updates from the company.

What to Do During a PagerDuty Outage

1. Confirm the outage scope — check status.pagerduty.com and Statusfield to understand which components and regions are affected
2. Activate backup alerting — use whatever secondary method your team has (SMS group, Slack channel, phone tree)
3. Notify your on-call engineer directly — don't wait for PagerDuty to recover; reach out through Slack, phone, or email
4. Increase monitoring frequency — if your team is manually watching dashboards, set calendar reminders or Slack reminders at short intervals
5. Document the gap — track which alerts were missed and their timestamps so you can review them after PagerDuty recovers
6. Post-incident: add redundancy — use the incident as a forcing function to add a secondary alert path

Monitor PagerDuty Automatically

Statusfield continuously monitors PagerDuty's status and sends instant alerts when incidents are detected — so you know PagerDuty is having issues before your on-call engineer wonders why their phone isn't ringing.