SaaS Ranking
Menu

OneUptime

oneuptime.com · Monitoring and observability · checked 2026-09-13

52/100DBand D

Rank 11 of 47 in Monitoring and observability, where the median is 30.

We measured 12 of 12 criteria for OneUptime on 2026-09-13. We found 6 with a source and did not find 6 at the addresses we checked. That is a transparency score of 52 out of 100, band D.

Overview

0 days since the newest finding, 0 since the oldest. 12 of 12 criteria measured in the last 30 days.

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

OneUptime

oneuptime.com · Monitoring and observability

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
D 52of 100 Rank 11 of 47

Published commitments6 of 9 found

Measured behaviour0 of 3 found

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

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

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 OneUptime has no such document.

Where OneUptime sits in Monitoring and observability

  1. A0 0%
  2. B3 6%
  3. C7 15%
  4. D3 6%
  5. E17 36%
  6. F17 36%
47 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of OneUptime 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 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 location stated

weight 3 of 3

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

Seen at https://oneuptime.com/trust · checked 2026-09-13

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

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

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

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

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

Checked 1 address on 2026-09-13.

Show the 1 address we checked
  1. https://oneuptime.com/ – third-party requests before any interaction: a.quora.com, ad.doubleclick.net, alb.reddit.com, analytics.twitter.com, aplo-evnt.com, app.posthog.com, assets.apollo.io, bat.bing.com, connect.facebook.net, eu.posthog.com, fonts.googleapis.com, fonts.gstatic.com, pixel-config.reddit.com, q.quora.com, region1.analytics.google.com, s3-us-west-2.amazonaws.com, static.ads-twitter.com, stats.g.doubleclick.net, t.co, us-assets.i.posthog.com, www.google.com, www.google.de, www.googletagmanager.com, www.redditstatic.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-13.

Show the 8 addresses we checked
  1. https://oneuptime.com/legal/subprocessors – reached, no match (HTTP 200)
  2. https://oneuptime.com/subprocessors – reached, no match (HTTP 200)
  3. https://oneuptime.com/sub-processors – reached, no match (HTTP 200)
  4. https://oneuptime.com/legal/dpa – reached, no match (HTTP 200)
  5. https://oneuptime.com/dpa – reached, no match (HTTP 200)
  6. https://oneuptime.com/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://oneuptime.com/trust/subprocessors – reached, no match (HTTP 200)
  8. https://oneuptime.com/legal/sub-processors – reached, no match (HTTP 200)

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

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

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-13.

Show the 7 addresses we checked
  1. https://oneuptime.com/legal/privacy – reached, no match (HTTP 200)
  2. https://oneuptime.com/privacy – reached, no match (HTTP 200)
  3. https://oneuptime.com/privacy-policy – reached, no match (HTTP 200)
  4. https://oneuptime.com/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://oneuptime.com/legal/privacy-notice – reached, no match (HTTP 200)
  6. https://oneuptime.com/trust/privacy – reached, no match (HTTP 200)
  7. https://oneuptime.com/datenschutz – reached, no match (HTTP 200)

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 6
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://oneuptime.com/legal/dpa · checked 2026-09-13

✓

Subprocessor list

weight 3 of 3

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

Source: https://oneuptime.com/legal/subprocessors · checked 2026-09-13

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://oneuptime.com/ · checked 2026-09-13

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://oneuptime.com/ · checked 2026-09-13

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

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

    ISO 27001 27017 27018 Certified SOC 2 Report on request HIPAA Deployment available Single sign-on Okta, Azure AD, Google Workspace.

    Read at https://oneuptime.com/

    ISO 27001 27017 27018 Certified SOC 2 Report on request HIPAA Deployment available Single sign-on Okta, Azure

    Read at https://oneuptime.com/

    LB Laura Bennett Platform Lead at CryptoVault Exchange PCI compliance maintained PCI-DSS requires us to control our monitoring data.

    Read at https://oneuptime.com/

    ISO 27001 27017 27018 Certified SOC 2 Report on request HIPAA Deployment available Single sign-on Okta, Azure AD, Google Workspace.

    Read at https://oneuptime.com/

Source: https://oneuptime.com/ · checked 2026-09-13

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

  • Highest uptime figure on that page 99.98 %.
    Show the exact wording

    Uptime 30d 99.98% Ongoing Sev 2 Incident #482 - Checkout API degraded 02:47:12 02:47:58 Alert routed to policy Paymen

    Read at https://oneuptime.com/

Source: https://oneuptime.com/ · checked 2026-09-13

History

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

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.