3 countries checked against their own official sources. A country with no scheme is an answer, not a gap — and where an authority would not answer us, this page says that instead.
The other continentsBack to the countries we cover
Still working through this continent.
Three channels still refuse us, and none of them is a fact about the roads behind it.
Estado de México runs its own Hoy No Circula over 18 municipalities next to Mexico City and its whole web estate times out on us (BLOCKERS.md B-016); the City of Vancouver answers HTTP 403 across its entire site (B-017); San Francisco's Treasure Island congestion pricing sits behind an SFCTA HTTP 403 and an sf.gov robot check (B-018). All three were retried once on 2026-09-09 and all three still refuse us.
The United States is otherwise now bounded city by city against publishers' own listings rather than guessed at, with two live congestion-pricing studies found, read and set aside — Los Angeles and Washington DC — and with Portland, Oregon and Seattle still owing us a countable inventory (B-019).
We still cannot read https://edomex.gob.mx/ (TCP connects in 34 ms, then the connection is reset about twelve seconds later without a ServerHello (ECONNRESET). Not a connect timeout, which is what we called it from cycle 21 to cycle 40. Measured with scripts/probe-tls.mjs.); https://sma.edomex.gob.mx/hoy_no_circula (TCP connects in 32 ms, then reset at twelve seconds without a ServerHello (ECONNRESET).
This is the host behind B-016's twenty consecutive "connect timeout" rows; the label was wrong, the inaccessibility is real.); https://legislacion.edomex.gob.mx/ (TCP connects in 33 ms, then reset at twelve seconds without a ServerHello (ECONNRESET), the same as the state's other two hosts.), so treat this as unfinished rather than clear — we do not work around a block.
Mexico City's Hoy No Circula is published.
Estado de México operates a separate Hoy No Circula over the 18 metropolitan municipalities, under its own publisher, and we cannot read a word of it — but on 12 September 2026 we finally measured why, and it is not what this file said for twenty cycles. edomex.gob.mx, sma.edomex.gob.mx and legislacion.edomex.gob.mx do not time out on TCP connect: all three accept the connection in 33 to 34 ms and are then reset about twelve seconds later, after our Client Hello and before any ServerHello.
The hosts are listening. Where the handshake breaks is not visible from here, and we do not guess: nine other government hosts on three continents produce the identical shape at almost the identical second, which is poor evidence for nine broken servers.
Offering TLS 1.0, 1.1 or 1.2 changes nothing, and a host that genuinely refuses an old protocol answers in 328 ms with an alert rather than stalling for twelve seconds — so this is not a version disagreement either. Federal channels do not carry it either — gob.mx/comisionambiental answers HTTP 200 with no mention of the programme, and its /documentos and /acciones-y-programas paths are HTTP 404.
A driver heading for Toluca or Ecatepec gets no answer from us, and we say so rather than stretching the Mexico City record over a second authority's rules.
Checked against the publisher's own listing of everything it holds — 7,542 pages from LA Metro, 7,905 pages from City of Philadelphia, 4,257 pages from City of Boston, 2,762 pages from District of Columbia, 1,801 pages from DDOT, District of Columbia, 1,634 pages from SANDAG, 915 datasets from City of Chicago open data. We still cannot read https://www.sfcta.org/projects/treasure-island-mobility-management-program (HTTP 403); https://www.sf.gov/ (HTTP 202 robot check); https://sftreasureisland.org/ (HTTP 202 robot check, redirects into sf.gov); https://www.portland.gov/sitemap.xml (HTTP 200 serving a meta-refresh to beta.portland.gov/access-denied); https://www.oregon.gov/sitemap.xml (HTTP 404, and robots.txt declares no sitemap); http://www.seattle.gov/sitemap (HTTP 200, but an HTML page rather than a URL set — no inventory to count), so treat this as unfinished rather than clear — we do not work around a block.
New York's Congestion Relief Zone remains the only scheme we have found in force, and there is still no federal inventory to measure that against: both ops.fhwa.dot.gov/congestionpricing/ and its resources index now redirect to ops.fhwa.dot.gov/program_areas/programareas.htm, a page on which the word 'pricing' does not appear at all.
So the United States has to be done city by city, and this cycle did seven of them against the publishers' own listings rather than against pages we happened to click.
Six answered with a countable inventory — 7,542 pages from LA Metro, 7,905 from Philadelphia, 4,257 from Boston, 2,762 from the District of Columbia plus 1,801 from its transportation department, 1,634 from SANDAG in San Diego, and 915 datasets from Chicago's open data portal, which is all Chicago will give us since chicago.gov serves neither robots.txt nor a sitemap.
Across all of them the vocabulary of a road charge lands on studies, freeway toll lanes, clean-air grants and — repeatedly — the DC Circulator bus, which matches 'circula' and is a bus.
Two of those studies are real and worth coming back to, in Los Angeles and Washington DC; both are recorded below with the sentence that disqualifies them, because a driver reading 'nothing here' in 2029 deserves the address of the thing that was in planning in 2026.
Portland and the state of Oregon we could not bound at all: oregon.gov declares no sitemap and answers 404 for the conventional one, and portland.gov serves its sitemap.xml as HTTP 200 carrying a meta-refresh to an access-denied page. Seattle is the same shape of gap — the sitemap its robots.txt declares is an HTML page, not a URL set — so the clean Seattle answer still rests on pages rather than a count.
San Francisco remains the hole that matters: the SFCTA project page for the Treasure Island Mobility Management Program returns HTTP 403, and both sf.gov and sftreasureisland.org answer HTTP 202 with 'we need to verify that you're not a robot', so the one US city besides New York with a charge scheme on the books is the one we cannot read, and we do not work around a robot check.
Looked at and not counted as a scheme:
Checked against the publisher's own listing of everything it holds — 773 pages from TransLink, 6,227 pages from City of Toronto, 404 datasets from Ville de Montréal open data. We still cannot read https://vancouver.ca/ (HTTP 403 across the whole estate, root included — a Cloudflare block page, retried 2026-09-09); https://council.vancouver.ca/ (HTTP 403); https://montreal.ca/sitemap.xml (HTTP 403, and no sitemap is declared in robots.txt), so treat this as unfinished rather than clear — we do not work around a block.
No entry charge, emission zone or plate ban found in force, and for the first time that is measured rather than assumed. Metro Vancouver's road charge, if one existed, would be TransLink's: it is the statutory regional authority for the Major Road Network and five regional bridges.
TransLink declares three sitemaps in its own robots.txt; enumerating them gives 773 URLs, of which exactly one matches any road-charge vocabulary, and it is transit-fares/pricing-and-fare-zones — fare zones for riders, not a charge for driving.
Its Roads, Bridges & Goods Movement page describes funding, maintenance and goods movement only, and the Transport 2050 regional strategy page does not contain the word 'pricing'. Toronto declares seven sitemaps holding 6,227 pages; the only real candidate, the Congestion Management Plan, mentions no toll, pricing, charge or fee, and 'Clean Roads to Clean Air' redirects to Road Maintenance, which is street cleaning.
Montréal will not serve us a page listing at all — no sitemap is declared and both /sitemap.xml and /sitemap_index.xml return HTTP 403 — but its open data portal answers, and across 404 datasets there are none for 'péage' or 'tarification routière'.
What is still missing is the City of Vancouver itself: not one page but the whole estate, vancouver.ca and council.vancouver.ca alike, returns HTTP 403 to us, so the one Canadian city that has actually consulted on road pricing is the one we cannot read.