H3XA — Operational Evidence

Stress score690–100

Confidence15%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude100%

Breadth44%

Persistence100%

Corroboration0%

Baseline deviation100%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNsAS15802

ServicesTor, Signal, WhatsApp, BBC, ChatGPT, Claude, Facebook, Gemini, Instagram, Lantern, Medium, New York Times, Proton VPN, ProtonVPN, Psiphon, Telegram, The Guardian, TikTok, Twitter/X, X, YouTube

RegionsAE

Started2026-08-10 00:00

Last observed2026-10-02 00:00

Evidence

Underlying observations

voidly-atlas

Censorship detected in AEincident--8c92f272-eb3e-5e4d-bd92-5c2491d533b0

2026-08-10 00:00 voidly-atlas

Censorship detected in AEincident--0719a9a0-028d-54e4-6c65-a58cb9645e5b

2026-08-11 00:00 voidly-atlas

Internet censorship detected in UAEincident--f73a0b78-fd5f-5117-dd59-cc8181701f20

2026-08-12 00:00 voidly-atlas

Censorship detected in AEincident--a28a76e9-3cda-57ce-3c35-72df423b4cb9

2026-08-12 00:00 voidly-atlas

Censorship detected in AEincident--eb330e34-78f2-5d1a-daa5-18072dd3590b

2026-08-27 00:00 voidly-atlas

Censorship detected in AEincident--0d5404d4-0c07-58b2-b0d6-83ca9b545e09

2026-08-28 00:00 voidly-atlas

Censorship detected in AEincident--89979e7a-97f8-5e88-1b44-04785c5a429d

2026-08-29 00:00 voidly-atlas

Censorship detected in AEincident--4bc585bb-fefc-572d-a544-5925fdd74b65

2026-09-23 00:00 voidly-atlas

Internet connectivity disruption in UAEincident--df9d2d7d-fa12-5d3e-aa10-cc3a14af1c03

2026-09-23 20:30 voidly-atlas

Censorship detected in AEincident--9e41547e-24e1-5f24-c9ed-ccf68164159d

2026-09-24 00:00 voidly-atlas

Censorship detected in AEincident--eaad64a3-e394-55d6-5753-01b50ffde7fa

2026-09-25 00:00 voidly-atlas

Censorship detected in AEincident--bde4c525-4409-5261-e9ac-569805da2737

2026-09-26 00:00 voidly-atlas

Censorship detected in AEincident--3827e191-7378-56b1-c143-591f190610f0

2026-09-27 00:00 voidly-atlas

Censorship detected in AEincident--0351b67a-a07a-5cfa-8833-be44c2bb37a6

2026-09-28 00:00 voidly-atlas

Censorship detected in AEincident--d4bffc63-94f6-5632-f013-f08a14e8cbdb

2026-09-29 00:00 voidly-atlas

Censorship detected in AEincident--d0372c6f-f1bf-5759-f940-d0792c9d44ed

2026-09-30 00:00 voidly-atlas

Internet censorship detected in UAEincident--a7b26ca2-09c3-5aed-22c1-86114a5cbd69

2026-09-30 00:00 voidly-atlas

Censorship detected in AEincident--8f1a527f-8e27-59c3-e89f-690d7e4643f6

2026-10-01 00:00 voidly-atlas

Censorship detected in AEincident--6260ce06-b356-5839-e978-1b6877619a07

2026-10-02 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.