← Ebola Outbreak 2026

Data & API

The numbers on the dashboard are free to use under CC BY-SA 4.0. No account, no key, and any website can call them from the browser. Every figure points back to the source revision it came from, so you can check it.

Endpoints

Every outbreak has its own set of endpoints, addressed by its slug. Start from the list to find them. The examples below use the default outbreak, ebola-bundibugyo-2026.

GET /api/v1/outbreaks

Every outbreak tracked: slug, title, disease, status, places, source, the latest confirmed cases and deaths with their date, and links to its page and its endpoints.

Try it: /api/v1/outbreaks

GET /api/v1/outbreaks/<slug>/toll

One row per day (per weekly report, for an outbreak read from one) of cumulative confirmed, suspected, deaths and recovered, each linked to the exact Wikipedia revision, or to the report or page, it was read from. A field the source does not report is null: Candida auris (CDC’s NNDSS table) has no deaths, its `confirmed` is clinical cases, and its rows add `screening` (people found to carry the fungus on a screening swab, never counted as cases or suspected cases) with `mmwrYear` and `mmwrWeek`.

from, to
Inclusive date range, YYYY-MM-DD.
limit
Keep only the most recent N rows (1–1000).
format
json (default) or csv.

Try it: /api/v1/outbreaks/ebola-bundibugyo-2026/toll?from=2026-09-01&format=csv

GET /api/v1/outbreaks/<slug>/metrics

Derived indicators: new cases and deaths per 7 days, growth rate, doubling or halving time, reproduction number (Rt) and three fatality ratios, with their assumptions.

include=daily
Add the day-by-day series (new cases, 7-day average, interpolated flag).
format=csv
Return the daily series as CSV.

Try it: /api/v1/outbreaks/ebola-bundibugyo-2026/metrics?include=daily

GET /api/v1/outbreaks/<slug>/signals

Countries the news has linked to the outbreak, when each was first mentioned, and, once officially confirmed, how far the news led.

Try it: /api/v1/outbreaks/ebola-bundibugyo-2026/signals

An unknown slug returns 404 with a JSON { "error": ... } body, like every other error.

Un-prefixed endpoints are permanent aliases

/api/v1/toll, /api/v1/metrics and /api/v1/signals always return the default outbreak (currently ebola-bundibugyo-2026), with the same parameters and the same response as its per-outbreak endpoints. They will keep working, so existing scripts need no change. New integrations should use the per-outbreak paths.

Latest reading, as the API returns it

{
  "date": "2026-11-21",
  "confirmed": 11711,
  "suspected": 368,
  "deaths": 5719,
  "recovered": 3217,
  "source": "Wikipedia infobox (cites INSP DRC / WHO)",
  "sourceUrl": "https://en.wikipedia.org/w/index.php?oldid=1386855602",
  "revid": 1386855602,
  "revisionTimestamp": "2026-11-21T01:24:53Z",
  "rawPath": "data/raw/infobox/1386855602.txt",
  "rawSha256": "d0fc83013ae52b36622aefe31559f3d784aba52599ef86e544be7e26eec1974f"
}

From a browser or script

const res = await fetch("/api/v1/outbreaks/ebola-bundibugyo-2026/metrics");   // or the full https:// address
const { growth, rt, incidence } = await res.json();
console.log(growth.trend, rt.estimate);

Fair use

The API is free and keyless, and we would like to keep it that way. Please be considerate:

  • Cache what you fetch. The figures are refreshed twice a day and responses are cached for 15 minutes, so asking more often than that returns the same numbers. Polling once an hour is plenty.
  • Stay under the limit. Each IP address may make up to 60 requests per 60 seconds across /api/. Beyond that the API answers 429 Too Many Requests until the window passes. Back off and retry later; do not retry in a tight loop.
  • Use the parameters. Ask for a date range or a limit instead of downloading everything repeatedly.
  • Need more? If you run something that needs a higher limit, such as a news site, a dashboard or research, open an issue and tell us what you are building. Clients that keep hitting the limit may be blocked. For business use, a paid H5N1 feed with history and alerts is planned: see commercial data.

The service is provided as is, with no uptime guarantee, and is not an official public health resource.

How the indicators are calculated

All of them start from the daily cumulative totals. Days the source did not publish are filled in a straight line between neighbouring readings and flagged interpolated. A total that falls is treated as unchanged, because cumulative counts cannot decrease.

