Infrastructure Stress Event · h3xa-derived
country KH · KH
Application restriction — derived from 1 independent signal across 12 observations.
Stress score370–100
Confidence0%
TrajectoryRESOLVED
Statusresolved
Explainable score
Stress score components
Anomaly magnitude25%
Breadth37%
Persistence100%
Corroboration0%
Baseline deviation50%
Confidence
Confidence factors
0%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations60%
statistical significance25%
Affected infrastructure
Scope
ASNsAS147011
ServicesFacebook Messenger, Signal, Tor, WhatsApp, Telegram
RegionsKH
Started2026-08-10 00:00
Last observed2026-10-02 18:10
Evidence
Underlying observations
voidly-atlas
Censorship detected in KHincident--3d6c9f8d-90b4-5ffe-c5d8-6e56a455aa0f
voidly-atlasCensorship detected in KHincident--08dfd2d2-81c9-507d-0aed-11942c3dc002
voidly-atlasCensorship detected in KHincident--41a59ab2-48c9-5679-abf9-49218eb08515
voidly-atlasInternet censorship detected in Cambodiaincident--c880da4a-2228-5361-1494-54ee1b4253c6
voidly-atlasCensorship detected in KHincident--0137ffff-2c54-5725-1aa0-5b30a22c5864
voidly-atlasCensorship detected in KHincident--b56b4ee5-803a-5c32-c4a3-3ca18ac26d24
voidly-atlasCensorship detected in KHincident--abba48ba-dbb2-5cfa-d62b-a7deee06490c
voidly-atlasCensorship detected in KHincident--8eb1a6a0-3efb-5ece-05dc-e68004c1f11a
voidly-atlasInternet connectivity disruption in Cambodiaincident--83bcdfc2-ca52-5349-b2f8-645d0ecdeeea
voidly-atlasCensorship detected in KHincident--9013f304-fe91-5bfe-2faf-b57e90d5d7a5
voidly-atlasCensorship detected in KHincident--6aa7c7cf-cb3d-5ac9-54c0-6a863a924bcd
voidly-atlasInternet connectivity disruption in Cambodiaincident--bbb43784-ac8b-5439-8c04-af1e84031d13
Alternative explanations
What else could this be?
- single-source signal
- low statistical significance
- 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.