SaaS Ranking
Menu

PagerDuty: what they publish

pagerduty.com · Incident management · checked 2026-10-18

39/100EBand E

Rank 13 of 34 in Incident management, where the median is 30.

Public transparency score, not a product or security rating. Latest check: 2026-10-18. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

1 day since the newest dated result, 1 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

PagerDuty

pagerduty.com · Incident management

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 39of 100 Rank 13 of 34

Published commitments5 of 9 found

Measured behaviour0 of 3 found

Checked 2026-10-18. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that PagerDuty has no such document.

Where PagerDuty sits in Incident management

  1. A0 0%
  2. B1 3%
  3. C4 12%
  4. D6 18%
  5. E12 35%
  6. F11 32%
34 vendors with a score. Bands have fixed thresholds, see how the score works.

The band of PagerDuty is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What PagerDuty states

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-18.

Show the 8 addresses we checked
  1. https://pagerduty.com/legal/dpa – reached, no match (HTTP 404)
  2. https://pagerduty.com/dpa – reached, no match (HTTP 404)
  3. https://pagerduty.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://pagerduty.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://pagerduty.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://pagerduty.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://pagerduty.com/trust/dpa – reached, no match (HTTP 404)
  8. https://pagerduty.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Data processing agreement in Incident management: 6 of 34 companies

✗

Data location: where they say data is hosted

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://www.pagerduty.com/security/ · checked 2026-10-18

Show the 7 addresses we checked
  1. https://pagerduty.com/security – found, but behind a sign-in
  2. https://pagerduty.com/trust – reached, no match (HTTP 404)
  3. https://pagerduty.com/legal/privacy – reached, no match (HTTP 404)
  4. https://pagerduty.com/privacy – found, but behind a sign-in
  5. https://pagerduty.com/privacy-policy – found, but behind a sign-in
  6. https://pagerduty.com/compliance – reached, no match (HTTP 404)
  7. https://pagerduty.com/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Data location stated in Incident management: 13 of 34 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-18.

Show the 3 addresses we checked
  1. https://status.pagerduty.com/ – reached, no match (HTTP 200)
  2. https://pagerduty.com/status – reached, no match (HTTP 404)
  3. https://pagerduty.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Status page with history in Incident management: 9 of 32 companies

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-10-18.

Show the 2 addresses we checked
  1. http://pagerduty.com/ – redirects to https://pagerduty.com/
  2. https://pagerduty.com/ – no HSTS header

Is this wrong? Send us the URL

Across the market: HTTPS enforced with HSTS in Incident management: 22 of 33 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-10-18.

Show the 1 address we checked
  1. https://pagerduty.com/ – third-party requests before any interaction: bat.bing.com, bat.bing.net, cdn.cookielaw.org, connect.facebook.net, dev.visualwebsiteoptimizer.com, geolocation.onetrust.com, googleads.g.doubleclick.net, invalid, ob.thisgreencolumn.com, obs.thisgreencolumn.com, sessions.bugsnag.com, snap.licdn.com, www.clarity.ms, www.googleadservices.com, www.googletagmanager.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Incident management: 3 of 32 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-18.

Show the 6 addresses we checked
  1. https://pagerduty.com/legal/sla – reached, no match (HTTP 404)
  2. https://pagerduty.com/sla – reached, no match (HTTP 404)
  3. https://pagerduty.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://pagerduty.com/trust/sla – reached, no match (HTTP 404)
  5. https://pagerduty.com/uptime – reached, no match (HTTP 404)
  6. https://pagerduty.com/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Incident management: 2 of 34 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-18.

Show the 1 address we checked
  1. https://pagerduty.com/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Incident management: 4 of 33 companies

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 5
✓

Subprocessors: the published list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://www.pagerduty.com/subprocessors/ · checked 2026-10-18

Across the market: Subprocessor list in Incident management: 8 of 34 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://www.pagerduty.com/pricing/ · checked 2026-10-18

Across the market: Public pricing in Incident management: 27 of 34 companies

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://www.pagerduty.com/subprocessors/ · checked 2026-10-18

Across the market: Notice before subprocessors change in Incident management: 8 of 34 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page FedRAMP (not counted: the sentence does not carry it), ISO/IEC 27001, PCI DSS (not counted: the sentence does not carry it), SOC 2, SOC 2 Type II. The sentence we kept does not carry this finding on its own, so it counts in no list and no figure.
    Show the 5 exact wordings

    FedRAMP® Low Authorized at the Low Baseline PagerDuty has achieved FedRAMP® Authorization at the Low baseli

    Read at https://www.pagerduty.com/security/

    Request a copy of PagerDuty's SOC 2 Type 2 Reports ISO 27001 PagerDuty has achieved ISO 27001 certification.

    Read at https://www.pagerduty.com/security/

    ta centers comply within leading security practices and frameworks, including SOC 2, ISO 27001, and PCI DSS.

    Read at https://www.pagerduty.com/security/

    The SOC 2 report provides assurance that we have designed effective security controls as defined by the SOC 2

    Read at https://www.pagerduty.com/security/

    Read more about FedRAMP® Authorized Status SOC 2 Certification PagerDuty has successfully completed SOC 2 Type II examinations for our various Servi

    Read at https://www.pagerduty.com/security/

Source: https://www.pagerduty.com/security/ · checked 2026-10-18

Across the market: Certifications named in Incident management: 17 of 34 companies

✓

Named privacy contact (DPO or privacy address)

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://www.pagerduty.com/privacy-policy/ · checked 2026-10-18

Across the market: Named privacy contact in Incident management: 9 of 34 companies

History

100 0 2026-10-11: 39 of 1002026-10-18: 39 of 100 2026-10-11 2026-10-18
Score over the last 2 runs we measured PagerDuty in: 39 (2026-10-11), 39 (2026-10-18).

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

PagerDuty

5 found · 7 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-18.

Investigate 7 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  3. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  4. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  5. HTTPS enforced with HSTS

    How is HTTPS enforced on the product and sign-in domains we will use? Please distinguish those domains from the public website.

    Inspect this check
  6. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  7. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.