H3XA — Operational Evidence

Stress score580–100

Confidence9%

TrajectoryRESOLVED

Statusresolved

Explainable score

Stress score components

Anomaly magnitude69%

Breadth46%

Persistence100%

Corroboration0%

Baseline deviation86%

Confidence

Confidence factors

method diversity25%

source agreement0%

timestamp overlap0%

infrastructure overlap0%

alternative explanations50%

statistical significance69%

Affected infrastructure

Scope

ASNsAS136255, AS136780

ServicesWeb connectivity, HTTPS, Facebook Messenger, Signal, Tor, WhatsApp, Facebook, Instagram, Proton VPN, ProtonVPN, Psiphon, Twitter/X, X, Telegram

RegionsMM

Started2026-08-10 00:00

Last observed2026-10-02 06:00

Evidence

Underlying observations

voidly-atlas

Military coup internet shutdownincident--1c807020-826a-5653-4c0f-34f52d59c5a5

2021-02-01 00:00 voidly-atlas

Military coup internet shutdownincident--85a56888-5723-5601-5422-215e6ec9a777

2021-02-11 00:00 voidly-atlas

Military coup internet shutdownincident--944ab97a-7061-5720-8a7e-d1b8f220bd5b

2021-02-23 00:00 voidly-atlas

Military coup internet shutdownincident--ec40f9ee-efdf-516a-9ead-6329c68b9e7f

2021-04-05 00:00 voidly-atlas

Military coup internet shutdownincident--b611d744-b220-54c7-55cc-0727f638459b

2021-04-26 00:00 voidly-atlas

Censorship detected in MMincident--964f19f9-bc3f-55de-48f4-500a9f52d89c

2026-08-10 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--0952472a-76ff-5b41-232d-3149861a7e1d

2026-08-10 00:30 voidly-atlas

Censorship detected in MMincident--b34841e9-7642-557e-1f51-cf23f7fd27e8

2026-08-11 00:00 voidly-atlas

Censorship detected in MMincident--818bb357-73ec-5a62-17a3-7f54637bc42d

2026-08-12 00:00 voidly-atlas

Censorship detected in MMincident--4228f28f-ad08-5643-643b-fb33fd0553c2

2026-08-27 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--9d4af227-80e3-5a56-00d5-130de813b062

2026-08-27 19:10 voidly-atlas

Censorship detected in MMincident--b4853142-e0f3-519d-bedd-c2f59509f4ca

2026-08-28 00:00 voidly-atlas

Censorship detected in MMincident--81e3ad2e-7f8e-5797-8305-8912955d7e39

2026-08-29 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--00471385-8302-5234-6260-7e67d77b93c6

2026-08-29 02:00 voidly-atlas

Censorship detected in MMincident--0c5879bc-217a-510d-fab4-be32a5644d0e

2026-09-23 00:00 voidly-atlas

Censorship detected in MMincident--4facea6b-a7ba-5204-b5f3-699938872245

2026-09-24 00:00 voidly-atlas

Censorship detected in MMincident--c70ed81a-7f35-5b7d-5f37-356051cd5a15

2026-09-25 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--2660c2ea-20c7-596d-2b10-f88dc420bf41

2026-09-25 20:50 voidly-atlas

Censorship detected in MMincident--0dd25b90-fc02-5771-f483-08ecd7cfe8bf

2026-09-26 00:00 voidly-atlas

Censorship detected in MMincident--988226f8-2c4d-565b-0f7a-19bd5cf8313a

2026-09-27 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--8fec32c3-056a-5798-0036-66bf26fe469b

2026-09-27 02:05 voidly-atlas

Censorship detected in MMincident--1e87d19b-d5cf-5447-1b71-3b71e376d3e2

2026-09-28 00:00 voidly-atlas

Censorship detected in MMincident--26c5ed4b-9961-5faa-4659-ff5af4f3cf93

2026-09-29 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--1de1c53d-9c46-5838-d62a-cc3a8578abc3

2026-09-29 12:45 voidly-atlas

Censorship detected in MMincident--5d9beee0-7408-5afe-33d0-76822d0a73dd

2026-09-30 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--4c452e1c-ab98-5378-ab1d-3a36b37e1f00

2026-09-30 09:45 voidly-atlas

Censorship detected in MMincident--c8439972-3de4-5494-b797-eea04d92e86a

2026-10-01 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--72353986-fa10-5a2c-1daf-6b8fa758dd4b

2026-10-01 01:05 voidly-atlas

Censorship detected in MMincident--9db46282-8554-5ca2-c16d-084b6441841d

2026-10-02 00:00 voidly-atlas

Internet connectivity disruption in Myanmarincident--c10fb098-3d62-5472-67fa-52a9ae6feabb

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