H3XA — Operational Evidence

Stress score380–100

Confidence0%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude24%

Breadth2%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

0%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations60%

statistical significance24%

Affected infrastructure

Scope

ASNs—

Services—

RegionsTN

Started2026-08-10 00:00

Last observed2026-08-29 11:10

Evidence

Underlying observations

Censorship detected in TNincident--d05fa1fb-7386-5523-e40c-1ad690ea2e7e

2026-08-10 00:00 voidly-atlas

Censorship detected in TNincident--67f8fd76-8ae2-5c41-f8b3-b6a10cdb2824

2026-08-12 00:00 voidly-atlas

Internet connectivity disruption in Tunisiaincident--d0dc148d-1ba7-5ef7-33df-af0e187bebce

2026-08-26 13:50 voidly-atlas

Internet connectivity disruption in Tunisiaincident--ad84f987-19a5-5997-87c7-cf5decc776df

2026-08-27 13:10 voidly-atlas

Internet connectivity disruption in Tunisiaincident--139de2b6-5651-57f8-4c1d-ce76bdf2e0fc

2026-08-28 11:50 voidly-atlas

Internet connectivity disruption in Tunisiaincident--070b95e5-e87e-558d-e0c2-d4041dcc1579

2026-08-29 11:10

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.