H3XAOperational intelligence
Live analytical pictureEvidence before assessment
Stress score370–100
Confidence1%
TrajectoryRESOLVED
Statusresolved
Explainable score

Stress score components

Anomaly magnitude31%
Breadth15%
Persistence100%
Corroboration0%
Baseline deviation64%
Confidence

Confidence factors

1%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations50%
statistical significance31%
Affected infrastructure

Scope

ASNs—
ServicesFacebook Messenger, Signal
RegionsET
Started2026-08-10 16:50
Last observed2026-10-02 08:15
Evidence

Underlying observations

voidly-atlas
Internet connectivity disruption in Ethiopiaincident--ff7031fc-9bef-54d6-8644-666c6db0e04a
2026-08-10 16:50
voidly-atlas
Internet connectivity disruption in Ethiopiaincident--d32b6c4f-760a-5b27-9792-f8663ee58ace
2026-08-11 04:05
voidly-atlas
Internet connectivity disruption in Ethiopiaincident--02fc7c1b-a85b-5ecf-d7bb-0e7f94fdfda8
2026-08-13 12:20
voidly-atlas
Censorship detected in ETincident--19d1f166-f3ae-50b7-bb08-0b8a88a960b6
2026-08-27 00:00
voidly-atlas
Censorship detected in ETincident--ff2a45c7-26d7-5b9d-54c1-4ffbd95928a2
2026-08-28 00:00
voidly-atlas
Censorship detected in ETincident--2206fb19-087b-5450-a141-6a102c1dd870
2026-08-29 00:00
voidly-atlas
Internet connectivity disruption in Ethiopiaincident--95f98d32-00a3-54f4-e57e-2498f4423513
2026-08-29 06:55
voidly-atlas
Internet connectivity disruption in Ethiopiaincident--20c77cb1-d1d1-52b9-bce9-cd22f73affc2
2026-08-30 05:35
voidly-atlas
Censorship detected in ETincident--c3dfa98a-18b8-55b1-c7c0-91daf82d4527
2026-09-23 00:00
voidly-atlas
Censorship detected in ETincident--91321371-4f08-5e6a-c1a4-a66756c5b9ff
2026-09-24 00:00
voidly-atlas
Internet connectivity disruption in Ethiopiaincident--8f3afcff-67ea-595d-7cc5-c11839a9b11e
2026-09-24 08:50
voidly-atlas
Censorship detected in ETincident--032ba3a3-2491-5985-4c5d-c187f34a13b3
2026-09-25 00:00
voidly-atlas
Censorship detected in ETincident--eada65fe-bfc6-5aa2-df9a-127bd10e843d
2026-09-26 00:00
voidly-atlas
Censorship detected in ETincident--79a47191-5ab5-58c3-78fa-351b8e3e8bc9
2026-09-27 00:00
voidly-atlas
Censorship detected in ETincident--3c740268-64d4-5d0f-4d19-b144833bd0db
2026-09-28 00:00
voidly-atlas
Internet connectivity disruption in Ethiopiaincident--c5f05cbc-5b9c-5afa-df2f-9120c3103157
2026-09-28 04:15
voidly-atlas
Censorship detected in ETincident--b932a7d1-558f-555e-5a50-32e5080faba7
2026-09-29 00:00
voidly-atlas
Censorship detected in ETincident--20609fc2-f708-57c1-1ebb-6acdccc73de3
2026-09-30 00:00
voidly-atlas
Censorship detected in ETincident--ec5c60b6-f4e8-54c0-b42e-3701c3e19617
2026-10-01 00:00
voidly-atlas
Internet connectivity disruption in Ethiopiaincident--0c61cb36-3672-5d96-3787-659e3a605114
2026-10-01 07:05
voidly-atlas
Censorship detected in ETincident--14d8ca6e-901f-58bc-6f87-b25c2edc6706
2026-10-02 00:00
voidly-atlas
Internet connectivity disruption in Ethiopiaincident--f7018bdc-490f-5db6-9cec-f47237ccf055
2026-10-02 08:15
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.