Infrastructure Stress Event · h3xa-derived
country AZ · AZ
Application restriction — derived from 1 independent signal across 24 observations.
Stress score390–100
Confidence0%
TrajectoryRESOLVED
Statusresolved
Explainable score
Stress score components
Anomaly magnitude0%
Breadth46%
Persistence100%
Corroboration0%
Baseline deviation100%
Confidence
Confidence factors
0%
method diversity25%
source agreement0%
timestamp overlap0%
infrastructure overlap0%
alternative explanations60%
statistical significance0%
Affected infrastructure
Scope
ASNsAS29049, AS48830
ServicesTor, Proton VPN, ProtonVPN, Facebook, Instagram, Signal, TikTok
RegionsAZ
Started2026-08-10 00:00
Last observed2026-10-02 23:35
Evidence
Underlying observations
voidly-atlas
Censorship detected in AZincident--e277521e-6367-5c04-8051-709d15ea678f
voidly-atlasCensorship detected in AZincident--69270daa-cba1-54d2-967d-d2f5f8ed3cfd
voidly-atlasCensorship detected in AZincident--8b930dfe-c39a-52ed-b182-8588ae0facf4
voidly-atlasInternet connectivity disruption in Azerbaijanincident--b50aa748-6495-5601-acad-db67ad891e54
voidly-atlasInternet connectivity disruption in Azerbaijanincident--437ba0e1-cc8f-59d7-bef9-34522f9247ca
voidly-atlasCensorship detected in AZincident--1c4737cb-cb58-53af-ebd5-9913e3002428
voidly-atlasCensorship detected in AZincident--2e551f29-aacd-5b3a-4fdd-9f7739e73828
voidly-atlasInternet connectivity disruption in Azerbaijanincident--5be07e32-b889-5fbc-0197-65e95bf6df44
voidly-atlasCensorship detected in AZincident--c6ed2d8b-2ca3-5db7-0e5e-7f81b04ee3e9
voidly-atlasInternet connectivity disruption in Azerbaijanincident--3b1ff884-3cfe-5663-d523-feefa8d4cf59
voidly-atlasCensorship detected in AZincident--d3380cab-66ef-5633-b695-1342202c25b4
voidly-atlasInternet censorship detected in Azerbaijanincident--0dffa7a8-e237-542e-9b6e-a4e03c6cc568
voidly-atlasCensorship detected in AZincident--4e9a78b7-8271-5fc3-9fb8-1980d4977132
voidly-atlasCensorship detected in AZincident--7052343c-46c5-5257-c735-bba380159819
voidly-atlasCensorship detected in AZincident--e74ecdb9-3ef7-5b27-544d-7ce68947542f
voidly-atlasCensorship detected in AZincident--65696c89-c801-528e-424f-5960fe7a790b
voidly-atlasCensorship detected in AZincident--a2b7630c-169c-519a-59f0-28e0e0099e06
voidly-atlasCensorship detected in AZincident--650e4ac8-3bed-5baf-d9c2-f0735a923dda
voidly-atlasCensorship detected in AZincident--a4b1099a-41f6-5810-473f-183b49c58e0a
voidly-atlasInternet connectivity disruption in Azerbaijanincident--77ceefe1-9206-5270-576b-85fa392d0d5b
voidly-atlasCensorship detected in AZincident--2da58485-01ec-5605-b8b8-f6acbdf8c336
voidly-atlasInternet connectivity disruption in Azerbaijanincident--3aae3c13-7979-51b2-ed1a-5d29d96023f4
voidly-atlasCensorship detected in AZincident--d59288a0-5dc3-5e13-8833-cf9779054d5c
voidly-atlasInternet connectivity disruption in Azerbaijanincident--844e6463-0d26-59ce-abad-1300e0894c5c
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.