Report an Issue

Is PagerDuty Down? Current Status, Outage Reports & User Feedback

Operational Last checked: 3 minutes ago

User Reports (Last 12 Hours)

Quick Actions

Report an Issue
Official Website Official Status Page

Related Services

JFrog Operational Travis CI Operational Datadog Operational Bitbucket Operational New Relic Operational CircleCI Operational

Frequently Asked Questions

Login issues may be caused by credential problems, account status changes, or authentication service disruptions. Verify your email address and password are correct, check if your organization uses SSO (requiring login through a corporate portal), and try the password reset option if you continue experiencing difficulties.

Notification failures can result from device settings, contact method configuration, or delivery service issues. Verify your notification rules are correctly set up in your PagerDuty profile, check if your phone has notification permissions enabled for SMS or the PagerDuty app, and ensure your device isn't in Do Not Disturb mode.

Integration issues may be caused by configuration problems, connectivity failures, or API limitations. Verify your integration settings and credentials are correct, check if your services can connect to PagerDuty's API endpoints, and examine integration activity logs for specific error messages.

Incident creation failures can stem from integration misconfiguration, event filtering, or service mapping problems. Check if the integration between your monitoring tool and PagerDuty is correctly configured, verify event rules aren't inadvertently suppressing alerts, and ensure services are properly mapped to escalation policies.

Mobile app issues can result from authentication problems, synchronization failures, or app version compatibility. Try logging out and back into the mobile app, check if your device has a stable internet connection, and ensure you're using the latest version of the PagerDuty mobile app.

Escalation policy issues may be caused by schedule overrides, user availability settings, or configuration misunderstandings. Verify there are no active overrides affecting the escalation path, check if users are marked as unavailable during the incident time, and review the escalation policy details for any unexpected rules or timeouts.

Incident action failures can stem from permission limitations, UI loading issues, or session problems. Verify you have the necessary user role to modify incidents, try refreshing the page or switching between list and incident views, and check if you're viewing incidents from a restricted team or service.

Analytics issues may be caused by data processing delays, permission restrictions, or filtering problems. Allow up to 24 hours for recent incidents to appear in analytics, verify you have reporting permissions for the relevant services, and try adjusting time ranges or filters if specific data appears to be missing.

Incident History

Resolved Incidents

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 15:28 Resolved: 2025-07-05 15:35

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 14:12 Resolved: 2025-07-05 14:33

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 13:46 Resolved: 2025-07-05 13:59

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 12:56 Resolved: 2025-07-05 13:11

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 11:42 Resolved: 2025-07-05 11:53

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 11:14 Resolved: 2025-07-05 11:27

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 08:52 Resolved: 2025-07-05 11:27

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 08:24 Resolved: 2025-07-05 08:36

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 06:51 Resolved: 2025-07-05 08:36

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 05:51 Resolved: 2025-07-05 06:05

We have detected a potential outage for PagerDuty.
Started: 2025-07-05 05:16 Resolved: 2025-07-05 05:37

About PagerDuty

PagerDuty is an incident management platform that helps organizations detect, triage, and resolve operational disruptions through automated alerting, on-call scheduling, and incident response coordination. The service integrates with monitoring tools and application performance systems to identify problems, notify the appropriate responders through multiple channels, and provide collaborative tools for managing incidents from detection through resolution, enabling faster response to service disruptions across complex technology environments.

IT operations teams use PagerDuty to manage on-call rotations and escalation policies, ensuring critical alerts reach the right responders based on scheduling, expertise, and incident severity. DevOps engineers implement PagerDuty's integrations with monitoring tools to consolidate alerts from multiple systems, reducing alert fatigue while maintaining visibility into service health. Customer support organizations leverage PagerDuty to coordinate responses to customer-impacting issues across technical teams, tracking incident metrics and response times, while executive stakeholders utilize PagerDuty's analytics to measure operational performance, identify recurring problems, and drive continuous improvement in incident management processes.

Users may experience various types of issues when using PagerDuty, including occasional notification delivery delays across certain communication channels, temporary access limitations during scheduled maintenance periods, or brief synchronization lags when updating schedules and escalation policies. Mobile application alerts might sometimes require troubleshooting for specific device configurations or notification settings. Integration connections with monitoring tools could experience authentication failures requiring credential updates. Calendar synchronization between PagerDuty schedules and external calendar applications might occasionally show inconsistencies requiring manual refresh. During high-volume incident periods, users might notice increased latency when navigating the web interface, temporary limitations on complex report generation, or delayed processing for bulk administrative actions across multiple teams or services.

```