TrustedStatus Sentinel

How it works

Sentinel publishes a simple, factual status for common services based on independent, automated probes from a regional node. The goal is clarity: a calm answer to “is this a real issue, or just me?”

What “independent verification” means

Sentinel doesn’t rely on user reports, social media, or manual updates. Instead, it runs lightweight automated checks from a regional probe node and publishes the observed results.

What we measure

  • Front-door reachability: whether the service responds to requests from the UK node.
  • Degradation signals: repeated indicators like rate limiting (HTTP 429), partial impairment, or vendor incident signals (where applicable).
  • Consistency over time: Sentinel uses consecutive-run validation to avoid “flapping” caused by momentary blips.

Consecutive-run validation (anti-flap)

Sentinel runs checks every minute and requires repeated evidence before changing status. This reduces false alarms from short, transient issues.

  • Degraded: requires consecutive degraded evidence (typically 2 runs).
  • Outage: requires consecutive unreachable evidence (typically 3 runs).
  • Recovery: requires consecutive healthy evidence (to avoid bouncing).

How we treat HTTP 4xx (including 429)

A 4xx response usually proves the service is reachable, even if access is blocked or rate-limited. Sentinel treats these as reachability-positive signals.

  • HTTP 429 (Too Many Requests): treated as reachable. If it repeats across consecutive runs, the service may be marked Degraded.
  • 4xx never triggers Outage: Outage is reserved for true unreachability (timeouts, connection failures, DNS/TLS errors).

What we don’t claim

  • This does not guarantee message delivery, call quality, or every feature working end-to-end.
  • This is not a mirror of vendor incident declarations. Vendors can report issues that don’t affect all users, and vice versa.

Status definitions

Operational
The service is responding normally from the UK node based on repeated checks.
Degraded
The service is reachable but appears impaired (for example: rate limiting, partial disruption, or repeated errors) from the UK node.
Outage
The service is not reachable from the UK node based on repeated checks (timeouts or connection failures).

Limitations

  • Internet routing and regional infrastructure can vary. A problem in one area may not affect everyone.
  • This is currently a UK node view. Other nodes may be added later.
  • Automated checks are designed to be lightweight and respectful of services.