H3XA — Operational Evidence

Stress score610–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude100%

Breadth22%

Persistence100%

Corroboration0%

Baseline deviation76%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNs—

ServicesFacebook Messenger, Tor, WhatsApp

RegionsHK

Started2026-08-11 17:10

Last observed2026-10-01 23:30

Evidence

Underlying observations

Internet connectivity disruption in Hong Kongincident--26d22ddf-227e-54cc-da24-058df8a5d6b7

2026-08-11 17:10 voidly-atlas

Internet connectivity disruption in Hong Kongincident--744e3070-5d60-55ee-af66-00a2dbe4ce26

2026-08-13 10:01 voidly-atlas

Internet connectivity disruption in Hong Kongincident--5b853d2e-1866-5055-ff97-97f58671d3a7

2026-08-26 18:20 voidly-atlas

Internet connectivity disruption in Hong Kongincident--0f6f9df9-7e7b-5dbd-ba10-3a4bc9a34e6c

2026-08-27 01:00 voidly-atlas

Censorship detected in HKincident--d4c74a99-fb92-5d6e-0cdd-15fb2d4e33d1

2026-08-28 00:00 voidly-atlas

Internet connectivity disruption in Hong Kongincident--19f40118-ea43-52dd-144d-cbe645aaedbe

2026-08-28 00:30 voidly-atlas

Internet connectivity disruption in Hong Kongincident--03ded034-8e07-5f4c-4c07-9e9c172afcfa

2026-08-29 00:30 voidly-atlas

Internet connectivity disruption in Hong Kongincident--24f4c1e0-110f-5193-9a62-e0e4041c4c8d

2026-08-30 01:30 voidly-atlas

Censorship detected in HKincident--f795d320-3c74-5170-d5d1-5e11590e50bb

2026-09-26 00:00 voidly-atlas

Censorship detected in HKincident--b2a348d5-24af-5189-d679-ac0ce592e2cd

2026-09-27 00:00 voidly-atlas

Censorship detected in HKincident--151ee704-80bd-507f-3135-cb364bf0302d

2026-09-28 00:00 voidly-atlas

Internet connectivity disruption in Hong Kongincident--edb0250c-1ee4-54ae-7467-83e70de25b73

2026-09-30 05:02 voidly-atlas

Internet connectivity disruption in Hong Kongincident--320c582b-5d91-5098-1243-4e4a2c76b400

2026-10-01 23:30

Alternative explanations

What else could this be?

single-source signal
insufficient corroboration

Provenance

Ownership boundary

This event is an h3xa-derived analytical product. The evidence references above point to source-owned STIX observations; h3xa claims no ownership of the underlying data.