Skip to content

Outage tracker / Sentry

Is Sentry down?

I'm having a problem

Vendor reports no incidentWhat Sentry reports

Sentry reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:38 UTC.

Sentry's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Sentry pass from all 10 regions we check.

As of Nov 5, 2026, 3:40 PM UTC, RealUptime's checks of Sentry passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:40 PM UTC
US-East931 msChecks passing
US-West1055 msChecks passing
Europe687 msChecks passing
Asia-Pacific950 msChecks passing
US-Central131 msChecks passing
Canada882 msChecks passing
UK158 msChecks passing
Southeast Asia1092 msChecks passing
Australia2245 msChecks passing
South America281 msChecks passing
their status pagetheir claim, not our reading

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

from Sentry's own status page, checked Nov 5, 2026, 3:32 PM UTC
Sentry's own status page shows no incident, and our checks of Sentry pass 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
  • EU Errors AlertingOperational
  • EU Transaction IngestionOperational
  • EmailOperational
  • 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
1.2sp95 · 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-10-07 UTC: p95 187ms2026-10-08 UTC: p95 262ms2026-10-09 UTC: p95 339ms2026-10-10 UTC: p95 294ms2026-10-11 UTC: p95 279ms2026-10-12 UTC: p95 362ms2026-10-13 UTC: p95 284ms2026-10-14 UTC: p95 373ms2026-10-15 UTC: p95 399ms2026-10-16 UTC: p95 437ms2026-10-17 UTC: p95 761ms2026-10-18 UTC: p95 780ms2026-10-19 UTC: p95 716ms2026-10-20 UTC: p95 250ms2026-10-21 UTC: p95 638ms2026-10-22 UTC: p95 215ms2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 172ms2026-10-25 UTC: p95 193ms2026-10-26 UTC: p95 209ms2026-10-27 UTC: p95 993ms2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
US-West
1.4sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 357ms2026-10-08 UTC: p95 442ms2026-10-09 UTC: p95 436ms2026-10-10 UTC: p95 511ms2026-10-11 UTC: p95 523ms2026-10-12 UTC: p95 495ms2026-10-13 UTC: p95 423ms2026-10-14 UTC: p95 672ms2026-10-15 UTC: p95 666ms2026-10-16 UTC: p95 685ms2026-10-17 UTC: p95 646ms2026-10-18 UTC: p95 660ms2026-10-19 UTC: p95 590ms2026-10-20 UTC: p95 261ms2026-10-21 UTC: p95 362ms2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Europe
1.0sp95 · 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-10-07 UTC: p95 933ms2026-10-08 UTC: p95 515ms2026-10-09 UTC: p95 337ms2026-10-10 UTC: p95 317ms2026-10-11 UTC: p95 354ms2026-10-12 UTC: p95 338ms2026-10-13 UTC: p95 408ms2026-10-14 UTC: p95 329ms2026-10-15 UTC: p95 412ms2026-10-16 UTC: p95 323ms2026-10-17 UTC: p95 514ms2026-10-18 UTC: p95 357ms2026-10-19 UTC: p95 843ms2026-10-20 UTC: p95 825ms2026-10-21 UTC: p95 313ms2026-10-22 UTC: p95 278ms2026-10-23 UTC: p95 359ms2026-10-24 UTC: p95 328ms2026-10-25 UTC: p95 276ms2026-10-26 UTC: p95 753ms2026-10-27 UTC: p95 462ms2026-10-28 UTC: p95 505ms2026-10-29 UTC: p95 455ms2026-10-30 UTC: p95 640ms2026-10-31 UTC: p95 559ms2026-11-01 UTC: p95 602ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Asia-Pacific
3.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 775ms2026-10-08 UTC: p95 601ms2026-10-09 UTC: p95 540ms2026-10-10 UTC: p95 486ms2026-10-11 UTC: p95 556ms2026-10-12 UTC: p95 531ms2026-10-13 UTC: p95 708ms2026-10-14 UTC: p95 512ms2026-10-15 UTC: p95 344ms2026-10-16 UTC: p95 556ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 407ms2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.9s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
US-Central
926msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 236ms2026-10-08 UTC: p95 233ms2026-10-09 UTC: p95 308ms2026-10-10 UTC: p95 238ms2026-10-11 UTC: p95 218ms2026-10-12 UTC: p95 295ms2026-10-13 UTC: p95 252ms2026-10-14 UTC: p95 274ms2026-10-15 UTC: p95 184ms2026-10-16 UTC: p95 201ms2026-10-17 UTC: p95 225ms2026-10-18 UTC: p95 267ms2026-10-19 UTC: p95 478ms2026-10-20 UTC: p95 283ms2026-10-21 UTC: p95 351ms2026-10-22 UTC: p95 280ms2026-10-23 UTC: p95 274ms2026-10-24 UTC: p95 472ms2026-10-25 UTC: p95 315ms2026-10-26 UTC: p95 225ms2026-10-27 UTC: p95 616ms2026-10-28 UTC: p95 426ms2026-10-29 UTC: p95 575ms2026-10-30 UTC: p95 817ms2026-10-31 UTC: p95 735ms2026-11-01 UTC: p95 380ms2026-11-02 UTC: p95 732ms2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 926ms
Oct 7Oct 21Nov 5
Canada
464msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 614ms2026-10-08 UTC: p95 568ms2026-10-09 UTC: p95 516ms2026-10-10 UTC: p95 599ms2026-10-11 UTC: p95 480ms2026-10-12 UTC: p95 575ms2026-10-13 UTC: p95 603ms2026-10-14 UTC: p95 390ms2026-10-15 UTC: p95 244ms2026-10-16 UTC: p95 212ms2026-10-17 UTC: p95 289ms2026-10-18 UTC: p95 284ms2026-10-19 UTC: p95 497ms2026-10-20 UTC: p95 294ms2026-10-21 UTC: p95 439ms2026-10-22 UTC: p95 362ms2026-10-23 UTC: p95 274ms2026-10-24 UTC: p95 262ms2026-10-25 UTC: p95 282ms2026-10-26 UTC: p95 265ms2026-10-27 UTC: p95 226ms2026-10-28 UTC: p95 709ms2026-10-29 UTC: p95 723ms2026-10-30 UTC: p95 512ms2026-10-31 UTC: p95 495ms2026-11-01 UTC: p95 277ms2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 818ms2026-11-05 UTC: p95 464ms
Oct 7Oct 21Nov 5
UK
742msp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 205ms2026-10-08 UTC: p95 216ms2026-10-09 UTC: p95 385ms2026-10-10 UTC: p95 394ms2026-10-11 UTC: p95 464ms2026-10-12 UTC: p95 462ms2026-10-13 UTC: p95 316ms2026-10-14 UTC: p95 356ms2026-10-15 UTC: p95 212ms2026-10-16 UTC: p95 231ms2026-10-17 UTC: p95 466ms2026-10-18 UTC: p95 352ms2026-10-19 UTC: p95 4.7s2026-10-20 UTC: p95 183ms2026-10-21 UTC: p95 211ms2026-10-22 UTC: p95 441ms2026-10-23 UTC: p95 358ms2026-10-24 UTC: p95 319ms2026-10-25 UTC: p95 253ms2026-10-26 UTC: p95 282ms2026-10-27 UTC: p95 411ms2026-10-28 UTC: p95 376ms2026-10-29 UTC: p95 295ms2026-10-30 UTC: p95 245ms2026-10-31 UTC: p95 592ms2026-11-01 UTC: p95 982ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 280ms2026-11-04 UTC: p95 424ms2026-11-05 UTC: p95 742ms
Oct 7Oct 21Nov 5
Southeast Asia
2.0sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 937ms2026-10-08 UTC: p95 929ms2026-10-09 UTC: p95 356ms2026-10-10 UTC: p95 845ms2026-10-11 UTC: p95 347ms2026-10-12 UTC: p95 652ms2026-10-13 UTC: p95 406ms2026-10-14 UTC: p95 879ms2026-10-15 UTC: p95 343ms2026-10-16 UTC: p95 418ms2026-10-17 UTC: p95 559ms2026-10-18 UTC: p95 441ms2026-10-19 UTC: p95 989ms2026-10-20 UTC: p95 838ms2026-10-21 UTC: p95 432ms2026-10-22 UTC: p95 836ms2026-10-23 UTC: p95 841ms2026-10-24 UTC: p95 919ms2026-10-25 UTC: p95 813ms2026-10-26 UTC: p95 806ms2026-10-27 UTC: p95 945ms2026-10-28 UTC: p95 404ms2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 894ms2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Australia
2.5sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 528ms2026-10-08 UTC: p95 627ms2026-10-09 UTC: p95 560ms2026-10-10 UTC: p95 558ms2026-10-11 UTC: p95 541ms2026-10-12 UTC: p95 576ms2026-10-13 UTC: p95 568ms2026-10-14 UTC: p95 886ms2026-10-15 UTC: p95 923ms2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 930ms2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 695ms2026-10-23 UTC: p95 613ms2026-10-24 UTC: p95 893ms2026-10-25 UTC: p95 507ms2026-10-26 UTC: p95 558ms2026-10-27 UTC: p95 574ms2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
South America
1.5sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 684ms2026-10-08 UTC: p95 746ms2026-10-09 UTC: p95 475ms2026-10-10 UTC: p95 741ms2026-10-11 UTC: p95 449ms2026-10-12 UTC: p95 486ms2026-10-13 UTC: p95 576ms2026-10-14 UTC: p95 725ms2026-10-15 UTC: p95 593ms2026-10-16 UTC: p95 749ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 927ms2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 447ms2026-10-22 UTC: p95 808ms2026-10-23 UTC: p95 7.1s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.5s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5

