Open Data
Everything we record is downloadable. Take it as a spreadsheet, query it as JSON, or subscribe to the feed — no key, no sign-up, no rate-limit form to fill in.
SpreadsheetDownload as CSV
Opens directly in Excel, Google Sheets or LibreOffice. UTF-8 with a byte-order mark, so accented and non-Latin place names survive.
HXL-tagged CSV for humanitarian tools
Add format=hxl and a second row of Humanitarian Exchange Language hashtags is added under the header (#event+id, #date+occurred, #country+code+iso2, #geo+lat, #geo+lon, #severity+code and so on), so HXL Proxy, libhxl or HDX can filter and join it without a mapping step.
Build your own filtered export
Add country (ISO-2) and type to narrow it:
https://globalincidenttracker.com/api/export.php?year=2026&country=PK&type=flood
Every incident type key is listed on the incident types page. Country codes are standard ISO 3166-1 alpha-2.
ProgrammaticJSON API
No key and no registration. Please identify your application in the User-Agent header and keep automated polling to a few requests a minute.
| Endpoint | Returns |
|---|---|
| /api/incidents.php?format=list&days=1 | Recent incidents as a JSON list |
| /api/incidents.php?format=geojson&days=7 | GeoJSON FeatureCollection, ready for any mapping library |
| /api/incidents.php?country=PK&type=flood | Filtered by country and category |
| /api/incidents.php?near=24.86,67.01&radius=65 | Everything within a radius of a point, in kilometres |
| /api/stats.php | Live counters, breakdown by type and by country |
| /api/trend.php?country=PK&months=12 | Monthly counts for charting |
| /api/export.php?year=2026 | Full-year CSV |
| /api/export.php?year=2026&format=hxl | The same CSV with an HXL hashtag row |
| /rss.xml | Latest incidents as RSS |
Licence
The incident records we compile — the classification, geocoding, clustering and the pages built from them — are published under Creative Commons Attribution 4.0. Use them commercially or non-commercially; the only condition is that you credit Global Incident Tracker with a link.
Upstream data keeps its own terms. We aggregate from public agencies whose licences differ, and passing our data on does not override theirs:
- USGS, NOAA, NASA (EONET, FIRMS), openFEMA — US public domain
- GDACS — European Commission / UN, free reuse with attribution
- National warning services outside the US and Europe — CAP Alert Hub feeds, marked public domain
- Place names — GeoNames, CC BY 4.0
- Country borders — Natural Earth 1:50m, public domain. Every incident with coordinates is filed by the country whose border contains it, not by whichever country centre happens to be nearest.
- Headlines from news sources — we store the title, a link and our own classification, never the article text. Copyright in the original reporting stays with the publisher.
If you plan to redistribute at scale, check each upstream licence yourself rather than relying on this summary.
How to cite this dataset
Global Incident Tracker. (2026). Global Incident Tracker incident dataset. Retrieved 10 October 2026, from https://globalincidenttracker.com/data
For a specific record, cite its own page — every incident has a permanent URL.
What you should say about the limits
- Severity is our own monitoring signal, not an official assessment.
- We do not publish casualty figures unless an official source states them.
- News-derived records reflect where media reports, so coverage is thinner where local press is sparse.
- A large share of current records are official warnings rather than confirmed damage.
- The live archive begins when this tracker launched; older events are in the history section.
Using it on your own site?
Charts of these records, with their tables, are on the statistics page. Code and service licences are on licences & credits.
There is a ready-made embeddable map and counter that needs no key, and email alerts if you would rather be told than poll.