Sentry is the leading application monitoring and error tracking platform, used by over 100,000 organizations to detect, triage, and resolve software errors in real time. The platform captures crash reports, performance traces, session replay recordings, and release health data across web, mobile, and backend applications. Sentry supports over 100 programming languages and frameworks with native SDKs, providing stack traces, breadcrumbs, and contextual data that help developers identify root causes within minutes rather than hours.
Sentry outages typically involve event ingestion pipeline congestion during global error spikes — when a widespread infrastructure failure causes thousands of applications to generate error floods simultaneously. ClickHouse database performance issues affect event search and issue detail loading. Alert notification delivery delays stem from evaluation queue backlogs. The relay infrastructure that receives events at the edge can experience regional capacity issues during traffic surges. Self-hosted Sentry instances have independent availability from sentry.io.
When Sentry goes down, development teams lose visibility into application errors at the exact moment they may need it most. Crash reports stop arriving, performance monitoring data goes dark, and release health metrics become unavailable. Teams cannot triage new errors, assign issues, or track error resolution. For organizations that use Sentry as their primary error alerting system, an outage means bugs may reach users undetected until service resumes.
Use this page to check Sentry availability. Sentry outages may affect event ingestion, the web UI, or alerting independently. Check status.sentry.io for the official per-component status page. If you run self-hosted Sentry, your instance has independent availability from sentry.io cloud.
Sentry SDKs implement local buffering and retry logic, so events are queued on the client side during short outages. However, buffer sizes are limited, and extended outages may cause events to be dropped. High-volume applications generating thousands of errors per minute are more likely to exceed buffer limits during prolonged ingestion outages.
Alert delivery failures can result from Sentry platform outages, misconfigured alert rules, or notification channel issues. Check if events are appearing in the Sentry UI without triggering alerts — this suggests a rule configuration problem. If no events are appearing at all, the ingestion pipeline may be down. Check status.sentry.io for current incidents.
Sentry uses rate limiting and event sampling to handle error spikes. When a widespread infrastructure failure causes millions of errors simultaneously, Sentry may throttle ingestion to protect platform stability. Your project's rate limits and quotas determine how many events are accepted. Enable spike protection in project settings to avoid quota exhaustion.
Monitor Sentry with PinusX Uptime Monitor for independent availability verification. Get Slack and email alerts within 60 seconds when Sentry becomes unreachable. This ensures you know immediately when your error tracking is offline, allowing you to increase manual testing and monitoring vigilance during the gap.
Monitor Sentry uptime with PinusX. Get instant alerts when services go down.