Check your own site while you wait on Sentry

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.

Email me when Sentry reports an incident on its status page, and again when it reports it resolved.

Get an email when Sentry reports an incident

Email me when Sentry reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Sentry's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 931msstatus code: 401checked: Nov 5, 2026, 3:20 PM 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
      Checks passinglatency: 1055msstatus code: 401checked: Nov 5, 2026, 3:20 PM 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.
    • US-Central
      Checks passinglatency: 131msstatus code: 401checked: Nov 5, 2026, 3:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Sentry normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 882msstatus code: 401checked: Nov 5, 2026, 3:34 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Sentry normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 281msstatus code: 401checked: Nov 5, 2026, 3:36 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Sentry normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 687msstatus code: 401checked: Nov 5, 2026, 3:30 PM 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.
    • UK
      Checks passinglatency: 158msstatus code: 401checked: Nov 5, 2026, 3:33 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Sentry normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 950msstatus code: 401checked: Nov 5, 2026, 3:08 PM 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.
    • Southeast Asia
      Checks passinglatency: 1092msstatus code: 401checked: Nov 5, 2026, 3:38 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Sentry normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2245msstatus code: 401checked: Nov 5, 2026, 3:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Sentry normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

Ingestion delays across all data, 1h 10mdeclared on their status page2026-11-04
Delays in spans and transactions processing, 1h 45mdeclared on their status page2026-11-03
Sentry.io dashboard and API is down, 1h 33mdeclared on their status page2026-11-03
Sentry dashboard is down, 4h 21mdeclared on their status page2026-11-02
Increased latency processing integration webhooks, 21mdeclared on their status page2026-10-21
Sentry.io not loading in US region, 1hdeclared on their status page2026-10-21
Sentry.io not loading, 3h 18mdeclared on their status page2026-10-20
Sentry is down, 53mdeclared on their status page2026-10-19

check 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 check readings and Sentry's own claim at the time, side by side.

Full check history for Sentry: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Sentry uptime by RealUptime's checksLive, from this page's own readings.
[![Sentry uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Sentry down?", https://realuptime.io/outages/sentry. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://sentry.io/api/0/organizations/
secondary
https://status.sentry.io/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: sentry.io

RealUptime is not affiliated with Sentry; the name identifies what we checked, and nothing here speaks for Sentry's own team. We send a single web request to Sentry from 10 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.