New cases and deaths per 7 days
The rise in the total over the last 7 days, compared with the 7 days before that.
Where the window ends
The source is updated in batches, so the newest days often look like “no new cases” just because the report has not been entered yet. Measuring up to such a day would understate current incidence. The windows therefore end on the latest day the total actually moved, but never more than 3 days before the last reading, so a genuine halt still shows. The response says which day that is in windowEnd.
Growth rate and doubling or halving time
r = ln(this week’s new cases ÷ last week’s) ÷ 7, per day. The range is a 95% interval from counting error alone (the square root of 1/n₁ + 1/n₂ on the log ratio). It does not include reporting noise, so treat it as a minimum. The trend is called growing or shrinking only when that whole range is above or below zero; otherwise stable. Doubling time is ln 2 ÷ r.
Reproduction number (Rt)
The average number of people each case infects, implied by the growth rate. With a gamma-distributed serial interval of mean μ and standard deviation σ, R = (1 + r·σ²/μ)^(μ²/σ²) (Wallinga & Lipsitch, 2007). The serial interval is set per disease, below. Where no source has been verified for a disease, Rt is left out rather than borrowed from another one. It describes recent transmission and lags real changes.
Case fatality, three ways
naive is deaths ÷ confirmed cases; it is too low while cases are still unresolved. delayAdjusted divides deaths by the cases confirmed some days earlier (set per disease, below), which accounts for the lag from confirmation to death; it is left out where that delay has no verified source. resolved is deaths ÷ (deaths + recovered); it runs high when recoveries are under-reported. The true value is most plausibly within that spread.

Assumptions by outbreak

  • Candida auris in the US 2026. Rt not reported. Rt is not reported for Candida auris: it spreads through contaminated surfaces, devices and hands in healthcare facilities, often from people who carry it for months without symptoms, so there is no serial interval to base Rt on. No case-to-death delay is used either, because NNDSS collects no deaths. Delay-adjusted fatality not reported. No deaths in the source (NNDSS does not collect deaths), so the deaths, new-deaths and fatality fields are null. Weekly source: 2 readings in the last 14 days are enough, and the days between reports are filled in a straight line.
  • Ebola Outbreak 2026. Serial interval μ = 15.3 days, σ = 9.3 days (WHO Ebola Response Team, NEJM 2014 (West Africa, Zaire ebolavirus); not measured for this Bundibugyo outbreak, so Rt carries that extra uncertainty). Confirmation-to-death delay 10 days.
  • Hantavirus Outbreak 2026. Rt not reported. A hand-curated record with no daily readings, so no rates are derived from it. Delay-adjusted fatality not reported.
  • Bangladesh Measles Outbreak 2026. Rt not reported. Rt is not reported for measles: no serial interval with a verified mean and standard deviation has been sourced, and lab-confirmed counts here depend on testing capacity, so their growth is an unreliable guide to transmission. Delay-adjusted fatality not reported.
  • US Measles Outbreaks 2026. Rt not reported. Rt is not reported for measles: no serial interval with a verified mean and standard deviation has been sourced, and the CDC’s weekly total mixes many separate outbreaks counted by rash-onset year, so its growth is an unreliable guide to transmission. Delay-adjusted fatality not reported. Weekly source: 2 readings in the last 14 days are enough, and the days between reports are filled in a straight line.
  • Greece West Nile Virus Outbreak 2026. Rt not reported. Rt is not reported for West Nile virus: it passes from birds to people through mosquitoes, not from person to person, so there is no serial interval between human cases. Delay-adjusted fatality not reported. Weekly source: 2 readings in the last 14 days are enough, and the days between reports are filled in a straight line.

Nothing here is a forecast. These are descriptions of the recent past that depend on how complete reporting is. For decisions, rely on official guidance from WHO and the health authorities.

News signals

Twice a day the tracker reads WHO and news feeds and records any country other than DR Congo that is reported to have cases linked to this outbreak. An entry is a lead to verify, not a confirmed case. The ledger keeps the date of the first mention, so once a country is officially confirmed we can measure how many days the news came earlier. It is only a useful early warning if that lead time turns out to be real and the false alarms are few, and the ledger exists to find out.

Nursing homes

A separate layer from the outbreak endpoints: recurring measurements by state and by facility, shown on Nursing homes. Same conventions (keyless, CORS-open, JSON or CSV, errors as { "error": ... }).

