Relay service A*
Suspected · Single source · anonymizedSuspected
Corroborating
Warning
Recovered
The timeline below is a synthetic UI sample (not a real entry), illustrating the four-state card layout.
Risk watch · neutral aggregation
Third-Party Node Risk Watch
Aggregation and relay of public community feedback only: every entry links to the original source; nothing here is a factual finding or purchase advice.
⚖ Legal notice and correction policy
Content is aggregated and relayed from public communities and is not independently verified by this site; it is not an accusation against any party named. Single-source reports are always anonymized. If you believe an entry is inaccurate, correct it at the original source — this page syncs the status on the next data refresh. No commercial promotion link is ever allowed on this page (enforced by a build-time assertion).
Corrections (correction matters only): OPS1985OS@protonmail.com
Four-state machine
Four-state machine
SuspectedSingle source · anonymized
CorroboratingCross-source corroborated
WarningConcrete evidence of exit/failure
RecoveredNo new complaints in 30 days
Current entries
Watcher running: no entry passes the publish bar yetUntil original thread, cross-source corroboration and severity are all satisfied, this page stays empty — we never publish unverified accusations.
UI sample · synthetic
Publishing rules (red lines)
- Every entry links to the original public thread; wording is limited to suspected / user-reported / pending verification.
- Suspected and corroborating stages stay anonymized (e.g. "Relay service A*"); a real name appears only from the Warning stage onward, and only with two or more distinct sources.
- Zero commercial links and zero referral parameters on this page; a build-time scan fails the build otherwise.