Sentry uptime
Sentry, checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.
Sentry is up.
Up for 31 d. Last checked 2026-11-20 18:54 UTC from Singapore: 200 in 248 ms.
Last 24 hours
Up for 31 d100% passed
287 checks, median 169 ms from Falkenstein, all passed
95% under 183 ms
Response time by region
Medians over this range, on one scale up to 500 ms.
Last 90 days
Up for 31 d99.92% passed
14,805 checks, median 170 ms from Falkenstein, 11 failed checks, 7 timeouts
95% under 211 ms
Response time by region
Medians over this range, on one scale up to 500 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
Failures older than 15 days show on the bars only.
In the last 30 days Sentry passed 8,862 of 8,863 checks, 99.98%.
2 outages since 30 Sep 2026; the longest lasted 10 min, on 20 Oct 2026.
Availability
The share of checks that passed, and the outages that began, in each window up to now.
| Last | Passed | Checks | Outages |
|---|---|---|---|
| 24 hours | 100% | 288 of 288 | 0 |
| 7 days | 100% | 2,015 of 2,015 | 0 |
| 30 days | 99.98% | 8,862 of 8,863 | 0 |
| 90 days | Not enough history yet: checks began on 30 Sep 2026 | ||
A year of checks is kept; the year's figure appears here once there is a year of them.
Response time by location
Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.
| From | Median | 95th percentile | Mean | Checks |
|---|---|---|---|---|
| Falkenstein, Germany | 166 ms | 183 ms | 178 ms | 420 |
| Helsinki, Finland | 167 ms | 551 ms | 205 ms | 42 |
| Ashburn, USA | 100 ms | 208 ms | 135 ms | 503 |
| Copenhagen, Denmark | 184 ms | 213 ms | 196 ms | 43 |
| Singapore | 280 ms | 888 ms | 325 ms | 505 |
| Sydney, Australia | 417 ms | 503 ms | 424 ms | 502 |
Outages
Every outage in the last year, newest first. Times are UTC; what failed and where are kept for 14 days.
| Began (UTC) | Ended (UTC) | Length | What failed | Seen from |
|---|---|---|---|---|
| 10 min | Not kept | Not kept | ||
| 10 min | Not kept | Not kept |
What is checked
Error tracking and performance monitoring: SDKs in apps send errors and traces there.
StatOSS sends GET https://sentry.io/api/0/ and counts the check as passed on status 200 within 10 seconds. The root of the web API on sentry.io, which answers 200 with its version and no token.
SDKs send events to separate ingest addresses, which are not checked; events can be taken in while the web app is down, and the other way round.
Sentry reports its own incidents at status.sentry.io. The figures here are measured from outside and can differ from it in both directions.
How it is measured
- One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
- A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 200.
- A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
- Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
- Availability is the share of checks that passed. There are no maintenance windows: every check counts.
It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.