Voidly
Data

Incident record · Belarus

Internet connectivity disruption in Belarus

Type
disruption
Status
active
Severity
critical
Inspect evidence Cite this incident

Source summary

IODA detected significant connectivity drop in Belarus. 1 critical alerts recorded.

Open incident JSON
Reported anomaly rate
31%

Source-defined signal; not a universal test-failure percentage.

Source measurement count
1

The record’s count can represent aggregate inputs or alerts.

Incident confidence
65%

A source score, not certainty of intentional censorship.

Linked evidence has its own count and confidence fields. These quantities are not interchangeable.

Follow the evidence

1 linked records.

Inspect the observation, the upstream claim and why it was linked.

Qualifying linked evidence sources: IODA (1). Historical incident source labels may include quarantined observations and are not detection evidence by themselves.

Linked observation dates

1 dated · 0 without a verified timezone
IODA1 linked record
Oct 14, 2026 · 20:30 UTCSingle observed timestamp

Each point is a linked record. Horizontal position shows observation time; stacking separates nearby points. The full records below provide the values. This is not a measured outage-duration chart.

Upstream claims are attributed to their source. Multiple records or source names do not by themselves establish independent corroboration.

IODA1 record · open evidence

outage · critical

ioda:alert:ping-slash24:region:443:1792009800

IODA detected critical level outage for Brest

Upstream claim · IODA
Signal value
0.310078
Signal baseline
258
Evidence confidence
75%
Link confidence
80%

Why it is linked: Same country and date, critical level IODA alert

Retrieved
2026-10-15 00:00:08.504154 · timezone unspecified
Open IODA entity dashboard (day parameters)
Complete evidence record
{
  "asn": null,
  "blockingMethod": null,
  "citationScope": "signal_window",
  "citationUrl": "https://ioda.inetintel.cc.gatech.edu/country/BY?from=1791936000&until=1792022400",
  "confidence": 0.75,
  "continent": null,
  "countryCode": "BY",
  "domain": null,
  "domainCategory": null,
  "exactMeasurementLink": false,
  "id": 562765524,
  "kind": "alert",
  "linkConfidence": 0.8,
  "linkReason": "Same country and date, critical level IODA alert",
  "observedAt": "2026-10-14T20:30:00Z",
  "probeNodeId": null,
  "regionCode": "443",
  "retrievedAt": "2026-10-15T00:00:08.504154",
  "riskTier": null,
  "signalBaseline": 258,
  "signalLevel": "critical",
  "signalType": "outage",
  "signalValue": 0.31007751937984496,
  "source": "ioda",
  "sourceRef": "ioda:alert:ping-slash24:region:443:1792009800",
  "sourceUrl": "https://ioda.inetintel.cc.gatech.edu/country/BY",
  "unSubregion": null,
  "upstreamCause": null,
  "upstreamClaim": "IODA detected critical level outage for Brest",
  "upstreamSeverity": "critical"
}
Source-reported corroboration

The source’s corroboration assessment is separate from incident confidence and evidence-link confidence. Inspect its source list, count and description.

{
  "description": "Single source label: ioda",
  "evidenceCount": 1,
  "level": "low",
  "score": 0.6,
  "sourceCount": 1,
  "sources": [
    "ioda"
  ]
}

Declared incident sources (historical metadata): IODA.

Qualifying linked evidence sources: IODA (1).

Fewer than two qualifying linked source labels are present. Stored incident labels may include quarantined OONI observations and do not establish corroboration.

Scope and attribution

What the record names.

Methodology

Affected services

No services named.

Incident mechanism

No mechanism specified at the incident level.

Individual evidence may carry more specific methods. Those do not automatically describe the entire incident.

Affected domains · 0

Domains named by the source record. Each link opens country-specific OONI measurements; a named domain is not a blanket national-block verdict.

No domains named.

Networks and evidence attribution

ASNs named by this source record: None listed.

This aggregate describes fields literally present in qualifying linked evidence. It does not identify who caused an event or prove intent.

{
  "asns_attributed": 0,
  "domains_attributed": 0,
  "methods": [
    {
      "evidence_count": 1,
      "method": "outage"
    }
  ],
  "note": "Aggregated from this incident's qualifying linked evidence rows — only domains, ASNs, and blocking methods the evidence literally records are shown, with the per-item evidence count. No per-domain/per-ASN attribution is present in the qualifying linked evidence for this incident (e.g. country/ASN-level outage signals).",
  "sources": [
    "ioda"
  ],
  "top_asns": [],
  "top_domains": []
}
What this record cannot establish

Measurements alone do not attribute an event to a government, ISP or another actor, and do not establish intent. An outage or anomalous result can have several explanations.

The country label is an aggregation scope. It is not a census of every network, city or service. Regional or ASN fields belong to their individual source evidence and should not be expanded into a national claim.

A confirmed duration is not supplied. The source observation window and evidence timestamps do not prove an exact start and stop of blocking.

Signal definitions, baseline rates and model versions depend on the source. This record does not establish a common baseline or calibrated certainty. Use the source’s specific signal definition and evaluation before interpreting a score.

Inspect measurement coverage

Cite this incident

Take the record
with you.

Use the permanent published URL.
The original source title is preserved.

BibTeX ↓RIS ↓Markdown ↓JSON ↓Full citation page →

The record over time.

Created
2026-10-15 00:00:23.089097 · timezone unspecified
Last updated
2026-10-15 00:00:23.089097 · timezone unspecified
Revision
1
Revision history and original fields

Revision-history array unavailable.

Canonical ID: BY-2026-1578. Source ID: BY-2026-1578. Hash ID: 547878fe4121.

Additional source duration field: unavailable. It is retained separately from the minutes field and does not establish a verified event duration.

