Incident data and licences
Incident data for underwriting and modelling
Every safety incident the register holds at energy sites and in the power systems of data centres, as data for your own models: the cause, the part that failed, who made it and who ran it, and how long it was out, with the source behind every value. By spreadsheet, weekly file or API.
Five sets
Take one set or all of them. Every number below is read from the register as it stands today.
Data centre power
UPS and battery rooms, backup generators, switchgear, transformers and fuel systems at data centres, with how long services were down where reported.
Free sample, 20 recordsBattery storage
Grid-scale battery storage and hybrid sites: fires, thermal runaway, explosions and failures, with the manufacturer, integrator and the part that failed where named.
Free sample, 20 recordsSolar
Solar farms and commercial roofs: fires, storm and hail damage and electrical faults, with the part that failed and the outage where reported.
Free sample, 20 recordsWind
Onshore and offshore wind: fires, blade and tower failures, collapses and cable faults.
Free sample, 20 recordsGrid and substations
Substations, transformers, switchgear and lines: fires, explosions and failures that cut supply, with how long and how many were cut off where reported.
Free sample, 20 recordsWhat each record holds
- Site, place, country and the date of the incident
- Operator, owner, manufacturer, integrator and builder, where a source names them
- Capacity, technology and the age of the site at the time
- Root cause and the part that failed, as the sources state them
- The fire service response, evacuations, injuries and deaths
- How long the site or service was out, where reported
- A loss estimate, with how it was made
- Insurance and regulatory outcomes, where reported
- Every source, with the words behind each value
- Verification status: checked against a second source or not
Publicly reported incidents name the site and the companies only where the source does. Incidents given to the register in confidence are anonymised absolutely and never identify a site, company or person. How entries are written and checked: methodology.
Prices
| Licence | What it gives | Price |
|---|---|---|
| Pilot, one set | 3 months of one set: the full set today as a spreadsheet and CSV, the full verified dataset every Monday, and the API. Counts in full towards a year of that set. | £1,500 |
| One set, a year | The same for 12 months, for one business unit. | £6,000 a year |
| Enterprise | Every set, weekly files, the API, benchmarks and the annual report, up to 25 users in one business unit. | from £12,000 a year |
| Enterprise Plus and Data partner | Group-wide use, or the data inside your own product. See Enterprise and API. | £18,000 and £25,000 a year |
Prices exclude VAT where it applies; no VAT is charged at present. Use is covered by the data licence.
A free sample
Twenty records of one set with every field, as a spreadsheet, by email at once. To a work address.
Start the pilot, £1,500
A numbered invoice is made at once, to pay by card or bank transfer or to forward to whoever pays. Access starts as soon as it is paid: the set by email, the weekly files and an API key from your dashboard.
Questions
How current is it?
New incidents are found, written and checked every day, from the news in many languages, fire services, regulators and operators. Older incidents are added as the register searches the archive, country by country. The weekly file carries everything published up to that Monday.
How is it checked?
Every entry is reviewed before it is published and carries its sources, so any value can be checked. Records checked against a second source say so. Corrections are free for anyone, and a corrected entry says what changed.
Can we see it before paying?
Yes: the free sample above, and every incident's public entry on the register. For a different cut of the data, write to editor@energyincidentregister.com.