PagerDuty / Incident Management

PagerDuty Status: How to Check If PagerDuty Is Down Right Now (2026)

Updated June 2026 ยท 8 min read ยท API Status Check

Quick Answer

Check PagerDuty status at status.pagerduty.com (official) or apistatuscheck.com/is-pagerduty-down for independent real-time monitoring.

Staff Pick

๐Ÿ“ก Monitor your APIs โ€” know when they go down before your users do

Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.

Start Free โ†’

Affiliate link โ€” we may earn a commission at no extra cost to you

The Official PagerDuty Status Page

PagerDuty maintains an official status page at status.pagerduty.com. This page shows real-time status for all PagerDuty services:

Alerting & Notifications: Phone calls, SMS, push notifications, and email alerts fired from escalation policies
Event Ingestion: Receiving events from monitoring integrations (Datadog, Prometheus, CloudWatch, etc.) via the Events API
Incident Management: Creating, acknowledging, and resolving incidents in the PagerDuty UI and API
PagerDuty Web App: The pagerduty.com dashboard, on-call schedules, and service management
Mobile App: iOS and Android app for on-call engineers to receive and manage alerts
REST API: Third-party integrations and automation using the PagerDuty REST API

What Each PagerDuty Status Means

Operational: All PagerDuty systems are working normally. If you're not receiving alerts, check your escalation policies, notification rules, contact methods, and whether the integration source (Datadog, AWS, etc.) is actually firing events.
Degraded Performance: PagerDuty is processing events but slower than normal. Expect delayed alert delivery โ€” notifications may arrive minutes late. Incidents are still being created, just with latency.
Partial Outage: A specific component is failing. Often this means phone call delivery is down while email alerts still work, or one region is affected. Check which component is degraded and switch to a working notification channel.
Major Outage: PagerDuty alerting is down for most users. Your monitoring tools are still firing events, but PagerDuty can't deliver notifications to your on-call team. Activate your manual fallback procedures immediately.
Under Maintenance: Planned maintenance. PagerDuty typically schedules these during low-traffic windows and provides advance notice via status.pagerduty.com.
๐Ÿ“ก
Recommended

Monitor your alerting tool independently

The hardest outage to catch is when your alerting system itself goes down. Better Stack monitors PagerDuty independently so you know before your on-call team goes dark.

Try Better Stack Free โ†’

The Unique Problem: Your Alerting Tool Needs Monitoring Too

PagerDuty sits in a uniquely difficult position in your infrastructure stack. It is the system you rely on to tell you when everything else breaks โ€” which means if PagerDuty itself breaks, you may not find out until a production incident has been silently burning for hours.

This is not theoretical. PagerDuty has had significant incidents where notification delivery failed across specific channels (often SMS or phone calls) while the status page lagged behind real user impact. Engineering teams running post-mortems after silent outages frequently discover the root cause was a PagerDuty notification failure โ€” not a missed alert from their monitoring stack.

Why This Matters for On-Call Teams

A PagerDuty notification failure during a 3 AM production incident is a company-level event. The engineers on call have no idea something is wrong. Customers are affected. Your monitoring tools are firing alerts โ€” PagerDuty just isn't delivering them. This is why independent PagerDuty status monitoring is critical infrastructure, not a nice-to-have.

5 Ways to Check PagerDuty Status Right Now

1.

Official PagerDuty Status Page

Visit status.pagerduty.com for real-time component status. Subscribe to email or webhook notifications for incident updates and detailed post-mortems.

status.pagerduty.com โ†’
2.

API Status Check (Independent Monitor)

APIStatusCheck independently monitors PagerDuty's endpoints and shows real uptime data โ€” monitoring that PagerDuty doesn't control.

Check live PagerDuty status โ†’
3.

X/Twitter Search

Search 'PagerDuty down' or 'PagerDuty alerts not working' on X. On-call engineers report missed pages in real time โ€” often faster than the official status update.

Search X for 'PagerDuty down' โ†’
4.

Test a PagerDuty Integration Directly

