CheckUpstream measured Sentry at 99.598% availability across 2737 independent checks (global · api). 49 incidents were recorded in the past 12 months; the most recent resolved earlier today after 2 hours. Status signals are polled from Sentry's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
99.598%
global · api · n=2737 · p95 819ms (30d)
Share of our own checks against Sentry endpoints that returned Sentry's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 12 incidents · 30 of 30 days with none posted · 1m of declared impact
Fewer incidents in the last 30 days than 7% of 232 tracked services.
Share of each window with no impact declared by Sentry
7d
100.000%
30d
99.997%
90d
99.999%
180d
99.999%
1y
100.000%
Downtime like this can be refundable
If you're a paying Sentry customer, outages in these windows may count against Sentry's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Sentry entitlement →Does Sentry actually matter to you?
A Sentry outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 12 incidents Sentry published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Sentry takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
1signal across 1 source
HN 1
Live Sentry status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/sentry)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Sentry is currently Operational. CheckUpstream tracks Sentry in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Sentry's last resolved incident started earlier today and lasted 2h 23m (degraded performance).
Looking for the live "is Sentry down" view? See the Sentry Live status page.
Aug 25, 09:38 UTC · resolved in 3h 2m · Resolved
Aug 12, 11:45 UTC · resolved in 4m · Resolved
Aug 7, 16:21 UTC · resolved in 49m · Resolved
Aug 6, 08:59 UTC · resolved in 2h 31m · Resolved
Jul 27, 16:23 UTC · resolved in 2h 6m · Resolved
Jul 21, 10:30 UTC · resolved in 3h 49m · Resolved
Jul 20, 11:11 UTC · resolved in 5h 49m · Resolved
Jul 16, 21:06 UTC · resolved in 9h 54m · Resolved
Jul 14, 14:44 UTC · resolved in 4h 55m · Resolved
Jul 13, 11:51 UTC · resolved in 2h 38m · Resolved
Jul 13, 00:58 UTC · resolved in 2h 2m · Resolved
Jul 10, 22:43 UTC · resolved in 4h 56m · Resolved
Sentry's 30-day measured availability is 99.598%, from CheckUpstream's own probes against Sentry endpoints. It is the share of checks that returned the expected response, not a figure taken from Sentry's status page.
Sign up to CheckUpstream and add Sentry to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Sentry's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.