Every recall on this site can be read as data, free, without a key, and reused with attribution. This page says what is in it, how it was matched, and what it cannot tell you.
The cross-border crosswalk
2,057 vehicle safety recalls that appear in more than one country’s register, matched on the manufacturer’s own campaign code. 109 of them appear in all three.
No regulator publishes this, and none can: each holds only its own register, and the registers share no identifier. The one field they have in common is the number the manufacturer gave the campaign internally — Ford’s European filing and Ford’s American filing both say 26S31 — and that is what the match is built on.
| Register | Recalls stating a maker code | Where the code comes from |
|---|---|---|
| United States — NHTSA | 3,826 | A sentence inside the remedy text |
| Canada — Transport Canada | 12,304 | A published column |
| European Union — Safety Gate | 2,600 | The companyRecallCode field |
How to get it
One request, no key, no rate limit, open CORS:
https://api.carsmultiverse.com/v1/crosswalkThe full endpoint list documents the rest: each national register’s coverage, the European alerts in full, and the two who-was-told-first comparisons. There is also a Model Context Protocol server, if you would rather your assistant asked us directly.
What a row means, and what it does not
It means that two or three registers used the same manufacturer reference for a campaign. Each side keeps its own identifier and its own date, so any row can be checked against the regulator that filed it — the European rows carry a direct link to the Commission’s page for that alert.
It does not mean the notices are word for word identical, or that the recalls covered the same vehicles in each market. And absence is not evidence: a register may well hold a recall without stating the code, in which case it cannot appear here. The dataset is a floor, not a census.
The match is exact after identical normalisation on every side. Nothing is paired on brand and date, which is how a finding gets manufactured rather than discovered.
How to cite this
The dataset is deposited and has a permanent identifier, so it can be cited in work that outlives this website:
CarsMultiverse (2026). Vehicle safety recalls matched across national registers on the manufacturer’s own campaign code. Zenodo. https://doi.org/10.5281/zenodo.22087136
That identifier names one fixed version. To cite the dataset itself, which always resolves to the newest deposit, use https://doi.org/10.5281/zenodo.22087135.
The deposit is a fixed snapshot, which is what a citation needs. The copy served from the API is rebuilt continuously, which is what a reader needs. The two are meant to differ, and the deposit records the date it was taken.
The same files, with a script that regenerates the CSV, are on GitHub.
Licence
The filings belong to the regulators: the United States Department of Transportation, Transport Canada under the Open Government Licence, and the European Commission. The matching between them is ours, and you may reuse it with attribution to carsmultiverse.com.
If you find a row you think is wrong, it goes on the corrections page and we will say so there.
Canada and America · Europe and America · How to verify what we publish