Send a test event to your PagerDuty Events API integration key to verify event ingestion is working. A 202 response means events are being accepted.

curl -X POST https://events.pagerduty.com/v2/enqueue -H "Content-Type: application/json" -d '{"routing_key":"YOUR_INTEGRATION_KEY","event_action":"trigger","payload":{"summary":"Test event","source":"test","severity":"info"}}'
5.

Check the PagerDuty Community Forum

The PagerDuty Community Forum often has threads with other teams reporting and discussing incidents in real time, especially for complex partial outages.

PagerDuty Community โ†’

Common PagerDuty Problems and Their Causes

Not every PagerDuty problem is an outage. Here are the most common symptoms and what actually causes them:

Alerts not firing / no page receivedCheck this order: (1) Is status.pagerduty.com showing an incident? (2) Did your monitoring tool actually fire the event? Check Datadog/AWS event log. (3) Are your escalation policies correctly configured? (4) Are notification rules set to the right channel (phone vs. SMS vs. push)?
PagerDuty phone call alerts not workingPhone call delivery is the most common single-channel failure during PagerDuty incidents. Always configure at least two notification methods (phone + SMS + push) so a single channel failure doesn't silence your on-call.
Duplicate alerts / alert stormUsually an upstream monitoring tool misconfiguration, not PagerDuty. Check your alert threshold and re-trigger settings. PagerDuty's event deduplication uses the dedup_key field โ€” verify your integration is sending consistent dedup keys.
Incident auto-resolved unexpectedlyCheck your integration resolve settings. Many monitoring tools auto-resolve PagerDuty incidents when the alert condition clears. This is usually correct behavior โ€” confirm in your monitoring tool's PagerDuty integration settings.
PagerDuty web app not loading / 504 errorsApp-layer issues are usually shorter than alerting outages. Check status.pagerduty.com for the "Web App" component specifically. Alerting typically continues to work during UI-only incidents.
On-call schedule not routing correctlySchedule overrides, rotation gaps, or timezone issues are almost always configuration errors โ€” not PagerDuty outages. Review your schedule in the UI and check for gaps in rotation. PagerDuty's schedule viewer shows who is actually on call right now.

What to Do When PagerDuty Is Down During an Incident

A PagerDuty outage during a live production incident is a worst-case scenario. Every on-call team should have a fallback procedure documented before it is needed:

Immediate Response

  • Confirm PagerDuty outage at status.pagerduty.com
  • Call on-call engineer directly (have a printed roster)
  • Post in emergency Slack/Teams channel manually
  • Subscribe to PagerDuty status updates for resolution ETA
  • Check monitoring dashboards directly (Datadog, CloudWatch, etc.)

Proactive Preparation

  • Keep a printed or offline on-call roster with direct phone numbers
  • Configure a secondary alerting channel (OpsGenie, Opsgenie, direct SMS)
  • Set up independent PagerDuty status monitoring (Better Stack, API Status Check)
  • Run quarterly "PagerDuty is down" drills with your team
  • Enable multiple notification methods per engineer

PagerDuty Uptime History

PagerDuty processes hundreds of millions of alerts per year for over 25,000 companies. At this scale, incidents โ€” when they occur โ€” have wide blast radius:

1-3x/month
Reported incidents
Typically notification delays or single-channel failures, not full outages
15-45 min
Avg incident duration
Most incidents are resolved quickly; phone delivery issues can persist longer
99.9%+
Historical uptime
Per PagerDuty SLA on Business and Enterprise plans

The most impactful PagerDuty incidents historically involve notification delivery โ€” particularly phone call and SMS channels. PagerDuty uses third-party telephony providers, and failures there can affect a single notification channel while others remain operational. Always configure multiple notification methods per engineer. Also see: Datadog status guide and Sentry status guide for related observability tools.

๐Ÿ“ก
Recommended

Get alerted when PagerDuty goes down

Better Stack independently monitors PagerDuty's endpoints so your team gets notified when your notification system has an issue โ€” before an incident slips through silently.

Try Better Stack Free โ†’

