H3XA — Operational Evidence

Stress score660–100

Confidence15%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude100%

Breadth44%

Persistence100%

Corroboration0%

Baseline deviation84%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNsAS8048

ServicesSignal, ChatGPT, Claude, Facebook, Gemini, Instagram, ProtonVPN, Telegram, TikTok, WhatsApp, X, YouTube

RegionsVE

Started2026-08-10 00:00

Last observed2026-10-03 00:10

Evidence

Underlying observations

Censorship detected in VEincident--b2b00369-7de0-57c2-112e-3aa3ef7a9693

2026-08-10 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--8f2d65bb-d883-590b-6864-e3acead2a9c7

2026-08-10 01:30 voidly-atlas

Censorship detected in VEincident--50dd9e45-c6b7-56fd-55db-6de5cf25f8f8

2026-08-11 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--4ef8b1c4-63fe-5d7e-aa83-dc0da77a4908

2026-08-11 15:20 voidly-atlas

Internet connectivity disruption in Venezuelaincident--f855c49d-873b-56cb-2f86-bf788003b8d6

2026-08-12 00:00 voidly-atlas

Censorship detected in VEincident--d8587274-408c-5528-1585-716415ad9248

2026-08-12 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--d10fdec8-f923-50b2-4dda-66a01d3e3a1b

2026-08-13 13:50 voidly-atlas

Censorship detected in VEincident--524c85c7-c945-57b9-f29f-24660c4a9456

2026-08-27 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--90c44b81-51ad-502a-4053-3b03f8b5ab44

2026-08-27 05:20 voidly-atlas

Censorship detected in VEincident--04d55020-71b9-541d-0b2f-026ae8b53a8e

2026-08-28 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--41514bcc-c9f8-51b6-4c58-fc774b3ecfbe

2026-08-28 13:05 voidly-atlas

Censorship detected in VEincident--11cad668-9da6-5774-1ed2-422da066d0c9

2026-08-29 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--c33ad734-30a2-5b24-880c-aff6a97540fc

2026-08-29 02:40 voidly-atlas

Internet connectivity disruption in Venezuelaincident--5215b84b-aeba-56e8-6e08-47e1679e5a55

2026-08-30 00:30 voidly-atlas

Censorship detected in VEincident--e616f284-f363-548f-6b6e-1b53b126b65e

2026-09-23 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--1a4c9df3-c4bb-507b-d7f9-69dd43455bf4

2026-09-23 00:10 voidly-atlas

Censorship detected in VEincident--eabdca52-8aa4-5277-7684-b2477e231f04

2026-09-24 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--cade82dc-b089-589b-af6b-0de5d334b7da

2026-09-24 00:30 voidly-atlas

Internet connectivity disruption in Venezuelaincident--609cccf1-9555-5043-c846-bf9e21cdfb2b

2026-09-25 13:20 voidly-atlas

Internet connectivity disruption in Venezuelaincident--936941d3-473f-5283-dbeb-7596ce5ab0df

2026-09-26 00:50 voidly-atlas

Internet connectivity disruption in Venezuelaincident--09183090-3572-533f-1371-d9c1098cdfd1

2026-09-27 00:10 voidly-atlas

Internet connectivity disruption in Venezuelaincident--c3836c25-5aa5-5e34-48f9-3cb7925a4d76

2026-09-28 11:30 voidly-atlas

Internet connectivity disruption in Venezuelaincident--1581d28e-7a85-5223-351a-1d4ed693b8a1

2026-09-29 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--07d191f1-7595-5b75-0c34-7f1f28cea851

2026-09-30 01:10 voidly-atlas

Internet connectivity disruption in Venezuelaincident--29260757-e3ad-54a3-c5dc-7011ca597621

2026-10-01 00:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--bf3bb5c8-096a-52ad-7082-83cebc317cbc

2026-10-02 04:00 voidly-atlas

Internet connectivity disruption in Venezuelaincident--1edd9ff1-5865-5419-0e81-321920318ee9

2026-10-03 00:10

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.