RealUptime

 ⟨136 unchanged words⟩  are RealUptime's own check readings, never user reportsreports. For a service whose status feed we can read, `vendor.feed_working` is true and never`vendor` holds the vendor's own declared incident from its status page.page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "blocked" means our check was refused, which ⟨8 unchanged words⟩ A no-data answer is never a passing check. ThisOur ischeck readings are our own reading from outside, not the  ⟨12 unchanged words⟩ 

 ⟨89 unchanged words⟩  a caller must hold the key. User reports, public chatter and the vendors' own statuspublic pageschatter are not read for a stack (those  ⟨9 unchanged words⟩ here; a member's own page still shows it. A member whose own status feed RealUptime reads is levelled by the vendor's declared incident instead of our checks (`services[].vendor.feed_working` is true, its plate label says so, major or critical reads as down, minor as degraded, none as up, and no probe event is listed for it); `summary.counts.vendor_incident` and `vendor_quiet` count those members apart from the check counts. An unknown key answers `summary.level: "not_found"`, ⟨8 unchanged words⟩  are RealUptime's own check readings, never user reportsreports. For a service whose status feed we can read, `vendor.feed_working` is true and never`vendor` holds the vendor's own declared incident from its status page.page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "blocked" means our check was refused, which ⟨8 unchanged words⟩ A no-data answer is never a passing check. ThisOur ischeck readings are our own reading from outside, not the  ⟨12 unchanged words⟩ 

 ⟨165 unchanged words⟩  are RealUptime's own check readings, never user reportsreports. For a service whose status feed we can read, `vendor.feed_working` is true and never`vendor` holds the vendor's own declared incident from its status page.page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "blocked" means our check was refused, which ⟨8 unchanged words⟩ A no-data answer is never a passing check. ThisOur ischeck readings are our own reading from outside, not the  ⟨12 unchanged words⟩ 

 ⟨62 unchanged words⟩ the service is not in RealUptime's catalog). When the service's status feed works, `vendor` carries what the vendor itself declares on its status page, and the verdict, `verdict_source` and plate then come from that declaration alone (down while its live incident is rated major or critical, otherwise up); our own reading is `checks_reading`, shown beside it. Also returns `plate`, the public page's headline:  ⟨76 unchanged words⟩  are RealUptime's own check readings, never user reportsreports. For a service whose status feed we can read, `vendor.feed_working` is true and never`vendor` holds the vendor's own declared incident from its status page.page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "blocked" means our check was refused, which ⟨8 unchanged words⟩ A no-data answer is never a passing check. ThisOur ischeck readings are our own reading from outside, not the  ⟨12 unchanged words⟩ 

 ⟨144 unchanged words⟩  are RealUptime's own check readings, never user reportsreports. For a service whose status feed we can read, `vendor.feed_working` is true and never`vendor` holds the vendor's own declared incident from its status page.page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "blocked" means our check was refused, which ⟨8 unchanged words⟩ A no-data answer is never a passing check. ThisOur ischeck readings are our own reading from outside, not the  ⟨12 unchanged words⟩ 

