Developer platforms
Is Sentry down?
Live Sentry status, measured independently. We probe 5 Sentry endpoints from monitoring regions on every continent and record every outage we detect.
Sentry is up
Our probes are reaching Sentry normally from every region we check from.
Checked every minute from 6 regions on every continent.
- 24h uptimeUptime, 24 hours
- 7d uptimeUptime, 7 days
- 30d uptimeUptime, 30 days
- Website99.99% uptime, 30 days6 regions, 267 to 1172 msCheckingp50688 msMedian responsep95985 msSlowest 5% of checks1000 ms500024 h ago12 h agonow
- API99.38% uptime, 30 days6 regions, 134 to 616 msCheckingp50314 msMedian responsep95550 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Event ingestion100% uptime, 30 days6 regions, 113 to 691 msCheckingp50304 msMedian responsep95532 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Documentation100% uptime, 30 days6 regions, 98 to 388 msCheckingp50245 msMedian responsep95459 msSlowest 5% of checks500 ms250024 h ago12 h agonow
- Official status feed99.72% uptime, 30 days5 regions, 166 to 559 msCheckingp50376 msMedian responsep95581 msSlowest 5% of checks500 ms250024 h ago12 h agonow
Daily strip:99.5% or better99–99.5%95–99%below 95%no data yet
Get notified when Sentry goes down
Follow these 5 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment Sentry goes down. They don't count against your monitor quota. Free plan, no card required.
About Sentry outages
Sentry receives exceptions and performance data from applications and turns them into alerts and issues. A Sentry incident means your error reporting goes dark, which is a particularly bad time for your own bugs to appear. Ingestion and the web UI are separate systems and fail independently.
What we check
Every row is a real monitor in Uptimy, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website sentry.io is unreachable. | httpsentry.io/welcome/ | HTTP 200 | 1 min |
API The Sentry API root is not answering. The UI and integrations depend on it. | httpsentry.io/api/0/ | HTTP 200 | 2 min |
Event ingestion The event ingestion endpoint is not answering. SDKs cannot deliver errors and traces. | httpo1.ingest.sentry.io/api/1/envelope/ | Any HTTP response | 2 min |
Documentation Sentry's documentation is unreachable. | httpdocs.sentry.io | HTTP 200 | 5 min |
Official status feed Sentry's status page is unreachable. | httpstatus.sentry.io/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Sentry's official status page.
Embed a live Sentry badge
A status badge for your README, wiki, or runbook that updates every minute from these probes and links back to this page. Pick the whole service or a single check.
Preview
Markdown
[](https://www.upti.my/status/sentry?utm_source=badge)HTML
<a href="https://www.upti.my/status/sentry?utm_source=badge"><img src="https://www.upti.my/status/sentry/badge.svg" alt="Sentry status"></a>Recent Sentry outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
Sentry is up. Is your Sentry integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on Sentry and fail quietly. Here is what teams that rely on Sentry monitor on their side.
Do not rely on one observability vendor
If error tracking and alerting both live in the same tool, an incident there blinds you. External uptime checks and heartbeats give you an independent signal.
Independent uptime monitoringSentry status: frequently asked questions
Check the official page for ingestion incidents. Silence from an error tracker is ambiguous, which is exactly why independent uptime checks and heartbeats matter alongside it.
Look at the per-region results above. If our probes fail from every region, Sentry has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, Sentry may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about Sentry" above: your Uptimy workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on Sentry: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other developer platforms
Uptimy is not affiliated with Sentry. Sentry and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.