| Component | Value | Weight | Points |
|---|---|---|---|
| Anomaly | 0.00 | 0.00 | 0.0 |
| Breadth | 0.00 | 0.00 | 0.0 |
| Persistence | 0.00 | 0.00 | 0.0 |
| Corroboration | 0.00 | 0.00 | 0.0 |
| Baseline deviation | 0.00 | 0.00 | 0.0 |
Readings
Internet disruption in UZ
The derived record for August 2026: episodes in that window, the score, and public reporting from the same dates.
Stress60latest episode in this window
Episodes1
ClassService Blocking
Modelh3xa-iss-1.1
Record
Episode starts
Each mark is an episode start. Situation stress 60 follows the active episode, or the latest episode when every episode is resolved. Source: this situation's briefing pack, from the first episode start through the latest.
- country UZ · SERVICE_BLOCKING · stress 60
Score
How the stress points are made
Points = weight × component × 100, on a 0–100 track. Model h3xa-iss-1.1. Source: the latest derivation stored for each episode.
- Anomaly
- Breadth
- Persistence
- Corroboration
- Baseline deviation
Provenance
Observation to derivation
Each episode cites the source observation and the derivation that scored it. Situation sit-dec0fb287b4987e7901e1c78.
Observation
Internet censorship detected in Uzbekistanvoidly-atlas · 36531f539b24
Censorship detected in UZvoidly-atlas · 9827a4b8d5ec
Censorship detected in UZvoidly-atlas · 6efc753cfd11
Censorship detected in UZvoidly-atlas · e4d1315ce933
Censorship detected in UZvoidly-atlas · bfeb8750dbee
Internet censorship detected in Uzbekistanvoidly-atlas · 87c34ba312fb
Censorship detected in UZvoidly-atlas · 9e4b93dfe035
Internet censorship detected in Uzbekistanvoidly-atlas · 4dcac3e95705
Internet censorship detected in Uzbekistanvoidly-atlas · 63811d4f5b25
Internet censorship detected in Uzbekistanvoidly-atlas · 9d1e1c338934
Episode
country UZise-be086d27ce1fcac7a6ee25a3 · 2026-08-12 00:00
Derivation
UnwrittenNo derivation row
Comparison
Episodes side by side
Same situation, one column per episode, ordered by start time. Component values are the 0–1 inputs to the weighted score.
| Measure | country UZ 2026-08-12 00:00 |
|---|---|
| Classification | SERVICE_BLOCKING |
| Stress | 60 |
| Confidence | 15% |
| Status | resolved |
| Anomaly | 0.00 |
| Breadth | 0.00 |
| Persistence | 0.00 |
| Corroboration | 0.00 |
| Baseline deviation | 0.00 |
| Baseline n | none |
Record
Outage reporting
Outage reporting for Uzbekistan in August 2026 is read from NetBlocks, Cloudflare, and Internet Society Pulse. A note is attached when it names this place and falls in this month. It is not an observation, and it does not change the stress score. Fetched 2026-10-28 23:07.
- No NetBlocks report names Uzbekistan in August 2026.
- No Cloudflare outage note names Uzbekistan in August 2026. Radar entries are not connected on this deployment.
- Internet Society Pulse is not connected on this deployment.
Headlines
Headlines for Uzbekistan in August 2026 from Google News. Public headlines are not an observation, and they do not change the stress score.
Setting
Collateral models
Attached air, maritime, reference-CTI, and proprietary nodes are co-occurrence notes. They are not inputs to the stress score.
No air track is attached to this record.
The reference catalog is attached so it can be read beside this situation. It is not an observation, and it is not an input to the stress score.
No catalog entry names this place. The catalog stays reference material.
No supplier note matches this situation. Supplier notes stay outside the score.