Skip to content

Outage tracker / Sentry

Is Sentry down?

I'm having a problem

Operationalchecked moments ago

We reached Sentry from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, Sentry answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 8:16 PM UTC
US-East327 msOperational
US-West117 msOperational
Europe199 msOperational
Asia-Pacific857 msOperational
US-Central256 msOperational
Canada397 msOperational
UK152 msOperational
Southeast Asia374 msOperational
Australia576 msOperational
South America233 msOperational
their status pagetheir claim, not our reading

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

from Sentry's own status page, checked Oct 5, 2026, 7:52 PM 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
  • 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
636msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 313ms2026-09-07 UTC: p95 337ms2026-09-08 UTC: p95 352ms2026-09-09 UTC: p95 283ms2026-09-10 UTC: p95 299ms2026-09-11 UTC: p95 182ms2026-09-12 UTC: p95 399ms2026-09-13 UTC: p95 344ms2026-09-14 UTC: p95 188ms2026-09-15 UTC: p95 171ms2026-09-16 UTC: p95 201ms2026-09-17 UTC: p95 203ms2026-09-18 UTC: p95 198ms2026-09-19 UTC: p95 185ms2026-09-20 UTC: p95 199ms2026-09-21 UTC: p95 282ms2026-09-22 UTC: p95 201ms2026-09-23 UTC: p95 325ms2026-09-24 UTC: p95 397ms2026-09-25 UTC: p95 366ms2026-09-26 UTC: p95 329ms2026-09-27 UTC: p95 408ms2026-09-28 UTC: p95 462ms2026-09-29 UTC: p95 554ms2026-09-30 UTC: p95 384ms2026-10-01 UTC: p95 475ms2026-10-02 UTC: p95 459ms2026-10-03 UTC: p95 453ms2026-10-04 UTC: p95 470ms2026-10-05 UTC: p95 636ms
Sep 6Sep 20Oct 5
US-West
386msp95 · 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-09-06 UTC: p95 875ms2026-09-07 UTC: p95 793ms2026-09-08 UTC: p95 930ms2026-09-09 UTC: p95 973ms2026-09-10 UTC: p95 939ms2026-09-11 UTC: p95 265ms2026-09-12 UTC: p95 423ms2026-09-13 UTC: p95 405ms2026-09-14 UTC: p95 433ms2026-09-15 UTC: p95 475ms2026-09-16 UTC: p95 432ms2026-09-17 UTC: p95 304ms2026-09-18 UTC: p95 400ms2026-09-19 UTC: p95 303ms2026-09-20 UTC: p95 297ms2026-09-21 UTC: p95 295ms2026-09-22 UTC: p95 306ms2026-09-23 UTC: p95 313ms2026-09-24 UTC: p95 315ms2026-09-25 UTC: p95 464ms2026-09-26 UTC: p95 335ms2026-09-27 UTC: p95 283ms2026-09-28 UTC: p95 679ms2026-09-29 UTC: p95 712ms2026-09-30 UTC: p95 950ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 904ms2026-10-03 UTC: p95 934ms2026-10-04 UTC: p95 334ms2026-10-05 UTC: p95 386ms
Sep 6Sep 20Oct 5
Europe
335msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 621ms2026-09-07 UTC: p95 610ms2026-09-08 UTC: p95 604ms2026-09-09 UTC: p95 754ms2026-09-10 UTC: p95 715ms2026-09-11 UTC: p95 373ms2026-09-12 UTC: p95 545ms2026-09-13 UTC: p95 445ms2026-09-14 UTC: p95 252ms2026-09-15 UTC: p95 229ms2026-09-16 UTC: p95 225ms2026-09-17 UTC: p95 277ms2026-09-18 UTC: p95 273ms2026-09-19 UTC: p95 225ms2026-09-20 UTC: p95 335ms2026-09-21 UTC: p95 286ms2026-09-22 UTC: p95 298ms2026-09-23 UTC: p95 276ms2026-09-24 UTC: p95 278ms2026-09-25 UTC: p95 315ms2026-09-26 UTC: p95 257ms2026-09-27 UTC: p95 208ms2026-09-28 UTC: p95 545ms2026-09-29 UTC: p95 268ms2026-09-30 UTC: p95 334ms2026-10-01 UTC: p95 356ms2026-10-02 UTC: p95 297ms2026-10-03 UTC: p95 315ms2026-10-04 UTC: p95 248ms2026-10-05 UTC: p95 335ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.0sp95 · 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-09-06 UTC: p95 456ms2026-09-07 UTC: p95 445ms2026-09-08 UTC: p95 559ms2026-09-09 UTC: p95 384ms2026-09-10 UTC: p95 533ms2026-09-11 UTC: p95 676ms2026-09-12 UTC: p95 514ms2026-09-13 UTC: p95 490ms2026-09-14 UTC: p95 450ms2026-09-15 UTC: p95 427ms2026-09-16 UTC: p95 399ms2026-09-17 UTC: p95 442ms2026-09-18 UTC: p95 442ms2026-09-19 UTC: p95 381ms2026-09-20 UTC: p95 409ms2026-09-21 UTC: p95 289ms2026-09-22 UTC: p95 381ms2026-09-23 UTC: p95 411ms2026-09-24 UTC: p95 333ms2026-09-25 UTC: p95 429ms2026-09-26 UTC: p95 552ms2026-09-27 UTC: p95 807ms2026-09-28 UTC: p95 824ms2026-09-29 UTC: p95 755ms2026-09-30 UTC: p95 717ms2026-10-01 UTC: p95 668ms2026-10-02 UTC: p95 942ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
US-Central
263msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 720ms2026-09-07 UTC: p95 780ms2026-09-08 UTC: p95 766ms2026-09-09 UTC: p95 936ms2026-09-10 UTC: p95 869ms2026-09-11 UTC: p95 479ms2026-09-12 UTC: p95 221ms2026-09-13 UTC: p95 211ms2026-09-14 UTC: p95 348ms2026-09-15 UTC: p95 337ms2026-09-16 UTC: p95 215ms2026-09-17 UTC: p95 216ms2026-09-18 UTC: p95 260ms2026-09-19 UTC: p95 211ms2026-09-20 UTC: p95 262ms2026-09-21 UTC: p95 302ms2026-09-22 UTC: p95 215ms2026-09-23 UTC: p95 294ms2026-09-24 UTC: p95 282ms2026-09-25 UTC: p95 213ms2026-09-26 UTC: p95 269ms2026-09-27 UTC: p95 369ms2026-09-28 UTC: p95 478ms2026-09-29 UTC: p95 723ms2026-09-30 UTC: p95 443ms2026-10-01 UTC: p95 274ms2026-10-02 UTC: p95 221ms2026-10-03 UTC: p95 202ms2026-10-04 UTC: p95 238ms2026-10-05 UTC: p95 263ms
Sep 6Sep 20Oct 5
Canada
407msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 876ms2026-09-07 UTC: p95 816ms2026-09-08 UTC: p95 523ms2026-09-09 UTC: p95 844ms2026-09-10 UTC: p95 880ms2026-09-11 UTC: p95 852ms2026-09-12 UTC: p95 269ms2026-09-13 UTC: p95 261ms2026-09-14 UTC: p95 248ms2026-09-15 UTC: p95 309ms2026-09-16 UTC: p95 356ms2026-09-17 UTC: p95 215ms2026-09-18 UTC: p95 241ms2026-09-19 UTC: p95 252ms2026-09-20 UTC: p95 256ms2026-09-21 UTC: p95 259ms2026-09-22 UTC: p95 399ms2026-09-23 UTC: p95 475ms2026-09-24 UTC: p95 366ms2026-09-25 UTC: p95 239ms2026-09-26 UTC: p95 292ms2026-09-27 UTC: p95 278ms2026-09-28 UTC: p95 246ms2026-09-29 UTC: p95 227ms2026-09-30 UTC: p95 299ms2026-10-01 UTC: p95 327ms2026-10-02 UTC: p95 255ms2026-10-03 UTC: p95 268ms2026-10-04 UTC: p95 292ms2026-10-05 UTC: p95 407ms
Sep 6Sep 20Oct 5
UK
257msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 433ms2026-09-07 UTC: p95 446ms2026-09-08 UTC: p95 424ms2026-09-09 UTC: p95 402ms2026-09-10 UTC: p95 438ms2026-09-11 UTC: p95 224ms2026-09-12 UTC: p95 220ms2026-09-13 UTC: p95 326ms2026-09-14 UTC: p95 495ms2026-09-15 UTC: p95 214ms2026-09-16 UTC: p95 197ms2026-09-17 UTC: p95 203ms2026-09-18 UTC: p95 206ms2026-09-19 UTC: p95 205ms2026-09-20 UTC: p95 210ms2026-09-21 UTC: p95 229ms2026-09-22 UTC: p95 243ms2026-09-23 UTC: p95 213ms2026-09-24 UTC: p95 178ms2026-09-25 UTC: p95 427ms2026-09-26 UTC: p95 227ms2026-09-27 UTC: p95 191ms2026-09-28 UTC: p95 213ms2026-09-29 UTC: p95 193ms2026-09-30 UTC: p95 197ms2026-10-01 UTC: p95 231ms2026-10-02 UTC: p95 209ms2026-10-03 UTC: p95 384ms2026-10-04 UTC: p95 194ms2026-10-05 UTC: p95 257ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 776ms2026-09-08 UTC: p95 748ms2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 770ms2026-09-13 UTC: p95 981ms2026-09-14 UTC: p95 844ms2026-09-15 UTC: p95 745ms2026-09-16 UTC: p95 701ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 827ms2026-09-19 UTC: p95 468ms2026-09-20 UTC: p95 953ms2026-09-21 UTC: p95 341ms2026-09-22 UTC: p95 867ms2026-09-23 UTC: p95 393ms2026-09-24 UTC: p95 856ms2026-09-25 UTC: p95 371ms2026-09-26 UTC: p95 394ms2026-09-27 UTC: p95 392ms2026-09-28 UTC: p95 957ms2026-09-29 UTC: p95 377ms2026-09-30 UTC: p95 540ms2026-10-01 UTC: p95 988ms2026-10-02 UTC: p95 882ms2026-10-03 UTC: p95 361ms2026-10-04 UTC: p95 617ms2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Australia
604msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 878ms2026-09-07 UTC: p95 892ms2026-09-08 UTC: p95 819ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 981ms2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 964ms2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 662ms2026-09-15 UTC: p95 620ms2026-09-16 UTC: p95 568ms2026-09-17 UTC: p95 633ms2026-09-18 UTC: p95 624ms2026-09-19 UTC: p95 978ms2026-09-20 UTC: p95 917ms2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 992ms2026-09-24 UTC: p95 993ms2026-09-25 UTC: p95 870ms2026-09-26 UTC: p95 797ms2026-09-27 UTC: p95 946ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 782ms2026-09-30 UTC: p95 872ms2026-10-01 UTC: p95 779ms2026-10-02 UTC: p95 789ms2026-10-03 UTC: p95 814ms2026-10-04 UTC: p95 719ms2026-10-05 UTC: p95 604ms
Sep 6Sep 20Oct 5
South America
641msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 956ms2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 956ms2026-09-11 UTC: p95 823ms2026-09-12 UTC: p95 825ms2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 753ms2026-09-15 UTC: p95 467ms2026-09-16 UTC: p95 455ms2026-09-17 UTC: p95 459ms2026-09-18 UTC: p95 463ms2026-09-19 UTC: p95 457ms2026-09-20 UTC: p95 773ms2026-09-21 UTC: p95 465ms2026-09-22 UTC: p95 441ms2026-09-23 UTC: p95 465ms2026-09-24 UTC: p95 471ms2026-09-25 UTC: p95 644ms2026-09-26 UTC: p95 438ms2026-09-27 UTC: p95 673ms2026-09-28 UTC: p95 645ms2026-09-29 UTC: p95 721ms2026-09-30 UTC: p95 461ms2026-10-01 UTC: p95 502ms2026-10-02 UTC: p95 537ms2026-10-03 UTC: p95 675ms2026-10-04 UTC: p95 521ms2026-10-05 UTC: p95 641ms
Sep 6Sep 20Oct 5

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.

