Status

1 feed(s) stale.

Checked against each source when this page loads, not cached from a dashboard somebody forgot to update.

San Francisco, CA
GET https://data.sfgov.org/resource/i98e-djp9.json?%24select=max%28filed_date%29 -> 403 Forbidden: <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> <hr><center>nginx</center> </body> </html>
New York City, NY
newest 2026-09-08 · 1d old
Chicago, IL
newest 2026-09-08 · 1d old
Los Angeles, CA
newest 2026-09-05 · 4d old
Seattle, WA
newest 2026-09-08 · 1d old
Austin, TX
newest 2026-09-08 · 1d old

A feed with nothing newer than 21 days is treated as abandoned. Full per-metro detail, including which dataset each figure comes from, is on coverage.

Method

Why this page exists.

What is being measured

For each metro, the date of the newest record in the city’s own dataset, fetched when you loaded this page. Not whether our servers are up, which is the least interesting thing that could be wrong. If a city stops publishing, this is the number that moves.

Why 21 days

Cities skip holidays and occasionally a week. Three weeks of silence is longer than any normal gap we have seen and short enough to catch a dead feed before anyone works a stale list. A metro past the line is pulled from the product rather than served with a warning.

Why it is not cached

A status page built from a cache tells you what was true when someone last remembered to refresh it. This one queries each source per load, so it can be slow and it can show something we would rather it did not.

Why we check at all

Of seven candidate city datasets evaluated for this product, two had silently stopped updating, one in 2019 and one in 2020, while still serving hundreds of thousands of rows to anyone who asked. A dataset does not go offline when it dies. It just stops changing.