Infrastructure Stress Event · h3xa-derived
country EG · EG
Application restriction — derived from 1 independent signal across 25 observations.
Stress score420–100
Confidence0%
TrajectorySTABLE
Statusactive
Explainable score
Stress score components
Anomaly magnitude11%
Breadth44%
Persistence100%
Corroboration0%
Baseline deviation100%
Confidence
Confidence factors
0%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations60%
statistical significance11%
Affected infrastructure
Scope
ASNsAS8452
ServicesTor, ChatGPT, Claude, Facebook, Gemini, Instagram, ProtonVPN, Signal, Telegram, TikTok, WhatsApp, X, YouTube
RegionsEG
Started2026-08-10 00:00
Last observed2026-10-03 01:30
Evidence
Underlying observations
voidly-atlas
Censorship detected in EGincident--f00a3863-80fc-5384-c9c2-ca0be83857da
voidly-atlasInternet connectivity disruption in Egyptincident--1ebf8db6-dadf-5d7b-2cde-1f1b1ffd9683
voidly-atlasCensorship detected in EGincident--4acbfe53-c330-5859-fb11-b567255e155d
voidly-atlasInternet connectivity disruption in Egyptincident--bc18cfb5-6af7-5450-d7d8-712953fed0dc
voidly-atlasCensorship detected in EGincident--216db8ff-fd32-5e8a-45a6-a6c5f23b470f
voidly-atlasCensorship detected in EGincident--6953fe4f-f19c-5b7d-c7c5-24fcd123d8f5
voidly-atlasInternet connectivity disruption in Egyptincident--82adeb9c-fbba-59b7-500a-5ee8c406e211
voidly-atlasCensorship detected in EGincident--ad6aa747-cfd6-5671-2bb3-a314598a1fee
voidly-atlasInternet connectivity disruption in Egyptincident--d27499c2-b7a5-5e06-2b3c-275cbfc5e871
voidly-atlasCensorship detected in EGincident--5ed0bf8c-c0e1-529a-3610-a837310de139
voidly-atlasCensorship detected in EGincident--95cc63d4-3654-5032-b92b-15c3c589edb7
voidly-atlasInternet connectivity disruption in Egyptincident--5fa3516c-7e92-52ee-dd14-bcab7994a7ec
voidly-atlasCensorship detected in EGincident--1da74c60-f3c4-5625-39ea-4773bb3cbae7
voidly-atlasInternet connectivity disruption in Egyptincident--1265e785-cda6-5f10-5081-b5d7944b9b09
voidly-atlasCensorship detected in EGincident--e8eae31e-e2c6-5422-b12d-6130d3f7675e
voidly-atlasCensorship detected in EGincident--859e1870-a7f9-5421-9a05-4a59f94915da
voidly-atlasInternet connectivity disruption in Egyptincident--f09aff77-fffc-58cb-193e-e88f4c41815e
voidly-atlasCensorship detected in EGincident--5328b7f1-5eee-5e8d-fc43-9ae6f65ed87c
voidly-atlasCensorship detected in EGincident--0f5cea32-2b99-5918-bee3-7e865a4c3758
voidly-atlasCensorship detected in EGincident--7b746771-f83e-575e-1a5c-2cd3db2ee9e5
voidly-atlasCensorship detected in EGincident--f9561edc-bc54-5a7a-3021-c11a8e55279f
voidly-atlasInternet connectivity disruption in Egyptincident--577aa971-afcc-5a77-cb92-af750b34cdff
voidly-atlasCensorship detected in EGincident--68438a5f-b900-5706-1284-0e38f2b11174
voidly-atlasCensorship detected in EGincident--317d5ff7-4f0f-54ce-83a2-8ef9caab8ba6
voidly-atlasInternet connectivity disruption in Egyptincident--ada37f80-6969-54fd-f78f-ceb023c42aeb
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.