H3XAOperational intelligence
Live analytical pictureEvidence before assessment
Stress score630–100
Confidence15%
TrajectorySTABLE
Statusactive
Explainable score

Stress score components

Anomaly magnitude100%
Breadth15%
Persistence100%
Corroboration0%
Baseline deviation99%
Confidence

Confidence factors

15%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations50%
statistical significance100%
Affected infrastructure

Scope

ASNs—
ServicesFacebook Messenger, Tor
RegionsUG
Started2026-08-11 15:35
Last observed2026-10-03 06:55
Evidence

Underlying observations

voidly-atlas
Internet connectivity disruption in Ugandaincident--588b5cba-7909-50b9-c84b-d1d439163d07
2026-08-11 15:35
voidly-atlas
Censorship detected in UGincident--6c049c4c-7f12-5f95-4994-286e035f585e
2026-08-27 00:00
voidly-atlas
Censorship detected in UGincident--8e3ce58c-c343-5862-2589-e02edfc5f0c5
2026-08-28 00:00
voidly-atlas
Censorship detected in UGincident--df704682-91d8-50c2-c18f-39726bf290c2
2026-08-29 00:00
voidly-atlas
Internet connectivity disruption in Ugandaincident--8ba905c5-30a6-5ece-2bec-5eb85ca5ae27
2026-09-23 00:10
voidly-atlas
Internet connectivity disruption in Ugandaincident--4759b0d8-f710-56a8-175a-1f5f516fd337
2026-09-24 12:45
voidly-atlas
Internet connectivity disruption in Ugandaincident--a7b23069-4994-5af1-de63-1a202115b5b0
2026-09-25 01:00
voidly-atlas
Censorship detected in UGincident--f4e845b9-c224-59e0-6caa-3939c59048e3
2026-09-26 00:00
voidly-atlas
Internet connectivity disruption in Ugandaincident--1d58bd9e-4438-5e8a-7a37-91e17a8aa600
2026-09-26 00:40
voidly-atlas
Censorship detected in UGincident--5e2cefcb-a066-5240-8fef-024deec22ca2
2026-09-27 00:00
voidly-atlas
Internet connectivity disruption in Ugandaincident--62e77442-a4a8-5f75-bd26-7c2b17a85ed6
2026-09-27 07:35
voidly-atlas
Censorship detected in UGincident--bbbc0a7e-6ea8-5ccc-8762-b1d4d7214047
2026-09-28 00:00
voidly-atlas
Internet connectivity disruption in Ugandaincident--6bb33560-155b-5d6f-a67c-6a429a77fe47
2026-09-28 11:20
voidly-atlas
Censorship detected in UGincident--7bc1ed37-02d8-5328-209a-fe41a4837f98
2026-09-29 00:00
voidly-atlas
Internet connectivity disruption in Ugandaincident--152d519e-849f-5e7a-2d14-3d5f4af57ccf
2026-09-29 12:55
voidly-atlas
Internet connectivity disruption in Ugandaincident--ecba06bb-056e-5d74-56da-73c8f9d04570
2026-09-30 05:05
voidly-atlas
Internet connectivity disruption in Ugandaincident--407157c8-1f01-55e3-8c27-bb36b4421fec
2026-10-01 11:40
voidly-atlas
Censorship detected in UGincident--784781f4-6094-5df9-4b96-1b31797540a4
2026-10-02 00:00
voidly-atlas
Internet connectivity disruption in Ugandaincident--de8dcfe8-f798-53c7-6d2d-b95709587590
2026-10-02 21:05
voidly-atlas
Internet connectivity disruption in Ugandaincident--964ce1e8-328b-53a1-b7f5-3432ecc8f8a5
2026-10-03 06:55
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.