Infrastructure Stress Event · h3xa-derived
country VE · VE
Service blocking — derived from 1 independent signal across 12 observations.
Stress score590–100
Confidence15%
TrajectorySTABLE
Statusactive
Explainable score
Stress score components
Anomaly magnitude100%
Breadth9%
Persistence100%
Corroboration0%
Baseline deviation84%
Confidence
Confidence factors
15%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations50%
statistical significance100%
Affected infrastructure
Scope
ASNs—
ServicesSignal
RegionsVE
Started2026-08-10 00:00
Last observed2026-08-29 02:40
Evidence
Underlying observations
voidly-atlas
Censorship detected in VEincident--b2b00369-7de0-57c2-112e-3aa3ef7a9693
voidly-atlasInternet connectivity disruption in Venezuelaincident--8f2d65bb-d883-590b-6864-e3acead2a9c7
voidly-atlasCensorship detected in VEincident--50dd9e45-c6b7-56fd-55db-6de5cf25f8f8
voidly-atlasInternet connectivity disruption in Venezuelaincident--4ef8b1c4-63fe-5d7e-aa83-dc0da77a4908
voidly-atlasInternet connectivity disruption in Venezuelaincident--f855c49d-873b-56cb-2f86-bf788003b8d6
voidly-atlasCensorship detected in VEincident--d8587274-408c-5528-1585-716415ad9248
voidly-atlasInternet connectivity disruption in Venezuelaincident--d10fdec8-f923-50b2-4dda-66a01d3e3a1b
voidly-atlasCensorship detected in VEincident--524c85c7-c945-57b9-f29f-24660c4a9456
voidly-atlasInternet connectivity disruption in Venezuelaincident--90c44b81-51ad-502a-4053-3b03f8b5ab44
voidly-atlasCensorship detected in VEincident--04d55020-71b9-541d-0b2f-026ae8b53a8e
voidly-atlasInternet connectivity disruption in Venezuelaincident--41514bcc-c9f8-51b6-4c58-fc774b3ecfbe
voidly-atlasInternet connectivity disruption in Venezuelaincident--c33ad734-30a2-5b24-880c-aff6a97540fc
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.