Loading status…
Loading status…
Sentry status · Developer Tools · checked (2m ago)
No — Sentry is not down. All Sentry systems are reported operational.
According to Sentry's official status page, Sentry was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Sentry's feed reported no outage in 99.96% of our checks.
Everything above is read from Sentry's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Sentry in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Sentry is an error tracking and performance monitoring platform: applications send it exceptions, traces and session data, and it groups and alerts on them. Its failure mode is quiet, because the thing that breaks is your visibility into everything else.
Sentry's status page separates ingestion — receiving events from your applications — from the dashboard, alerting and the API. Ingestion is the one to watch: if it is degraded, events are dropped or delayed, and you learn about outages in your own systems late. Sentry usually posts these as degraded rather than as an outage because ingest backs up rather than failing outright.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Sentry's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Sentry was down.
9 other services isuptime tracks were also reporting a problem as of the same check, 2m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Sentry's status endpoint.
Sentry has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Sentry posted itself — not every problem users hit.
resolved · Sep 18, 10:17 AM (5d ago)
resolved · Sep 18, 08:36 AM (5d ago)
resolved · Sep 10, 04:13 PM (13d ago)
resolved · Sep 10, 03:25 PM (13d ago)
resolved · Sep 1, 02:16 PM (22d ago)
resolved · Sep 1, 08:01 AM (22d ago)
resolved · Aug 31, 08:31 PM (22d ago)
resolved · Aug 27, 09:24 AM (27d ago)
resolved · Aug 26, 04:17 PM (28d ago)
resolved · Aug 25, 09:38 AM (29d ago)
resolved · Aug 18, 09:42 PM (35d ago)
resolved · Aug 13, 05:47 PM (40d ago)
resolved · Aug 12, 09:58 PM (41d ago)
resolved · Aug 12, 12:58 PM (42d ago)
resolved · Aug 12, 11:45 AM (42d ago)
resolved · Aug 7, 04:21 PM (47d ago)
resolved · Aug 6, 08:59 AM (48d ago)
resolved · Jul 27, 04:23 PM (58d ago)
resolved · Jul 21, 10:30 AM (64d ago)
resolved · Jul 20, 11:11 AM (65d ago)
Missing events are usually filtering rather than an outage: check your inbound filters, sample rate and rate limits, and confirm the DSN matches the project you are looking at. Ad blockers block Sentry's browser SDK, so client-side errors from real users can silently never arrive. Exhausting the monthly event quota drops events with no incident posted.
Sentry is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.