Skip to content

Outage tracker / Sentry

Is Sentry down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Sentry from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Sentry (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 1:27 AM UTC
US-East66 msOperational
US-West115 msOperational
Europe224 msOperational
Asia-Pacific690 msOperational
their status pagetheir claim, not our reading

Sentry reports: All systems operational (“All Systems Operational”)

from Sentry's own status page, checked Sep 3, 2026, 12:27 AM UTC
Our probes and Sentry's own status page agree: both show Sentry as reachable right now.

Sentry's own component breakdown, as they publish it

  • DashboardOperational
  • EU Error IngestionOperational
  • Password-BasedOperational
  • SlackOperational
  • US Error IngestionOperational
  • US Errors AlertingOperational
  • APIOperational
  • EmailOperational
  • EU Errors AlertingOperational
  • EU Transaction IngestionOperational
  • GoogleOperational
  • US Transaction IngestionOperational
  • EU Attachment IngestionOperational
  • GitHubOperational
  • PagerDutyOperational
  • StripeOperational
  • US Attachment IngestionOperational
  • US Transactions AlertingOperational
  • Azure DevOpsOperational
  • EU Profile IngestionOperational
  • Microsoft TeamsOperational
  • US Profile IngestionOperational
  • US Spans AlertingOperational
  • EU Replay IngestionOperational
  • EU Transactions AlertingOperational
  • SAML-Based Single Sign-OnOperational
  • US Replay IngestionOperational
  • EU Span IngestionOperational
  • EU Spans AlertingOperational
  • US Span IngestionOperational
  • EU Cron MonitoringOperational
  • US Cron MonitoringOperational
  • US Uptime MonitoringOperational
  • Custom Metrics (beta)Operational
  • EU Size Analysis IngestionOperational
  • EU Uptime MonitoringOperational
  • Integration PipelineOperational
  • EU Snapshot IngestionOperational
  • US Size Analysis IngestionOperational
  • SeerOperational
  • US Snapshot IngestionOperational

These are Sentry's components, named and scored by Sentry. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Sentry's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Sentry response time, by region

US-East
394msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 281ms2026-08-21 UTC: p95 413ms2026-08-22 UTC: p95 498ms2026-08-23 UTC: p95 540ms2026-08-24 UTC: p95 546ms2026-08-25 UTC: p95 511ms2026-08-26 UTC: p95 575ms2026-08-27 UTC: p95 220ms2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.0s2026-09-01 UTC: p95 190ms2026-09-02 UTC: p95 200ms2026-09-03 UTC: p95 394ms
Aug 5Aug 19Sep 3
US-West
154msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 682ms2026-08-21 UTC: p95 330ms2026-08-22 UTC: p95 301ms2026-08-23 UTC: p95 362ms2026-08-24 UTC: p95 399ms2026-08-25 UTC: p95 357ms2026-08-26 UTC: p95 299ms2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 520ms2026-08-30 UTC: p95 453ms2026-08-31 UTC: p95 358ms2026-09-01 UTC: p95 241ms2026-09-02 UTC: p95 434ms2026-09-03 UTC: p95 154ms
Aug 5Aug 19Sep 3
Europe
298msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 350ms2026-08-21 UTC: p95 452ms2026-08-22 UTC: p95 548ms2026-08-23 UTC: p95 594ms2026-08-24 UTC: p95 428ms2026-08-25 UTC: p95 489ms2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 449ms2026-08-28 UTC: p95 371ms2026-08-29 UTC: p95 389ms2026-08-30 UTC: p95 281ms2026-08-31 UTC: p95 379ms2026-09-01 UTC: p95 369ms2026-09-02 UTC: p95 411ms2026-09-03 UTC: p95 298ms
Aug 5Aug 19Sep 3
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 489ms2026-08-21 UTC: p95 499ms2026-08-22 UTC: p95 462ms2026-08-23 UTC: p95 850ms2026-08-24 UTC: p95 793ms2026-08-25 UTC: p95 717ms2026-08-26 UTC: p95 897ms2026-08-27 UTC: p95 943ms2026-08-28 UTC: p95 719ms2026-08-29 UTC: p95 963ms2026-08-30 UTC: p95 825ms2026-08-31 UTC: p95 868ms2026-09-01 UTC: p95 794ms2026-09-02 UTC: p95 801ms2026-09-03 UTC: p95 1.1s
Aug 5Aug 19Sep 3

Is it Sentry, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Sentry -- it cannot diagnose Sentry's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 66msstatus code: 401checked: Sep 3, 2026, 1:04 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Sentry normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 115msstatus code: 401checked: Sep 3, 2026, 1:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Sentry normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 224msstatus code: 401checked: Sep 3, 2026, 1:27 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Sentry normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 690msstatus code: 401checked: Sep 3, 2026, 12:56 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Sentry normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionSentry is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionSentry is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionSentry is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionSentry is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionSentry is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionSentry is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Sentry, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Sentry yet, which is not evidence that nothing is wrong.

Recent outages

Span ingestion is degraded in US, 6h 14mdeclared on their status page2026-09-01
Sentry requests timing out / 504's, 3h 20mdeclared on their status page2026-09-01
Ingestion backlog, 2h 12mdeclared on their status page2026-08-31
sentry.io is not available, 6h 18mdeclared on their status page2026-08-27
Issues performance is degraded in the US, 4h 19mdeclared on their status page2026-08-26
Errors alerting degraded in US region, 3hdeclared on their status page2026-08-25
Alert backlogs in US, 39mdeclared on their status page2026-08-18
Span & Transaction ingestion delayed in DE, 4h 40mdeclared on their status page2026-08-13

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Sentry since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Sentry covering any window you pick, with our measurements and Sentry's own claim at the time, side by side.

Full availability history for Sentry: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Sentry, and again when they can reach it again. That is our own measurement from ten regions, not Sentry's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Sentry uptime measured by RealUptimeLive, from this page's own readings.
[![Sentry uptime measured by RealUptime](https://realuptime.io/outages/sentry/badge.svg?days=30)](https://realuptime.io/outages/sentry)
<a href="https://realuptime.io/outages/sentry"><img src="https://realuptime.io/outages/sentry/badge.svg?days=30" alt="Sentry uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Sentry's SLA implies, from our measurement

At or above your target

We measured none of downtime for Sentry over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Sentry's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://sentry.io/api/0/organizations/
secondary
https://status.sentry.io/
RealUptime is not affiliated with Sentry; the name identifies what we measured, and nothing here speaks for Sentry's own team. We send a single web request to Sentry from 4 regions on our own schedule and time the response. We do not see inside Sentry's systems, do not use an account or real transaction, and are not the same signal Sentry's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Sentry is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Sentry operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.