Get an email when we see Sentry go down, and when it is back

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.

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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 327msstatus code: 401checked: Oct 5, 2026, 7:50 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
      Operationallatency: 117msstatus code: 401checked: Oct 5, 2026, 8:07 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
      Operationallatency: 256msstatus code: 401checked: Oct 5, 2026, 7:27 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
      Operationallatency: 397msstatus code: 401checked: Oct 5, 2026, 7:37 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
    Operationallatency: 233msstatus code: 401checked: Oct 5, 2026, 7:33 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 199msstatus code: 401checked: Oct 5, 2026, 7:51 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
      Operationallatency: 152msstatus code: 401checked: Oct 5, 2026, 7:28 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 857msstatus code: 401checked: Oct 5, 2026, 8:16 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
      Operationallatency: 374msstatus code: 401checked: Oct 5, 2026, 7:32 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
      Operationallatency: 576msstatus code: 401checked: Oct 5, 2026, 7:54 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 outages

Delays in spans ingestion, 41mdeclared on their status page2026-09-18
Delayed ingestion of errors in EU, 3h 20mdeclared on their status page2026-09-18
Ingestion is delayed in US, 57mdeclared on their status page2026-09-10
Sentry.io elevated number of 500 errors, 1h 1mdeclared on their status page2026-09-10
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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.