PagerDuty status: is it down right now?
Our own check of pagerduty.com from Europe and the US, every 3 minutes, with recent history.
Checking now
Checking now
Waiting for the check results.
Checking PagerDuty…
Checking pagerduty.com from our locations
Follow PagerDuty's public website. Free 10-minute checks, no card. This does not check every feature.
Run a website? Check my website
This checks the response from pagerduty.com. It does not test playback, login or every PagerDuty feature.
Watch your site free
This page is for their outage. Your own site can fail the same way. Free plan: 3 monitors, SSL alerts, no card.
Watch your site freeabout this service
About PagerDuty
PagerDuty is the industry-standard on-call and incident-response platform. Alerts from Datadog, New Relic, Prometheus, CloudWatch and hundreds of other tools route through PagerDuty to page on-call engineers via push, SMS and phone. A PagerDuty outage during a real production incident is the nightmare scenario: your systems are down and your paging infrastructure cannot reach the on-call. The product splits into Events API (where alerts land), Notifications (the actual paging delivery), and the web app (where responders acknowledge and coordinate). Any of these can degrade independently.
The official PagerDuty status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster.
outage patterns
How PagerDuty outages affect production workloads
Developer-platform outages have outsized impact because they cascade. When PagerDuty is degraded, every customer's build pipeline, deploy hook, or webhook delivery can stall, and the failure mode often looks like a customer problem before engineers realize the dependency is the cause. CI runs hang, status checks never report, and queued jobs pile up silently.
The live check above provides independent public-endpoint evidence from EU and US, including status and response timing. That helps separate a broad reachability problem from a local client issue, but it does not execute your private API call, build, webhook, or deploy. Test the exact dependency path before attributing the incident to PagerDuty.
Common signs PagerDuty is having issues
- API rate limits returning earlier than the documented thresholds
- Webhook deliveries showing 5xx errors or unusual latency tail
- Deploy or build hooks accepted by PagerDuty but never firing downstream
- OAuth or token endpoints failing intermittently for the same client credentials
What to do when PagerDuty is degraded
When PagerDuty is having trouble, the fastest mitigation is usually feature-flagging the dependency off if your application can degrade gracefully. Check the multi-region results on this page first; if both regions report healthy but your application still sees failures, the issue is likely your network path or DNS, not PagerDuty itself.
monitor 24/7
Monitor PagerDuty automatically.
Get independent alerts when the public PagerDuty endpoint fails a confirmed check. Start free with 10-minute checks, or use Business or Agency for 60-second uptime checks.
10-minute free checks
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Email + push on Free
Paid plans unlock additional team and incident channels.
free forever · paid trials last 10 days
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor PagerDuty on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track PagerDuty uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is PagerDuty down right now?
See the latest check of pagerduty.com and its timestamp at the top of this page. If PagerDuty is down, you can also check the official status page for extra context.
How do I check if PagerDuty is having issues?
This page checks the public PagerDuty endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when PagerDuty goes down?
Set up a free monitor for pagerduty.com on Visual Sentinel for 10-minute checks with email and push alerts. Paid plans add checks as fast as 60 seconds and more notification channels.
Where can I find PagerDuty outage context?
The official PagerDuty status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster. Visual Sentinel checks the public PagerDuty endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
What happens to alerts during a PagerDuty Events API outage?
Most alerting integrations will retry on 5xx responses from the Events API for a limited window. Alerts generated during the outage are typically delivered once the API recovers, but latency can stretch into tens of minutes. Time-critical alerts may be effectively lost.
Can I fail over from PagerDuty during an outage?
Not in real time without prior setup. Teams that treat paging as critical maintain a secondary paging path (e.g. Opsgenie or direct Twilio) and fan out alerts to both providers from their monitoring tools. This only works if configured before the outage.