Incident index
Follow the record.
Documented censorship and network disruption.
Find an event. Follow its evidence. Cite the source.
One mark per returned record. This is a page breakdown, not a global trend.
TZ · selected country
158 matching records
Source generated
Filters are saved in the URL. Type, severity and status are separate fields from the source.
- TZ-2026-0019
- Type
- censorship
- Status
- suspected
- Mechanism
- Connection timeout / throttling
- TZ-2026-0018
- Type
- censorship
- Status
- suspected
- Mechanism
- Connection timeout / throttling
- TZ-2026-0017
- Type
- censorship
- Status
- suspected
- Mechanism
- DNS blocking
- TZ-2026-0016
- Type
- censorship
- Status
- suspected
- Mechanism
- Connection timeout / throttling
- TZ-2026-0003
- Type
- disruption
- Status
- active
- Mechanism
- Infrastructure outage
- TZ-2025-0002
- Type
- censorship
- Status
- active
- Mechanism
- Connection timeout / throttling
- TZ-2020-0005
- Type
- censorship
- Status
- confirmed
- Mechanism
- dns-blocking
- TZ-2020-0001
- Type
- censorship
- Status
- confirmed
- Mechanism
- Not specified
Keep the source attached.
Open data & exportsDates, classifications and reuse
Observation dates belong to each source record. Source-generation time is when the API assembled its response; it does not mean that every listed event is recent or still occurring. This page requests the source when loaded and does not continuously refresh.
“Censorship,” “disruption,” status and mechanism are source classifications. A network disruption alone does not establish intentional censorship. Check evidence, coverage and attribution before drawing conclusions.
Voidly-original incidents and annotations are CC BY 4.0. Upstream measurements retain their own licenses. Use the canonical incident URL, observation date and source when citing; each detail page provides citation downloads.
Dataset version: 2026.11.07. Page source check: .
Check measurement quality