Frequently Asked Questions

Where is the official PagerDuty status page?

PagerDuty's official status page is at status.pagerduty.com. It tracks real-time status for alerting and notification delivery, event ingestion, incident management, the web app, mobile app, and REST API. You can subscribe to email and webhook notifications for incident updates.

Why are my PagerDuty alerts not firing?

Start by checking status.pagerduty.com. If PagerDuty shows operational, the issue is almost always in the chain before PagerDuty: did your monitoring tool (Datadog, CloudWatch, Prometheus, etc.) actually fire the event? Check its event log. If the event was sent, verify your PagerDuty escalation policy routes to the correct service, and that your notification rules are configured correctly.

What should I do if PagerDuty is down during a real incident?

Activate your manual fallback: call the on-call engineer directly using a printed roster, post in your team emergency channel manually, and check your monitoring dashboards directly. Don't wait for PagerDuty to recover before responding to the underlying production issue.

Can I use a secondary tool as a backup for PagerDuty?

Yes โ€” many serious engineering teams run OpsGenie (now part of Atlassian) or Opsgenie as a secondary alerting path. Some teams configure their monitoring to send to both PagerDuty and a backup simultaneously. The overhead is worth it for critical production services.

How do I monitor PagerDuty status automatically?

Subscribe to email or webhook alerts at status.pagerduty.com, or use an independent monitoring service like Better Stack or API Status Check Alert Pro that watches PagerDuty endpoints separately from PagerDuty itself.

Alert Pro

14-day free trial

Stop checking โ€” get alerted instantly

Next time PagerDuty goes down, you'll know in under 60 seconds โ€” not when your users start complaining.

  • Email alerts for PagerDuty + 9 more APIs
  • $0 due today for trial
  • Cancel anytime โ€” $9/mo after trial

Never Miss a PagerDuty Outage Again

Monitor PagerDuty status independently so your team knows when your alerting system itself needs an alert.

Try Better Stack Free โ€” No Credit Card Required

Or use APIStatusCheck Alert Pro โ€” API monitoring from $9/mo

๐ŸŒ Can't Access PagerDuty?

If PagerDuty is working for others but not for you, it might be an ISP or regional issue. A VPN can help bypass network-level blocks and routing problems.

๐Ÿ”’

Troubleshoot with a VPN

Connect from a different region to test if the issue is local to your network. Also protects your connection on public Wi-Fi.

Try NordVPN โ€” 30-Day Money-Back Guarantee
๐Ÿ”‘

Secure Your PagerDuty Account

Service outages are a common time for phishing attacks. Use a password manager to keep unique, strong passwords for every account.

Try NordPass โ€” Free Password Manager
Quick ISP test: Try accessing PagerDuty on mobile data (Wi-Fi off). If it works, the issue is with your ISP or local network.

โณ While You Wait โ€” Try These Alternatives

๐Ÿ›  Tools We Use & Recommend

Tested across our own infrastructure monitoring 200+ APIs daily

Better StackBest for API Teams

Uptime Monitoring & Incident Management

Used by 100,000+ websites

Monitors your APIs every 30 seconds. Instant alerts via Slack, email, SMS, and phone calls when something goes down.

โ€œWe use Better Stack to monitor every API on this site. It caught 23 outages last month before users reported them.โ€

Free tier ยท Paid from $24/moStart Free Monitoring
1PasswordBest for Credential Security

Secrets Management & Developer Security

Trusted by 150,000+ businesses

Manage API keys, database passwords, and service tokens with CLI integration and automatic rotation.

โ€œAfter covering dozens of outages caused by leaked credentials, we recommend every team use a secrets manager.โ€

SEMrushBest for SEO

SEO & Site Performance Monitoring

Used by 10M+ marketers

Track your site health, uptime, search rankings, and competitor movements from one dashboard.

โ€œWe use SEMrush to track how our API status pages rank and catch site health issues early.โ€

From $129.95/moTry SEMrush Free
View full comparison & more tools โ†’Affiliate links โ€” we earn a commission at no extra cost to you