GET /api/v1/nursing-homes

The datasets in this layer, their sources and how fresh each one is.

Try it: /api/v1/nursing-homes

GET /api/v1/nursing-homes/respiratory

Weekly COVID-19, influenza and RSV cases and hospitalisations among nursing-home residents, by state and nationally (CDC NHSN). series=counts (default): counts, residents and reporting homes from CDC's open dataset, with rates per 100,000 residents computed from them. series=rates: CDC's dashboard rates per 100,000 residents, fresher but without counts. Null is missing data, never zero.

series
counts (default) or rates.
state
Two-letter state or territory code, or USA for the nation.
from, to
Inclusive range of week-ending dates (Sundays), YYYY-MM-DD.
format
json (default) or csv.

Try it: /api/v1/nursing-homes/respiratory?series=rates&state=USA&format=csv

GET /api/v1/nursing-homes/infection-control-citations

Nursing homes cited for an infection-control deficiency (CMS tag F880), one row per citation, with survey date, scope/severity, complaint or standard survey, correction status, dispute flags, the CMS release it came from and a Medicare Care Compare link. Without state or ccn it returns the per-state summary.

state
Two-letter state or territory code: that state's citations.
ccn
Six-character CMS Certification Number: one home's citations.
from, to
Inclusive range of survey dates, YYYY-MM-DD.
min_severity
Scope/severity letter A to L; G returns actual harm and immediate jeopardy only.
format
json (default) or csv.

Try it: /api/v1/nursing-homes/infection-control-citations?state=VT&format=csv

Sources, cadence and caveats

  • NHSN counts: CDC dataset tscn-ryh9 on data.cdc.gov. Labelled weekly, but its newest week is 29 March 2026 and its rows were last updated 24 August 2026. Checked twice a day; fetched only when CDC's metadata says the rows changed.
  • NHSN rates: the data file behind CDC's Nursing Home Data Dashboard on www.cdc.gov, updated on Thursdays; newest week 15 November 2026. Rates per 100,000 residents only. Recent weeks are preliminary. Its rates are close to, not equal to, rates computed from the counts.
  • CMS F880 citations: Health Deficiencies (r5ix-sfxw) on data.cms.gov, about monthly. Current release processed 1 October 2026, published 28 October 2026; next expected 2 December 2026. Fetched only when the release dates change. It holds about the last three inspection cycles per home, not a full history.
  • Influenza and RSV reporting became mandatory on 1 January 2025; the NHSN series include them from the week ending 12 January 2025. Weeks in which fewer than 90% of the usual homes reported are flagged thinReporting.
  • A citation is an inspection finding, not evidence of infections or an outbreak; it may have been corrected and may be under dispute (IDR/IIDR flags).

Outbreak Files (outbreakfiles.com, unofficial). Source: CDC National Healthcare Safety Network (NHSN), dataset tscn-ryh9 on data.cdc.gov (counts) and the data file behind CDC's Nursing Home Data Dashboard (rates), read automatically; each extract is archived with a SHA-256 checksum. U.S. government data, public domain. Not an official public health resource.

Outbreak Files (outbreakfiles.com, unofficial). Source: CMS Provider Data Catalog, Health Deficiencies (r5ix-sfxw), tag F880 only, read automatically once per CMS release; each release is archived with a SHA-256 checksum. U.S. government data, public domain. A citation is an inspection finding, not evidence of an outbreak; it may have been corrected and may be under dispute. Not an official public health resource.

Where the data comes from

Outbreak Files (outbreakfiles.com, unofficial). Figures come from the Wikipedia article's infobox (CC BY-SA 4.0), which cites INSP DRC and WHO; every reading links to the exact revision it was read from. Shared under CC BY-SA 4.0. Not an official public health resource.

  • One reading per UTC day, taken from the last revision of the article that day. Currently 139 readings, 2026-06-02 to 2026-11-21.
  • History before 2026-06-02 is not included: early versions of the article counted suspected deaths in the same field, which is a different definition.
  • Revisions that break the rule that totals never fall (typos, vandalism, edits in progress) are removed when history is imported. Some days have no reading because the infobox could not be parsed.
  • Licence: CC BY-SA 4.0. Credit “Outbreak Files” (outbreakfiles.com) and link the source revision when you republish figures. If you adapt the data, share the result under the same licence.