Live check
Is Sentry down right now?
Observed from Sentry’s public feed by our independent monitor. Always confirm operational decisions on the official status page.
While you wait: the Sentry incident checklist
- Remember which way the dependency points. Sentry being down doesn't make your app down: SDKs send asynchronously and drop events when the backend is unreachable. The outage is in your visibility, not your service.
- Confirm health independently. 'No new errors in Sentry' is meaningless right now. Check metrics, logs and uptime checks — signals that don't share Sentry's fate — before treating quiet as good.
- Expect a gap, not a backlog. Client SDKs buffer only briefly, so events from the window are mostly gone rather than delayed. Note the window so nobody trusts the 'zero errors' hour in next week's review.
- Unblock your releases. If CI uploads sourcemaps or creates Sentry releases as a blocking step, make it best-effort for the duration. A hotfix should never wait on the error tracker.
- Brace alert rules for recovery. Volume-based alert rules can misread the recovery burst as an incident spike. Expect a few false alarms as ingestion resumes and triage accordingly.
What breaks when Sentry has issues
Sentry incidents create an observability blind spot: new crashes go unrecorded, issue-based alerting into Slack or PagerDuty falls silent, and release-health data (crash-free rates, adoption) gaps out. Production itself is safe — SDKs are designed to fail open without blocking your request path — but CI steps that create releases or upload sourcemaps can fail builds, and any workflow gated on Sentry data stalls. The risk isn't downtime; it's shipping and operating blind while assuming silence means health.
FAQ
Will Sentry being down slow down or crash my app?
It shouldn't: Sentry SDKs send events asynchronously with small internal queues and are designed to drop data rather than block your application when the backend is unreachable.
Are events from the outage window lost or just delayed?
Assume mostly lost: client SDKs buffer briefly and drop what they can't send. Treat the window as a data gap rather than expecting a backfill after recovery.
Should sourcemap upload failures block CI?
Not during an incident — and arguably never on hotfix pipelines. Make the Sentry release step best-effort so the error tracker can't block a fix from shipping.
How do I monitor my app while Sentry is down?
Fall back to signals that don't share Sentry's fate: infrastructure metrics, application logs, uptime checks, and synthetic probes from a different provider.
Does this affect self-hosted Sentry?
No — status.sentry.io covers Sentry's SaaS platform. Self-hosted Sentry instances fail on your infrastructure, not theirs, and won't appear on this page.
Put Sentry’s status in your toolbar
Is it you — or your vendor? You checked once. The extension watches Sentry and the rest of your stack continuously — badge, popup and Side Panel, free for 5 vendors, no account.
Add to Chrome — free, no accountNot an outage? Track API changes before they become incidents.
VendorStatus shows when a dependency is failing now. Breakwater watches official developer changelogs and migration deadlines locally in your browser, so your team can plan the change before the next deploy.
Also on your stack?
Not affiliated with Sentry. Status data comes from their public status page.