Skip to content

Outage tracker

Is the internet down?

When many services are in an incident at the same time it is often not many separate problems: it can be one incident at a layer they share, a CDN, a cloud region, a transit route. We check 946 services from ten regions on our own schedule, and for a service whose status page we can read, this page uses the incident its vendor declares there; for any other it uses our check readings. A provider is named only when at least 5 services that sit behind it are in an incident at once while services on other providers mostly are not. Nothing here comes from user reports or social posts, and nothing here changes any service's own verdict.

Provider incidentevaluated moments ago

Cloudflare incident, from vendor reports and our checks

14 services that share a provider signal are in an incident, as reported by their vendors or by our checks, while services on other providers mostly are not. 25 of the 946 services we watch are in an incident in total. This is a correlation of those readings, not a cause the provider has stated.

Cloudflare: 14 services affected, 20h 44m so far.

ScalewayIncident reportedScalewayIncident reportedGrafana CloudIncident reportedCanvas LMSIncident reportedKlaviyoIncident reportedPowerSchoolIncident reportedSchoologyIncident reportedRailwayIncident reportedSeesawIncident reportedBitstampIncident reportedKrakenIncident reportedTikTokChecks failingScalewayIncident reportedQuay.ioIncident reportedActiveCampaignIncident reportedLinode (Akamai)Incident reportedCloudflareIncident reportedFlutterwaveIncident reportedTwilioIncident reportedAmplitudeIncident reportedSourceHutIncident reportedCloudflareIncident reportedBunny CDNIncident reportedOpenAIIncident reportedGoTo MeetingIncident reported

Who sits behind whom: the measured dependency map

Of the 946 services we track, 939 have a recorded provider signal on their primary endpoint. A service can carry more than one signal (a CDN in front of a cloud region), so the rows overlap. Measured from our own probe responses, daily since Aug 23, 2026, last observation moments ago.

Provider signalKindServicesShare of catalog
Cloudflareedge / CDN278 of 94629%
Amazon CloudFrontedge / CDN161 of 94617%
Fastlyedge / CDN66 of 9467%
Google front endcloud40 of 9464%
AWS us-east-1 (N. Virginia)cloud region33 of 9463%
Verceledge / CDN23 of 9462%
AWS (load balancer or S3 front)cloud22 of 9462%
Akamaiedge / CDN19 of 9462%
Azure Front Dooredge / CDN15 of 9462%
AWS us-west-2 (Oregon)cloud region13 of 9461%
Netlifyedge / CDN9 of 9461%
AWS eu-west-1 (Ireland)cloud region6 of 9461%
AWS eu-central-1 (Frankfurt)cloud region2 of 9460%
AWS ap-northeast-1 (Tokyo)cloud region1 of 9460%

Shared-infrastructure incidents, last 30 days

  • OpenCloudflareNov 4, 2026, 20h 44m so far

    Confidence: likely, based on 8 of the 278 services behind Cloudflare in an incident together while only 6 of the 349 control services were also down. 8 of the 278 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 343 of the 349 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    activecampaigncloudflarecoinbaseflutterwaveklaviyokrakenmonday-comopenairailwayseesawsinchsquaresupabasetrust-wallet

  • ClosedCloudflareNov 4, 2026, 27 min

    Confidence: likely, based on 5 of the 278 services behind Cloudflare in an incident together while only 6 of the 350 control services were also down. 5 of the 278 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 344 of the 350 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyencloudflarecoinbasekrakenoneflow

  • ClosedCloudflareNov 3, 2026, 57 min

    Confidence: likely, based on 5 of the 278 services behind Cloudflare in an incident together while only 4 of the 347 control services were also down. 5 of the 278 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 343 of the 347 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenkrakensinchtrust-walletzoom

  • ClosedCloudflareNov 3, 2026, 20 min

    Confidence: likely, based on 5 of the 279 services behind Cloudflare in an incident together while only 3 of the 352 control services were also down. 5 of the 279 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 349 of the 352 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenkrakenrunpodtrust-walletzoom

  • ClosedCloudflareNov 3, 2026, 2h 54m

    Confidence: likely, based on 8 of the 279 services behind Cloudflare in an incident together while only 4 of the 345 control services were also down. 8 of the 279 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 341 of the 345 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyencloudflaregitlabkrakenmercuryrunpodsinchzoom

  • ClosedCloudflareNov 3, 2026, 1h 2m

    Confidence: likely, based on 5 of the 278 services behind Cloudflare in an incident together while only 5 of the 354 control services were also down. 5 of the 278 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 349 of the 354 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyencloudflaremercuryrunpodzendesk

  • ClosedCloudflareNov 3, 2026, 14 min

    Confidence: likely, based on 5 of the 278 services behind Cloudflare in an incident together while only 6 of the 350 control services were also down. 5 of the 278 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 344 of the 350 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyencloudflaremercuryrunpodzendesk

  • ClosedCloudflareNov 3, 2026, 1h 14m

    Confidence: likely, based on 5 of the 277 services behind Cloudflare in an incident together while only 5 of the 349 control services were also down. 5 of the 277 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 344 of the 349 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenmercuryrunpodsinchzendesk

  • ClosedCloudflareNov 3, 2026, 1h 35m

    Confidence: likely, based on 6 of the 278 services behind Cloudflare in an incident together while only 3 of the 350 control services were also down. 6 of the 278 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 347 of the 350 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenflutterwavemercuryrunpodsinchzendesk

  • ClosedCloudflareNov 2, 2026, 19h 44m

    Confidence: likely, based on 11 of the 278 services behind Cloudflare in an incident together while only 2 of the 348 control services were also down. 11 of the 278 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 346 of the 348 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenaffirmancestry-combitrisebrevocloudflarecoinbaseflutterwavegitlabkrakenledgerlightspeed-posmake-commercuryneonopenaiphraserailwayreplitrunpodsinchsupabasetrust-walletvend-hq

  • ClosedCloudflareOct 29, 2026, 54 min

    Confidence: likely, based on 6 of the 57 services behind Cloudflare in an incident together while only 2 of the 81 control services were also down. 6 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 79 of the 81 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    bigcommerceclerkrailwaysnowflakeworkoszendesk

  • ClosedCloudflareOct 29, 2026, 35 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 81 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 79 of the 81 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    bigcommercecloudflarekrakenrailwaysnowflake

  • ClosedCloudflareOct 29, 2026, 55 min

    Confidence: likely, based on 6 of the 57 services behind Cloudflare in an incident together while only 2 of the 81 control services were also down. 6 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 79 of the 81 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    bigcommercecloudflarekrakenrailwayshopifysnowflake

  • ClosedCloudflareOct 29, 2026, 6h 45m

    Confidence: likely, based on 6 of the 57 services behind Cloudflare in an incident together while only 2 of the 81 control services were also down. 6 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 79 of the 81 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    bigcommercekrakenrailwaysnowflakezendeskzoom

  • ClosedCloudflareOct 28, 2026, 9h 50m

    Confidence: likely, based on 7 of the 57 services behind Cloudflare in an incident together while only 2 of the 79 control services were also down. 7 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 77 of the 79 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenanthropicbigcommercecloudflarekrakenrailwaysupabasezoom

  • ClosedCloudflareOct 28, 2026, 15 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 78 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 76 of the 78 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    bigcommercecloudflarekrakennew-relicrailway

  • ClosedCloudflareOct 28, 2026, 1h 16m

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 3 of the 81 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 78 of the 81 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropicbigcommercecloudflarekrakenrailway

  • ClosedCloudflareOct 28, 2026, 11 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 78 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 76 of the 78 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropicbigcommercekrakenopenairailway

  • ClosedCloudflareOct 27, 2026, 2h 20m

    Confidence: likely, based on 6 of the 57 services behind Cloudflare in an incident together while only 2 of the 81 control services were also down. 6 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 79 of the 81 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    cloudflarecoinbasedigitaloceankrakenrailwaysquare

  • ClosedCloudflareOct 27, 2026, 23 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 80 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 78 of the 80 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    bigcommercecoinbasedigitaloceankrakenrailway

  • ClosedCloudflareOct 27, 2026, 1h 23m

    Confidence: likely, based on 6 of the 57 services behind Cloudflare in an incident together while only 3 of the 78 control services were also down. 6 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 75 of the 78 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropiccloudflarecoinbasekrakenopenairailway

  • ClosedCloudflareOct 27, 2026, 50 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 77 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 75 of the 77 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropiccoinbasekrakenlinearrailway

  • ClosedCloudflareOct 27, 2026, 20 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 76 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 74 of the 76 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    cloudflarecoinbasekrakenlinearrailway

  • ClosedCloudflareOct 25, 2026, 42 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 3 of the 78 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 75 of the 78 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenanthropiccoinbasekrakensupabase

  • ClosedCloudflareOct 25, 2026, 36 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 3 of the 79 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 76 of the 79 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenanthropiccoinbasekrakensupabase

  • ClosedCloudflareOct 23, 2026, 14 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 3 of the 78 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 75 of the 78 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenanthropickrakenopenaisupabase

  • ClosedCloudflareOct 22, 2026, 1d 5h

    Confidence: likely, based on 12 of the 57 services behind Cloudflare in an incident together while only 3 of the 78 control services were also down. 12 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 75 of the 78 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenauth0bigcommerceclerkcloudflarecoinbasegitlabkrakennotionopenairailwayrenderresendsupabaseworkoszendeskzoom

  • ClosedCloudflareOct 22, 2026, 31 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 3 of the 80 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 77 of the 80 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    clerkcloudflarecoinbaserailwaysupabase

  • ClosedCloudflareOct 22, 2026, 5h 39m

    Confidence: likely, based on 7 of the 56 services behind Cloudflare in an incident together while only 3 of the 79 control services were also down. 7 of the 56 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 76 of the 79 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropicclerkcoinbasenotionnpmopenairailwaysupabase

  • ClosedAmazon CloudFrontOct 21, 2026, 1h 34m

    Confidence: likely, based on 5 of the 31 services behind Amazon CloudFront in an incident together while only 3 of the 102 control services were also down. 5 of the 31 services whose responses we measured behind Amazon CloudFront were in an incident together, as reported by their vendors or by our checks, while 99 of the 102 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    akamaicircleciduolingooktatwilio

  • ClosedCloudflareOct 21, 2026, 1h 58m

    Confidence: likely, based on 6 of the 57 services behind Cloudflare in an incident together while only 5 of the 77 control services were also down. 6 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 72 of the 77 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyencoinbasedocker-hubnotionopenairailwaysupabasezoom

  • ClosedCloudflareOct 20, 2026, 1h 3m

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 79 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 77 of the 79 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    cloudflaregitlabnotionrenderzendesk

  • ClosedCloudflareOct 20, 2026, 20 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 4 of the 77 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 73 of the 77 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    cloudflarenotionrailwayrenderzendesk

  • ClosedCloudflareOct 20, 2026, 16 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 4 of the 80 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 76 of the 80 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    cloudflarenotionpayoneerrailwayzendesk

  • ClosedCloudflareOct 15, 2026, 8 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 77 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 75 of the 77 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    bigcommercecloudflarekrakenopenairender

  • ClosedCloudflareOct 15, 2026, 5h 45m

    Confidence: likely, based on 6 of the 57 services behind Cloudflare in an incident together while only 2 of the 76 control services were also down. 6 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 74 of the 76 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    cloudflaregitlabkrakenopenairendersnowflakeworkos

  • ClosedCloudflareOct 15, 2026, 4h 24m

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 77 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 75 of the 77 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    cloudflaregitlabkrakenopenaisnowflake

  • ClosedCloudflareOct 13, 2026, 1d 15h

    Confidence: likely, based on 9 of the 57 services behind Cloudflare in an incident together while only 2 of the 76 control services were also down. 9 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 74 of the 76 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    adyenanthropicbigcommercecloudflarecoinbasegitlabkrakenmercurynpmopenairailwayrendersnowflakesupabasezoom

  • ClosedCloudflareOct 10, 2026, 41 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 1 of the 78 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 77 of the 78 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    cloudflaregroqkrakenopenairesend

  • ClosedCloudflareOct 10, 2026, 3h 29m

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 1 of the 76 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 75 of the 76 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropiccloudflaregroqkrakenopenai

  • ClosedCloudflareOct 10, 2026, 9 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 1 of the 79 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 78 of the 79 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropiccloudflarekrakenopenaizoom

  • ClosedCloudflareOct 9, 2026, 31 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 2 of the 79 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 77 of the 79 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropiccloudflarekrakenopenairesend

  • ClosedCloudflareOct 9, 2026, 46 min

    Confidence: likely, based on 5 of the 57 services behind Cloudflare in an incident together while only 3 of the 77 control services were also down. 5 of the 57 services whose responses we measured behind Cloudflare were in an incident together, as reported by their vendors or by our checks, while 74 of the 77 services on other providers were not. A correlation of those readings; not a statement from the provider, and no service's own verdict is changed by it.

    anthropiccloudflarecoinbasekrakenopenai

How this is measured, and what it cannot tell you

A provider signal is where a service's primary endpoint answered from. Every probe response carries two things we keep: the address our pinned socket actually dialed, and a short fixed set of edge-identifying response headers (cf-ray, x-amz-cf-pop, x-served-by, x-vercel-id, x-azure-ref, server, via). The address is matched against a small table of well-known provider ranges committed in our code (71 prefixes for Cloudflare, Fastly, a few AWS regions and Google, checked against the providers' published lists); the headers are matched only where a header is one that provider alone sets. A match says "this response came from behind X". No match says nothing. We never guess from a vendor name.

A provider incident is declared only when, inside a 15-minute window, at least 5 distinct services sharing one signal have an incident open (for a service whose status page we read, the incident its vendor declared there; for any other, an event our checks opened, which the database admits from our checks alone) AND the control group, the services that carry some other signal, mostly have none: at most 20% of them in an incident, over at least 10 of them. If the control group is in an incident too, the failure is broader than the provider and nothing is declared. It closes when the rule stops holding.

What it cannot tell you. It is a correlation of vendor reports and our check readings, not a root cause the provider has stated, and it can be wrong in both directions. It misses incidents at providers our prefix excerpt does not cover, incidents that affect fewer than 5 of the services we happen to track, and incidents behind a second layer we cannot see (a service on its own network whose database lives in a failing region). It can over-read a coincidence of unrelated incidents behind one very popular provider, which is why the control group and the threshold exist. The dependency map counts only services whose primary endpoint answers from behind a provider; a service that uses a provider for something we do not probe is not on it. A service's own verdict on its own page is never changed by anything here.

Machine-readable: /api/v1/outages/internet (no key), and the is_the_internet_down tool on the keyless MCP server. Each service's JSON answer also carries its own provider signals under infra. Read the tracker methodology for what a single reading means.