Past probe events RealUptime recorded for one catalog service.service whose status feed we cannot read. For a service whose feed works, `recent_events`, `last_outage` and `reliability` are `available: false` with the reason (the vendor's declared incidents are what count, our probe events are not listed or counted), and `vendor` leads. A probe event opens only when our checks  ⟨187 unchanged words⟩  are RealUptime's own check readings, never user reportsreports. For a service whose status feed we can read, `vendor.feed_working` is true and never`vendor` holds the vendor's own declared incident from its status page.page: that statement leads and gives the verdict and plate, and `checks_reading` and `vendor.regional_reading` are our check reading beside it, never a second outage. Where we cannot read a feed (`vendor.feed_working` false), the answer is our checks alone. "blocked" means our check was refused, which ⟨8 unchanged words⟩ A no-data answer is never a passing check. ThisOur ischeck readings are our own reading from outside, not the  ⟨12 unchanged words⟩ 

 ⟨44 unchanged words⟩ normal" or "insufficient_data", and RealUptime's own probecheck reading for the same regions so the two ⟨29 unchanged words⟩  Report volume never opens, extends or closes ana outageprobe event in RealUptime's event record; only probeour measurementschecks do. "insufficient_data" means there are not enough ⟨19 unchanged words⟩ no problems reported". Readings are RealUptime's own probecheck measurementsreadings, never user reports and never the vendor's status page. "blocked" means our probecheck was refused, which is NOT a confirmedfailed outage.check of the service. A no-data answer is never a healthypassing answer.check. This is our own reading from outside, not the service's official status. Cite the returned source.url when repeating any of this.

 ⟨42 unchanged words⟩  roll-up: `summary.headline` ("2 of 6 services downwith checks failing or degraded"), the worst member level,  ⟨82 unchanged words⟩ about any service's health. Readings are RealUptime's own probecheck measurementsreadings, never user reports and never the vendor's status page. "blocked" means our probecheck was refused, which is NOT a confirmedfailed outage.check of the service. A no-data answer is never a healthypassing answer.check. This is our own reading from outside, not the service's official status. Cite the returned source.url when repeating any of this.

How the internet looks from RealUptime's probecheck regions right now (https://realuptime.io/outages/internet-weather): for  ⟨147 unchanged words⟩ instead. Takes no arguments. Readings are RealUptime's own probecheck measurementsreadings, never user reports and never the vendor's status page. "blocked" means our probecheck was refused, which is NOT a confirmedfailed outage.check of the service. A no-data answer is never a healthypassing answer.check. This is our own reading from outside, not the service's official status. Cite the returned source.url when repeating any of this.

IsDo RealUptime's own checks of a third-party service currently downfail, asfrom measurednamed byregions? RealUptime'sA owncheck probesis fromone upunauthenticated request to fourthe namedservice's regions?front door; it says whether that check passed or failed, not whether the service works for users. Returns a verdict of "up" (our checks pass), "down" (our checks fail), "down_in_some_regions" (our checks fail from some regions), "blocked", "no_data", or "not_covered ⟨39 unchanged words⟩ the sentence under it. "reachable_reports_elevated" means our probeschecks answerpass but user reports or public chatter are above their spike threshold: NOT ana outagefailed check, and never to be quoted as one.  ⟨16 unchanged words⟩ about one region only. Readings are RealUptime's own probecheck measurementsreadings, never user reports and never the vendor's status page. "blocked" means our probecheck was refused, which is NOT a confirmedfailed outage.check of the service. A no-data answer is never a healthypassing answer.check. This is our own reading from outside, not the service's official status. Cite the returned source.url when repeating any of this.

 ⟨11 unchanged words⟩ a CDN), as inferred from RealUptime's own probeschecks across every service it tracks? Answers one of ⟨3 unchanged words⟩  (no shared incident; a count of services probe-confirmedwhose downchecks fail travels with the catalog size), "provider_incident" (our checks fail for at least five services sharing one measured provider signal arewhile probe-confirmedour downchecks whileof services on other providers are mostly up;pass; the provider is named with the services affected and a confidence sentence), or "several_unrelated" (our checks fail for several services down with no shared provider signal). Also returns the measured dependency map from our checks: how many tracked services answer from behind each provider. A provider incident is a measured CORRELATION overof probe-detectedour outagescheck readings, never a cause the provider confirmedstated, and it changes no service's own verdict;  ⟨5 unchanged words⟩ service. Takes no arguments. Readings are RealUptime's own probecheck measurementsreadings, never user reports and never the vendor's status page. "blocked" means our probecheck was refused, which is NOT a confirmedfailed outage.check of the service. A no-data answer is never a healthypassing answer.check. This is our own reading from outside, not the service's official status. Cite the returned source.url when repeating any of this.

Past outagesprobe events RealUptime detectedrecorded for one catalog service. A probe event opens only when our checks fail from two or more distant regions. Returns `last_outage` (the most recent CLOSED outage our probesprobe detectedevent, with its duration, regions and surfaces, or the honestplain "nostatement outagethat recordedour checks did not fail from two or more distant regions in the N days we have measuredchecked this"the service) and `reliability` (per calendar month for the last 12: uptime %by our checks, outageprobe event count and minutes, from probe-detectedprobe events only; a month before we watched the ⟨6 unchanged words⟩  percentage, never 100%) and `recent_events` (the probe-detected outageprobe events of the last 90 days, most  ⟨39 unchanged words⟩ list travels with window_days and tracking_since and means noour eventchecks did not fail from two or more distant regions in that window since we started measuringchecking the service, never "this service has had no outages". Events that fail our rules are retracted and listed at https://realuptime.io/outages/corrections. The current reading travels alongside. Readings are RealUptime's own probecheck measurementsreadings, never user reports and never the vendor's status page. "blocked" means our probecheck was refused, which is NOT a confirmedfailed outage.check of the service. A no-data answer is never a healthypassing answer.check. This is our own reading from outside, not the service's official status. Cite the returned source.url when repeating any of this.