Is Sentry Down?

No — Sentry is up

Reachable from all 17 checked regions

Average response time: 934ms

Last checked 17 minutes ago · checks run every 30 minutes

Official status page: https://status.sentry.io

Sentry uptime

100%

Last 7 days

99.83%

Last 30 days

99.07%

Last 90 days

905ms

Avg response, 30 days

Measured from multiple regions every 30 minutes. Percentages count only checks that returned an availability answer — 80 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

7-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

939ms

DNS 0ms TCP 6ms TLS 8ms TTFB 300ms

arn

1059ms

DNS 0ms TCP 6ms TLS 19ms TTFB 359ms

cdg

914ms

DNS 0ms TCP 2ms TLS 9ms TTFB 345ms

dfw

244ms

DNS 0ms TCP 1ms TLS 5ms TTFB 100ms

ewr

261ms

DNS 0ms TCP 8ms TLS 10ms TTFB 129ms

fra

466ms

DNS 0ms TCP 1ms TLS 14ms TTFB 287ms

gru

1084ms

DNS 0ms TCP 3ms TLS 65ms TTFB 571ms

iad

199ms

DNS 0ms TCP 2ms TLS 4ms TTFB 136ms

jnb

3641ms

DNS 0ms TCP 1ms TLS 177ms TTFB 2477ms

lax

565ms

DNS 0ms TCP 2ms TLS 11ms TTFB 202ms

lhr

719ms

DNS 0ms TCP 2ms TLS 11ms TTFB 336ms

nrt

832ms

DNS 0ms TCP 1ms TLS 40ms TTFB 578ms

ord

349ms

DNS 0ms TCP 21ms TLS 25ms TTFB 215ms

sin

2007ms

DNS 0ms TCP 1ms TLS 3ms TTFB 1129ms

sjc

386ms

DNS 0ms TCP 11ms TLS 19ms TTFB 256ms

syd

1719ms

DNS 0ms TCP 1ms TLS 155ms TTFB 918ms

yyz

496ms

DNS 0ms TCP 1ms TLS 25ms TTFB 236ms

What Sentry does

Sentry is an application monitoring and error tracking platform that helps developers identify and fix crashes in real time. It captures exceptions, performance data, and session replays from web, mobile, and backend applications. Sentry is used by thousands of engineering teams to maintain application health and reduce time to resolution for bugs.

What an outage looks like

When Sentry is down, error reports from your applications will fail to be ingested. This means new crashes and exceptions go unrecorded, creating blind spots in your monitoring. The Sentry dashboard becomes inaccessible, preventing you from investigating existing issues. Alert notifications for error spikes will not fire.

What to do about it

Check status.sentry.io for the current status. The Sentry SDKs in your application are designed to fail gracefully, so a Sentry outage will not crash your application. Events are buffered locally in the SDK and some may be retried. Check your application logs as a fallback for error visibility during the outage.

Is it down for everyone, or just you?

If this page says Sentry is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Sentry outage FAQ

Will my application crash if Sentry is down?

No, Sentry SDKs are designed to fail silently. If Sentry's ingestion endpoint is unreachable, the SDK will drop or buffer events without affecting your application's performance or stability. Your application continues running normally, you just lose error visibility temporarily.

Are errors lost during a Sentry outage?

Most Sentry SDKs have a limited local buffer and will retry sending events. However, during an extended outage, the buffer fills up and new events are dropped. Events that occurred during the outage period will not appear in Sentry. Your application logs are the best fallback for this period.

How do I monitor my monitoring tool?

Use an independent uptime monitoring service like FlareWarden to monitor Sentry's availability. Configure alerts through a non-Sentry channel (like email or Slack) so you know immediately when Sentry is down and can switch to checking application logs directly.

Does a Sentry outage affect performance monitoring?

Yes, Sentry's performance monitoring, session replays, and profiling all use the same ingestion pipeline. During an outage, all of these features will stop receiving data. Performance baselines may show gaps for the outage period in your dashboards once service is restored.

How we measure this

We request Sentry's public endpoint every 30 minutes from Fly.io regions across six continents — the most recent check ran from 17 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Sentry publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Sentry goes down

This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required