Sentry Status: How to Check If Sentry Is Down Right Now (2026)
Updated June 2026 · 7 min read · API Status Check
Quick Answer
Check Sentry status at status.sentry.io (official) or apistatuscheck.com/is-sentry-down for independent real-time monitoring.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
The Official Sentry Status Page
Sentry maintains an official status page at status.sentry.io. This page shows real-time status for all Sentry services:
What Each Sentry Status Means
Monitor your error tracker's uptime
Better Stack monitors Sentry's endpoints independently — so you know when your error monitoring has a blind spot. Free tier included.
Try Better Stack Free →Sentry Cloud vs. Self-Hosted: Different Failure Modes
Sentry offers both a cloud-hosted service (sentry.io) and a self-hosted open-source version. The failure modes are completely different:
Sentry Cloud (sentry.io)
What it is: Sentry's managed cloud service. Used by most teams. You pay for it and Sentry manages all infrastructure.
Signs of issues: Events not appearing in UI, notifications not firing, slow dashboard, 5xx errors on ingest endpoint.
Workaround: Check status.sentry.io. If ingestion is down, your SDK buffers events. No action needed — just wait.
Self-Hosted Sentry
What it is: Open-source Sentry running on your own infrastructure. You own all components: web, worker, Kafka, Redis, Postgres, ClickHouse.
Signs of issues: Events stuck in Kafka, worker queues backed up, Redis memory full, Postgres connection limits hit.
Workaround: Check worker process health, Kafka consumer lag, Redis memory usage. Self-hosted issues are typically infrastructure, not Sentry code.
5 Ways to Check Sentry Status Right Now
Official Sentry Status Page
Visit status.sentry.io for real-time component status. Subscribe to email notifications for incident updates and detailed post-mortems.
status.sentry.io →API Status Check (Independent Monitor)
APIStatusCheck independently monitors Sentry's endpoints and shows real uptime data — unbiased monitoring that Sentry doesn't control.
Check live Sentry status →X/Twitter Search
Search 'Sentry down' or 'sentry.io not working' on X. Developers report issues in real time — often faster than the official status update.
Search X for 'sentry down' →Sentry GitHub Issues
For self-hosted Sentry, check the Sentry GitHub repository for issues related to your version. Cloud outages are also sometimes discussed in issues.
Sentry GitHub Issues →Test the Sentry Ingest Endpoint
Send a test event to your DSN to verify if the ingest endpoint is responding. If you get a 200 response, Sentry is accepting events.
curl -X POST https://sentry.io/api/[PROJECT_ID]/store/ -H "X-Sentry-Auth: Sentry sentry_key=[KEY]" -d '{"message":"test"}'Common Sentry Errors During Outages
These are the errors and symptoms you'll see when Sentry is experiencing issues:
"Failed to send event to Sentry"SDK cannot reach the Sentry ingest endpoint. Events are buffered. Check status.sentry.io first."429 Too Many Requests from Sentry ingest"You've hit your Sentry plan's rate limit — not an outage. Upgrade your plan or reduce event volume. Check Settings → Usage."500 / 503 from sentry.io/api/store/"Sentry backend error. Likely an ingestion incident. Events buffer in the SDK and retry. Check status.sentry.io."No new issues appearing in Sentry"Could be an ingestion delay during an incident, or your SDK isn't sending events. Verify SDK initialization and add a `beforeSend` test event."Sentry notifications not firing"Notification pipeline may be degraded. Events may still be ingesting but alerts are delayed. Check notification settings and status.sentry.io."Source maps not loading in Sentry UI"Could be a processing delay during high load, or an issue with your release/source map upload. Verify your source map upload in the release artifacts.Sentry Outage History: What the Data Shows
Sentry processes billions of error events per month. At that scale, even brief ingestion delays affect thousands of teams:
The most impactful Sentry incidents are notification delays — where errors are ingested but your team doesn't get paged. This makes external monitoring of Sentry itself especially important for production teams. Also see: Datadog status guide for another popular observability tool.
Know when Sentry has a blind spot
Better Stack monitors Sentry's endpoints independently so you get alerted when your error tracker itself is down. Don't let your monitoring have an unmonitored failure mode.
Try Better Stack Free →What to Do When Sentry Is Down
If Ingestion Is Down
- Confirm at status.sentry.io — don't restart services yet
- SDK buffers events automatically — leave it running
- Monitor application health via logs and metrics directly
- Have backup error logging (stdout + log aggregator) for critical paths
- Subscribe to incident updates at status.sentry.io
If Notifications Stop Firing
- Check Sentry UI directly for new issues — events may be arriving
- Verify notification settings haven't changed (common gotcha)
- Check your Slack/PagerDuty integrations are still connected
- Manually review error rates in your metrics dashboard
- Set up a backup alert via direct log-based alerting temporarily
Frequently Asked Questions
Where is the official Sentry status page?
Sentry's official status page is at status.sentry.io. It shows real-time status for error ingestion, processing, notifications, performance monitoring, and the Sentry web UI. You can subscribe to email notifications for incident updates and post-mortems.
If Sentry is down, will I lose error data?
Usually no. Sentry SDKs buffer events locally and retry delivery when the ingest endpoint is unreachable. Short outages (minutes to a few hours) typically result in delayed events appearing in your Sentry dashboard once the incident resolves. Extremely long outages or SDK-level issues could cause event loss.
Why is Sentry slow or not showing new errors?
Slow error appearance usually means event processing is backed up due to high load or a partial incident. The events are likely in Sentry's queue and will appear once processing catches up. Check status.sentry.io — if it shows degraded performance, wait 30-60 minutes before investigating further.
Does a Sentry outage affect self-hosted installations?
No — self-hosted Sentry is independent of sentry.io. If you run Sentry on your own infrastructure, sentry.io status pages are irrelevant. Self-hosted Sentry failures are infrastructure issues on your end (Kafka, Redis, Postgres, worker process health).
How do I monitor Sentry status automatically?
Subscribe to email alerts at status.sentry.io, follow @getsentry on X, or use a secondary monitoring tool like Better Stack or API Status Check Alert Pro to watch Sentry's ingest endpoint independently.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Sentry goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Sentry + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial