Zum Inhalt springen
ENERGYWATCH
EN

As of Data currently unavailable

Methodology

This page sets out how the numbers come about. The most important section is the one about what cannot be calculated here.

01Source collection

Reports come in automatically from these feeds. The state of the last run is shown next to each one.

The data store is currently unreachable, so the list cannot be shown.

02Link checking

Every source is checked regularly to see whether it is still reachable. If the last live source of an incident disappears, the incident is withdrawn automatically.

The data store is currently unreachable, so the figures cannot be shown.

03What cannot be calculated here

None of these figures appear anywhere on this site, and not out of convenience. They cannot be derived honestly from this data, and a number with false precision is worse than no number.

  • Damage in euros. There are no reliable replacement values per facility, no public insurance data and no meaningful exchange rate reference across a period of war.
  • Lost capacity as a time series. The installed capacity of a damaged facility is rarely public, the state of repair almost never, and partial load operation is not reported.
  • Affected households over time. The figures come from different bodies with different counting methods and changing territorial baselines. Two numbers from different months are not a series.
  • Completeness of the incident count. We do not know what we do not know. A drop in the number of incidents can mean that less happened, or that less was reported.
  • Incidents in occupied territories. There is no independent reporting from there. What comes from there comes from one hand, and we treat it as such.

04The four confidence levels

Every published incident carries exactly one of these four levels. The level says something about the state of the sources and nothing about the severity of the incident.

  1. 01Officially confirmed

    The operator, the ministry, the authority or an international organisation reported it themselves.

  2. 02Reported more than once

    At least two editorially independent outlets report the same thing. Two offshoots of the same house count as one.

  3. 03Single report

    Exactly one source. The record is visibly marked as such and does not enter any analysis that assumes completeness.

  4. 04Unverified

    The report exists, the review is pending. Such records are not publicly visible.

There are also two states that are not levels: disputed, when sources contradict each other, and retracted, when a report has turned out to be false. Retracted records are not deleted but stay visible with the reason.

05No incident without at least one live source

An incident can only be published if at least one of its sources is reachable. This is not an editorial rule that one tries to follow, but a condition in the database. A record that violates it cannot be saved. If the last source drops out, a regular job automatically puts the incident back into review and records the reason.

The rule exists as the CHECK constraint incident_published_needs_live_source on the Incident table, with the same condition on the Outage table.