Turn any signal into insight and action. See how PagerDuty Digital Operations Management Platform integrates machine data and human intelligence to improve visibility and agility across organizations.
Check out the latest features we've been working on — from event intelligence, machine learning, response automation, on-call, analytics, integrations, and more.
Digital Operations Management arms organizations with the insights needed to turn data into opportunity across every operational use case, from DevOps, ITOps, Security, Support, and beyond.
Over 200 Integrations
Discover DevOps best practices with our library of webinars, whitepapers, reports, and much more.
Learn best practices and get support help with resources from our award-winning support team.
See how PagerDuty works with our live product demo — twice a week, every week.
Join live and on-demand webinars for product deep dives, industry trends, configuration training, and use case-specific best practices.
Interactive, simple-to-use API and technical documentation enables users to easily try updates and extend PagerDuty.
Engage with users and PagerDuty experts from our global community of 200k+ users. Become a member, connect, and share insights for success.
Get all your PagerDuty-related questions answered by exploring our in-depth support documentation and community forums.
Modern Security Monitoring: Which Tools Should Be in Your Stack? The approach you take when it comes to security monitoring needs to be completely different when you manage cloud-native or containerized applications, ...
PagerDuty helps organizations transform their digital operations. Learn more about PagerDuty's mission and what we do.
Meet our experienced and passionate executive team.
We are risk-taking innovators dedicated to delivering amazing products and delighting customers. Join us and do the best work of your career.
With the PagerDuty Foundation, we are committed to doing our part in giving back to the community.
“Availability Outage” means that the Service is not available to Customer for thirty (30) or more consecutive minutes, measured by PagerDuty’s server logs.
“Service” means PagerDuty’s hosted Incident tracking and alerting solution.
“Hours of Operation” shall be twenty-four (24) hours per day, three hundred sixty-five (365) days per year, excluding any time for Maintenance Outages.
“Incident” means an event that triggers the Service to alert a Responder using the Contact Information. Customer must configure the Service and supply the Contact Information in accordance with the Documentation to recognize and respond to Incidents.
“Contact Information” means the names, email addresses, and telephone numbers of the Responders.
“Responders” mean Customer IT personnel that the Customer wants the Service to alert in the event of an Incident, along with any ancillary information such as alert priorities.
“First Responder” means the Responder assigned to receive the initial alert for a new Incident.
“First Responder Alert” means a High Urgency Alert notification to a First Responder
“Successful Alert” means a First Responder Alert notification that was sent by a Delivery Service that has reported successful delivery through available means such as delivery receipt callbacks or polled status endpoints as defined in Delivery Period below.
“Delivery Service” means a third party service provider indicated in the Contact Information used to send an alert to a Responder such as a telephone service (e.g., Verizon, AT&T), push notification provider (e.g., Google, Apple), SMS provider, or email provider.
“Successful Attempt” means the Service has made the attempt to send the First Responder Alert using the designated Delivery Services, but not actual receipt or acknowledgement of delivery, which depends on Customer behavior that is outside of PagerDuty’s control.
“Delivery Period” means the time it takes the Service to deliver a First Responder Alert in accordance with the Service configuration and Contact Information limited to an address or device registered and located in the United States of America or Canada as shown by PagerDuty’s logs. For clarity, the Delivery Period is measured from the time that PagerDuty receives the trigger event notification from Customer to the time the logs show that the Successful Alert or Successful Attempt was delivered, less the delay time (if any) specified in the Service configuration. The logs used to measure the Delivery Period depend on the type of Delivery Service:
Type of Delivery Service
Log used to measure Delivery Period
API call to the service provider
Report of push attempt from service provider
Report SMS sent by service provider
Report email sent by email provider
“Delivery Failure” means (A) an Availability Outage or (B)a Delivery Period that exceeds five (5) minutes from receipt of the triggering event notification from Customer due to or caused by reasons within PagerDuty’s control, excluding specifically (but not exclusively) failures caused by: (i) Customer’s own telecommunications, Internet service providers, or Email domain server availability; (ii) a Force Majeure Event; (iii) any systemic Internet failures; (iv) a properly noticed Maintenance Outage; (v) a Delivery Failure which occurs during a time period when Customer’s alert volume for any 15 minute period during which at least one (1) Incident occurs exceeds 1000% over the median of 15 minute periods during which that Customer triggered Incidents in the previous six (6) months; (vi) any failure of Customer Responsibilities or (vii) if the Deliver Service is push notification, any failure in the service provider of a push notification channel.
“High Urgency Alert” means an alert that Customer has designated using the Service as having high urgency.
“Customer Responsibilities” means Customer’s obligations to (i) configure and use the Service correctly in accordance with the Documentation; (ii) follow proper procedure in communicating the Incident to PagerDuty; (iii) maintain and update all Contact Information.
“Documentation” means any documentation for the Service that Company provides to Customer, or that it posts on its website at https://www.pagerduty.com and https://www.pagerduty.com/support/.
“Force Majeure Event” means (i) compliance with any act, order, demand or request of any government or governmental authority, agency or instrumentality; (ii) labor disputes, difficulties or work stoppages or slowdowns of any kind; (iii) hurricane, earthquake, flood and other natural disasters or fires; (iv) war, rebellion, act of terrorism, or civil disorder; (v) act or omission of any telecommunication or services provider; (vi) any other cause beyond PagerDuty’s reasonable control.
“Maintenance Outage” means a planned or unplanned maintenance period, including, without limitation, any maintenance downtime or maintenance outage, not to exceed an aggregate of ten (10) hours in any calendar month.
2. Delivery Failure Credits. For each properly documented Delivery Failure, PagerDuty will credit to Customer ten percent (10%) of the fees paid during the month in which the Delivery Failure occurred against future fees, up to a maximum of thirty percent (30%) of total fees for that month. Credits are not cumulative, that is, there shall only be a single credit given for all Delivery Failures with a single cause. Customer must report the Delivery Failure at the time it occurs, and must claim any credits by presenting documented evidence of the Remedy Amount within fifteen (15) days of occurrence of the relevant Delivery Failure. Customer will permit PagerDuty or an independent third party to audit its records to verify the Remedy Amount if requested. THIS SERVICE LEVEL AGREEMENT SETS FORTH CUSTOMER’S SOLE REMEDYFOR ANY FAILURE OF SERVICE AVAILABILITY OR FAILURE TO CONTACT THE DESIGNATED PERSONNEL.
3. Maintenance Outages. PagerDuty will provide Customer with notification via e-mail for each planned Maintenance Outage outside of the normal maintenance hours at least one (1) business day in advance. Customer acknowledges that Service Outages and emergency circumstances may require Maintenance Outages under conditions where such notice is not practicable.