H3XA — Operational Evidence

Stress score380–100

Confidence5%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude48%

Breadth44%

Persistence100%

Corroboration0%

Baseline deviation2%

Confidence

Confidence factors

5%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance48%

Affected infrastructure

Scope

ASNsAS210574

ServicesChatGPT, Claude, Facebook, Gemini, Instagram, ProtonVPN, Signal, Telegram, TikTok, WhatsApp, X, YouTube

RegionsTR

Started2026-08-12 14:20

Last observed2026-09-30 00:00

Evidence

Underlying observations

Internet connectivity disruption in Turkeyincident--b68d1e59-a66f-5e1d-7887-1b37f6ef2b2f

2026-08-12 14:20 voidly-atlas

Internet censorship detected in Turkeyincident--da8aeddc-d2ac-5e95-def8-76f1cf2a80be

2026-09-23 00:00 voidly-atlas

Internet connectivity disruption in Turkeyincident--eca47b4e-c4b4-54e6-de71-517b63fef51e

2026-09-25 11:40 voidly-atlas

Internet censorship detected in Turkeyincident--feb6cf4b-593a-5262-d921-88e942a520a2

2026-09-27 00:00 voidly-atlas

Internet connectivity disruption in Turkeyincident--4a91170f-52e3-54ef-5959-9d5e79edd749

2026-09-29 12:45 voidly-atlas

Internet censorship detected in Turkeyincident--50b43442-b165-5f68-968a-67c1da8f9a96

2026-09-30 00:00

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.