Open data
APIdown's incident and uptime history, free to download in CSV or JSON. Useful for research, vendor due diligence, blog posts, or plotting your own charts. No account, no key.
Incident history
Every outage and degradation we have detected across all tracked APIs, with severity, start and resolution times, and duration.
5,000 most recent incidents
| Column | Meaning |
|---|---|
incident_id | Stable identifier; also the URL suffix at /incidents/{id} |
api_slug, api_name, category | Which API the incident belongs to |
severity | critical, major, or minor |
status | investigating, identified, monitoring, or resolved |
title | Short human description |
started_at, resolved_at | ISO 8601 timestamps; resolved_at empty while open |
duration_minutes | Empty while the incident is still open |
Monthly uptime
One row per API per calendar month: measured uptime, incident count, total downtime, and longest single outage.
Last 24 months, all tracked APIs
| Column | Meaning |
|---|---|
api_slug, api_name, category | Which API the row describes |
month | Calendar month as YYYY-MM (UTC) |
uptime_pct | Measured uptime for that month, three decimals |
incident_count | Incidents overlapping the month |
downtime_minutes | Total downtime, overlapping incidents merged |
longest_outage_minutes | Longest single outage in the month |
How to use it
- Attribution. These datasets are free to use, including commercially.
We ask that you credit “APIdown.net” and link to
https://apidown.netwherever you publish figures derived from them. - What the numbers are. Everything here is measured from anonymised client-side signals sent by applications running the APIdown SDK. They are our independent measurement, not the vendor's own reporting, and the two will differ. Client-side measurement includes the network path, so routing and DNS failures count against an API here.
- What is not included. No user, account, subscriber, or API-key data appears in these files, and no per-request or per-customer data — only public APIs and the incidents recorded against them.
- Freshness. Both datasets are generated on request and cached for an hour. For live values use the /v1 API instead.
Need this programmatically, filtered, or in bulk beyond the row limits? The public /v1 API covers the same data with query parameters.