Connect, Learn, Innovate. Join us for PagerDuty on Tour. Register now
AI agents that learn, predict, and automate. See what's new
Connect, Learn, Innovate. Join us for PagerDuty on Tour. Register now
✕
  • PagerDuty logo
  • Pricing
  • Search
  • English
  • Deutsch
  • Français
  • 日本語
  • Contact Us
  • Log In
  • Start for Free
  • PagerDuty Operations Cloud

    The platform for mission-critical work in the modern enterprise.

    Incident Management

    End-to-end orchestration for rapid issue resolution.

    AI at PagerDuty

    Revolutionize operations at the speed of AI.

    Automation

    Accelerate critical work across the enterprise.

    AI Agents

    Redefine operations with AI Agents that ignite growth.

    Status Pages

    A single source of truth for system status.

    PagerDuty Advance

    Generative AI for critical operations work.

    Customer Service Ops

    Bridge support and engineering teams.

    AIOps

    Reduce alert noise and accelerate triage.

    Discover what PagerDuty Automation can do for you.

    Template and Prompt Library

    Discover what PagerDuty Automation can do for you.

    ➔
    Work how you want with PagerDuty. Explore our 750+ integrations

    PagerDuty Operations Cloud

    The platform for mission-critical work in the modern enterprise.

    Developer Platform

    Customize your PagerDuty experience.

    Professional Services

    Get more value from PagerDuty.

    Security

    View our trust and compliance practices.

    Enterprise Class

    Secure, reliable, extensible, and scalable.

    Integrations

    Work how you want with PagerDuty.

    Discover what PagerDuty Automation can do for you.

    Template and Prompt Library

    Discover what PagerDuty Automation can do for you.

    ➔
    See how PagerDuty works for you. Request a demo
    Incident Management TransformationOperations Center ModernizationAutomation StandardizationCustomer Experience OperationsDigital Operations ResiliencyScaled Service OwnershipRemote-Location Operations
    Security Incident ManagementLLMOpsDataOpsFinOpsComplianceOpsCrisisOpsSee All Use Cases
    Financial ServicesHealthcareNon ProfitGovernmentEducationRetailAI Infrastructure
    FOX Customer Story

    Operational Integrity at FOX

    Learn how strategic technology investments powered FOX's digital and operational transformation.

    ➔
    Work how you want with PagerDuty. Explore our 750+ integrations
    Pricing
    Thought LeadershipAwardsCareersInvestor RelationsLeadershipNewsroom

    About us

    We're empowering teams with the time and efficiency to build the future.

    Our Impact

    See how we are building resilience and accelerating change.

    FY25 Impact Report

    FY25 Impact Report

    Learn about our efforts around global employee engagement, sustainability, and more.

    ➔
    LibraryBlogDemosWebinarsEventsEbooks
    TUIZoomSpotifyDraftKingsAustralian BankVodafoneFox CorporationSee All Customers
    Template and Prompt LibraryPagerDuty UniversityCommunityOps GuidesKnowledge Base
    Keynotes, workshops, and networking in San Francisco on May 13

    PagerDuty on Tour

    Keynotes, workshops, and networking in San Francisco on May 13

    ➔
    Have a question? We're here to help. Contact Us

    Service Level Agreement (Archived)

    Table of Contents

    Product Terms

    • Terms of Service
    • Standard Service Level Agreement
    • Product-Specific Terms

    Partner Terms

    • One-Time Reseller Agreement

    Policies & Other Terms

    • Privacy Policy
    • Acceptable Use Policy
    • Community Policy
    • DMCA Takedown Notice
    • Subprocessors
    • Support Policy
    • CSE Usage Policy
    • Jeli Legacy Support Policy
    • Process Automation
    • Data Processing Addendum
    • Information Security Practices
    • Modern Slavery Act
    • Safe Harbor
    • Cigna Machine Readable Files
    • Event Terms
    • Trial Terms

    Security

    • Overview
    • Security Disclosure
    • Safe and Secure Generative AI
    • In Scope Services

    Privacy

    • Privacy FAQs
    • Privacy Shield and Schrems II
    • PagerDuty's GDPR Approach
    • Region-Specific Data Privacy Laws
    1. Definitions.

      "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

      Telephone

      API call to the service provider

      Push notification

      Report of push attempt from service provider

      SMS

      Report SMS sent by service provider

      Email

      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 /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.

    Platform

    Incident Management AIOps Automation Business Operations Developer Platform Enterprise-Class Platform Digital Operations Management Generative AI What's New

    Solutions

    Incident Management Transformation Operations Center Modernization Automation Standardization Customer Experience Operations Digital Operations Resiliency Scaled Service Ownership Remote-Location Operations

    Resources

    Resources Library Community Forum PagerDuty On Tour Customer Stories Integration Guides Automation Library Blog Watch Demo Request a Demo Use Cases Events

    Company

    About PagerDuty Thought Leadership Newsroom Events PagerDuty.org Investor Relations Leadership Suppliers Careers Awards

    Support

    System Status Help & Support Partner with PagerDuty Contact Us Legal Services FAQs Accessibility Ops Guides PagerDuty University Knowledge Base

    Facebook X Instagram LinkedIn

    © 2026 PagerDuty, Inc. All rights reserved.

    Privacy policy Website Terms of Use California Privacy Notice Modern Slavery Act CCPA Cookie Settings