Infrastructure Stress Event · h3xa-derived
country ID · ID
Service blocking — derived from 1 independent signal across 13 observations.
Stress score580–100
Confidence15%
TrajectoryRESOLVED
Statusresolved
Explainable score
Stress score components
Anomaly magnitude100%
Breadth44%
Persistence100%
Corroboration0%
Baseline deviation27%
Confidence
Confidence factors
15%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations50%
statistical significance100%
Affected infrastructure
Scope
ASNsAS150509
ServicesChatGPT, Claude, Facebook, Gemini, Instagram, ProtonVPN, Signal, Telegram, TikTok, WhatsApp, X, YouTube
RegionsID
Started2026-08-12 16:40
Last observed2026-09-30 00:00
Evidence
Underlying observations
voidly-atlas
Internet connectivity disruption in Indonesiaincident--418e0788-04ef-5809-a435-8c966eddb0ad
voidly-atlasInternet connectivity disruption in Indonesiaincident--5e276c51-b4f2-519c-4071-4d324f46fb02
voidly-atlasInternet connectivity disruption in Indonesiaincident--0c860c14-ba31-5b86-ac24-7b45b0d4a72b
voidly-atlasInternet connectivity disruption in Indonesiaincident--092eacb4-ed4f-547f-9b1a-53440ec4b9b5
voidly-atlasInternet connectivity disruption in Indonesiaincident--7d6ab5ad-3baa-52da-0386-d18631dc8ad4
voidly-atlasInternet censorship detected in Indonesiaincident--0299a083-8e7f-56fd-c197-53a0987f4a4e
voidly-atlasInternet connectivity disruption in Indonesiaincident--5969ed8b-b532-58cb-c04a-0bbcb177a41a
voidly-atlasInternet connectivity disruption in Indonesiaincident--721487bd-d68e-526c-7eb5-f566e62f836a
voidly-atlasInternet connectivity disruption in Indonesiaincident--19f89ba0-bcca-5564-179f-6327fd100443
voidly-atlasInternet connectivity disruption in Indonesiaincident--e967aa90-cef7-5b46-9292-c754500406c4
voidly-atlasInternet connectivity disruption in Indonesiaincident--dc6b62e6-a1f2-509f-fdd4-27e3cef4eb73
voidly-atlasInternet connectivity disruption in Indonesiaincident--06a8b427-08e5-5e55-efbf-4b6afb9e0d96
voidly-atlasInternet censorship detected in Indonesiaincident--2e0cd2da-91ee-537c-b216-d808adbbedc0
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.