Complete source JSON
{
  "affectedAsns": [],
  "affectedDomains": [],
  "affectedServices": [],
  "anomalyRate": 0.31007751937984496,
  "attribution": {
    "asns_attributed": 0,
    "domains_attributed": 0,
    "methods": [
      {
        "evidence_count": 1,
        "method": "outage"
      }
    ],
    "note": "Aggregated from this incident's qualifying linked evidence rows — only domains, ASNs, and blocking methods the evidence literally records are shown, with the per-item evidence count. No per-domain/per-ASN attribution is present in the qualifying linked evidence for this incident (e.g. country/ASN-level outage signals).",
    "sources": [
      "ioda"
    ],
    "top_asns": [],
    "top_domains": []
  },
  "confidence": 0.65,
  "corroboration": {
    "description": "Single source label: ioda",
    "evidenceCount": 1,
    "level": "low",
    "score": 0.6,
    "sourceCount": 1,
    "sources": [
      "ioda"
    ]
  },
  "country": "BY",
  "countryName": "Belarus",
  "createdAt": "2026-10-15T00:00:23.089097",
  "description": "IODA detected significant connectivity drop in Belarus. 1 critical alerts recorded.",
  "duration": null,
  "durationHours": null,
  "endTime": null,
  "evidence": [
    {
      "asn": null,
      "blockingMethod": null,
      "citationScope": "signal_window",
      "citationUrl": "https://ioda.inetintel.cc.gatech.edu/country/BY?from=1791936000&until=1792022400",
      "confidence": 0.75,
      "continent": null,
      "countryCode": "BY",
      "domain": null,
      "domainCategory": null,
      "exactMeasurementLink": false,
      "id": 562765524,
      "kind": "alert",
      "linkConfidence": 0.8,
      "linkReason": "Same country and date, critical level IODA alert",
      "observedAt": "2026-10-14T20:30:00Z",
      "probeNodeId": null,
      "regionCode": "443",
      "retrievedAt": "2026-10-15T00:00:08.504154",
      "riskTier": null,
      "signalBaseline": 258,
      "signalLevel": "critical",
      "signalType": "outage",
      "signalValue": 0.31007751937984496,
      "source": "ioda",
      "sourceRef": "ioda:alert:ping-slash24:region:443:1792009800",
      "sourceUrl": "https://ioda.inetintel.cc.gatech.edu/country/BY",
      "unSubregion": null,
      "upstreamCause": null,
      "upstreamClaim": "IODA detected critical level outage for Brest",
      "upstreamSeverity": "critical"
    }
  ],
  "evidenceCount": 1,
  "evidenceSourceBreakdown": {
    "ioda": 1
  },
  "evidenceSpan": {
    "earliest": "2026-10-14T20:30:00Z",
    "latest": "2026-10-14T20:30:00Z"
  },
  "flag": "🇧🇾",
  "generated_at_utc": "2026-10-15T09:44:39.989188Z",
  "hashId": "547878fe4121",
  "id": "BY-2026-1578",
  "incidentType": "disruption",
  "measurementCount": 1,
  "mechanism": null,
  "normalOoniObservationCount": 0,
  "normalOoniObservationNote": "These linked OONI rows carry the historical signal_level='normal' stored label and are quarantined from qualifying evidence pending regrade. The label is not proof that every row was accessible or anomaly-free: low-anomaly rows and rows with an omitted confirmed result may be present.",
  "normalOoniObservations": [],
  "readableId": "BY-2026-1578",
  "reportUrl": "https://api.voidly.ai/data/incidents/547878fe4121/report?format=markdown",
  "revision": 1,
  "severity": "critical",
  "severityGrade": null,
  "sources": [
    "ioda"
  ],
  "startTime": "2026-10-14T20:30:00Z",
  "status": "active",
  "title": "Internet connectivity disruption in Belarus",
  "updatedAt": "2026-10-15T00:00:23.089097"
}
All Belarus incidents
Oct 11, 2026 · censorshipInternet censorship detected in BelarusOct 7, 2026 · censorshipSustained censorship in BY (2026-10)Oct 7, 2026 · censorshipInternet censorship detected in BelarusOct 6, 2026 · censorshipCensorship detected in BYOct 5, 2026 · censorshipCensorship detected in BYOct 4, 2026 · censorshipCensorship detected in BY

Related records come from up to 100 recent records in the same country. They do not establish a causal connection.

Country profile Explore OONI measurements Live feed

Check this live

Read incident JSON

Read the published record and its observation dates. A fresh response does not mean a new measurement or confirm a current restriction.

MCP and curl examples

Claim assessment is on hold. While the public incident projection is under review, the unified MCP service may answer verify_claim with an insufficient-evidence response. The example below is a request, not a verified conclusion.

Unified MCP endpoint: https://api.voidly.ai/mcp. Use the request in an initialized MCP client. Nothing runs on this page.

The curl command reads the published incident record; it does not call verify_claim or test a network connection.

MCP endpoints and availability

Agent summary

Facts: Internet connectivity disruption in Belarus. Country: Belarus. Source type: disruption. Source status: active. Reported observation window: 2026-10-14T20:30:00Z to unavailable.

As of linked evidence: . Record generated: 2026-10-15T09:44:39.989188Z; page checked: 2026-10-15T09:44:40.009Z. These are different times.

Stored incident source labels: 1 distinct declared names (ioda). These are historical metadata; qualifying linked sources are shown above. Source names are not independent corroboration.

Cite: Voidly Research. (n.d.). Internet connectivity disruption in Belarus [BY-2026-1578]. Voidly Global Censorship Index. https://voidly.ai/incident/BY-2026-1578

Publication date: Not supplied.

Use this in your agent

Connect the read-only Atlas MCP service, then select and copy this request into your agent.

Atlas MCP setup · Agent summary JSON · Endpoint: https://atlas-mcp.voidly.ai/mcp

Source generated:
Page source check:

Permanent incident URL

Voidly-original annotations: CC BY 4.0. Upstream data retain their source licenses.