Methodology
Camera counts and freshness shares on this site are computed by our own scripts from the agency feeds. This page says exactly how.
1. Camera count
We download each state’s public camera feed (2026-11-20). A record counts as one camera if it has a still-image address and a position. For California we count only cameras the feed marks in service. A camera that appears twice with the same image address is counted once. Washington records whose image is hosted on Oregon’s TripCheck server are counted under Oregon only.
2. Fresh image
For each camera we send one HEAD request to the image address (probe date 2026-11-20) and read the Last-Modified header. An image is fresh if that time is within 60 minutes of the probe. Cameras whose server sends no Last-Modified are left out of the percentage, and each page shows how many cameras the percentage is based on. Illinois also publishes an AgeInMinutes field, which we use when the header is missing. We never use a feed’s “updated” metadata as image age. A camera whose server did not answer our probe (timeout, refused connection) is not counted as offline; it simply has no age, because one failed request does not prove a camera is down. Last-Modified is the server’s own header; whether a given host sets it at the true capture time cannot be confirmed by us.
3. Latest results
| State | Cameras | With readable timestamp | Fresh (≤60 min) |
|---|---|---|---|
| California | 3,439 | 3,435 | 100% |
| Washington | 1,644 | 1,633 | 98% |
| Oregon | 1,208 | 1,207 | 99% |
| Illinois | 3,824 | 2,243 | 100% |
| Iowa | 1,259 | 1,112 | 100% |
| Kentucky | 243 | not probed | n/a |
One probe is a snapshot, not an uptime figure. We do not publish uptime until we have a week of probes.
4. Which cameras appear where
A camera is shown in full on at most one pass, city or route page; the more specific page owns it (pass before city before route). Hubs and corridor pages show up to 12 featured cameras plus tables. See the status page for live totals.
Step by step, with this edition’s numbers
- Feed fetch on 2026-11-20: California 3,439, Washington 1,644, Oregon 1,208, Illinois 3,824, Iowa 1,259, Kentucky 243 cameras, deduplicated by picture link (11,617 in total).
- Image probe on 2026-11-20 06:16 UTC: one HEAD request per picture, 15 second limit. We store the HTTP status and the Last-Modified age in minutes.
- Fresh means Last-Modified within 60 minutes of the probe. Of 9,630 cameras with a readable timestamp, 9,585 were fresh.
- Error means the server replied with a non-200 status. No answer means no reply (timeout or connection failure) and is never counted as offline.
Route order and maps
Cameras on a pass or route page are sorted along the principal axis of their coordinates (west to east or north to south). Distance along the route is the sum of straight-line miles between neighbours. Maps use the feed’s latitude and longitude scaled to the page, with a scale bar and corner coordinates computed from them. A dot cloud shows where cameras are; it is not a drawn state outline.
Known limits
- One probe is a snapshot, not uptime, and not a time series.
- Last-Modified is the file time the server reports; it may differ from the moment of capture, and some servers send none.
- Illinois and Kentucky image servers did not answer our probe from one PC, so we show no fresh or offline rate for them.
- Route order is geometric and can be slightly off on winding passes.
- Update intervals are not in our data and are not stated.
Check our numbers
The state table behind every total is downloadable under open data and summarised in the research report. Terms for each feed are listed on data sources.