SaaS Ranking
Menu

PagerDuty

pagerduty.com · Incident management · checked 2026-09-04

39/100EBand E

Rank 10 of 23 in Incident management, where the median is 30.

We measured 12 of 12 criteria for PagerDuty on 2026-09-04. We found 5 with a source and did not find 7 at the addresses we checked. That is a transparency score of 39 out of 100, band E.

Overview

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 10 of 23

Published commitments5 of 9 found

Measured behaviour0 of 3 found

Checked 2026-09-04. 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.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

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.

What they state

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

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-04.

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

✗

Data location stated

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-09-04

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

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-04.

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

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-04.

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

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-04.

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, ob.thisgreencolumn.com, obs.thisgreencolumn.com, sessions.bugsnag.com, snap.licdn.com, www.clarity.ms, www.google.com, www.google.de, www.googleadservices.com, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-04.

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

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-04.

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

Evidence

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

Published, with a source 5
✓

Subprocessor 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-09-04

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.pagerduty.com/pricing/incident-management/ · checked 2026-09-04

✓

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-09-04

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page FedRAMP, ISO/IEC 27001, PCI DSS, SOC 2, SOC 2 Type II.
    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-09-04

✓

Named privacy contact

weight 1 of 3

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

Source: https://www.pagerduty.com/privacy-policy/ · checked 2026-09-04

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare