H3XA — Operational Evidence

Stress score540–100

Confidence15%

TrajectorySTABLE

Statusactive

Explainable score

Stress score components

Anomaly magnitude100%

Breadth46%

Persistence100%

Corroboration0%

Baseline deviation1%

Confidence

Confidence factors

15%

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance100%

Affected infrastructure

Scope

ASNsAS55828, AS135411

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

RegionsBD

Started2026-08-10 01:45

Last observed2026-10-03 11:05

Evidence

Underlying observations

voidly-atlas

Internet connectivity disruption in Bangladeshincident--59e636dc-c21d-56c2-7300-1b7b3c18d3f0

2026-08-10 01:45 voidly-atlas

Internet connectivity disruption in Bangladeshincident--64dbdfb4-0ea0-52a6-f34f-791ba58b36af

2026-08-11 00:50 voidly-atlas

Internet connectivity disruption in Bangladeshincident--b12bc44a-72fb-5e25-c5b4-e807e6600b53

2026-08-12 01:20 voidly-atlas

Internet connectivity disruption in Bangladeshincident--cf0e5195-cc69-517a-6831-c3b6a7c93347

2026-08-27 08:00 voidly-atlas

Internet connectivity disruption in Bangladeshincident--9810bf87-8366-5608-0cf3-93e6ec5b9871

2026-08-28 20:10 voidly-atlas

Internet connectivity disruption in Bangladeshincident--1402d554-b142-561d-7eef-071a3a2e5c9d

2026-08-29 11:35 voidly-atlas

Internet connectivity disruption in Bangladeshincident--53afa868-d0db-5be4-3a69-c8771c26dcce

2026-08-30 05:50 voidly-atlas

Internet connectivity disruption in Bangladeshincident--4688f528-6900-512c-8b41-aa331bc1da91

2026-09-23 05:45 voidly-atlas

Internet censorship detected in Bangladeshincident--9b7202a2-dd1d-5170-822e-b6799cdcb5c3

2026-09-24 00:00 voidly-atlas

Internet connectivity disruption in Bangladeshincident--7207d7c2-45cb-50b7-4a8c-8e48f4a6065d

2026-09-26 06:45 voidly-atlas

Internet connectivity disruption in Bangladeshincident--67c30bc3-622b-5a21-1344-06cd299e93f0

2026-09-27 02:45 voidly-atlas

Internet connectivity disruption in Bangladeshincident--a15a9573-45ff-5bd0-c8e6-43b20cb2f3d1

2026-09-28 10:40 voidly-atlas

Internet connectivity disruption in Bangladeshincident--30c53b0a-ee87-5f78-50cf-d22c0c0facb4

2026-09-29 02:25 voidly-atlas

Internet connectivity disruption in Bangladeshincident--a8e155b0-5fde-5a57-7d99-4d11c4664585

2026-09-30 02:10 voidly-atlas

Internet connectivity disruption in Bangladeshincident--e5f7001d-2439-5696-5d5e-c915d7fc64f1

2026-10-01 08:15 voidly-atlas

Internet connectivity disruption in Bangladeshincident--8063bb39-9060-5932-13a6-d2b0b1d77612

2026-10-03 11:05

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.