PagerDuty status
PagerDuty platform availability. Distinguish incident ingestion and notifications from a problem in the monitored service.
Live Domain Check
Is PagerDuty Down? Check pagerduty.com Status and Outages
Run a live reachability check for pagerduty.com. Compare the regional responses with the problem you see in PagerDuty.
Find PagerDuty help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked-
Verdict-
Response Time-
Final URL-
Regional checks
Is PagerDuty working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding PagerDuty connection and service problems
PagerDuty UI access, event ingestion and notification delivery are separate incident-response functions.
The checker above requests pagerduty.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual PagerDuty action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse developer service checks.
PagerDuty status information and official help
PagerDuty help and reporting
Use the event-ingestion, incident or notification-delivery context.
Open pagerduty.com
Open the website in your browser and compare it with the result above.
Where to report problems with PagerDuty
Open PagerDuty help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Service/integration, event/incident ID, delivery channel, timestamp and error without integration keys.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to PagerDuty.
What to check when PagerDuty is not working
These are troubleshooting comparisons, not claims that PagerDuty is currently experiencing a particular incident.
Start with the action that failed
Compare whether an event was received and whether an incident was created before resending it.
Narrow down the affected service
Inspect notification delivery and service status; use your team's established alternate escalation route if paging is affected.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if PagerDuty is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the pagerduty.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open PagerDuty status and check whether the named service and incident time fit your error.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If PagerDuty Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when PagerDuty seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open pagerduty.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader PagerDuty issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting PagerDuty support.
Frequently asked questions about PagerDuty problems
Is PagerDuty down, or is the problem limited to one feature?
Run the pagerduty.com check and compare its original timestamps and responses with your actual error. PagerDuty UI access, event ingestion and notification delivery are separate incident-response functions.
Where can I report a problem with PagerDuty?
Use the community buttons on this page to share whether the service works for you. For help from PagerDuty, use the official help/reporting resource linked above. Use the event-ingestion, incident or notification-delivery context.
What should I check first when PagerDuty is not working?
Compare whether an event was received and whether an incident was created before resending it. Inspect notification delivery and service status; use your team's established alternate escalation route if paging is affected.
What information helps PagerDuty support investigate?
Service/integration, event/incident ID, delivery channel, timestamp and error without integration keys.