Updated 1:16 PM EDT
Sources and method
Live Roads USA reads 32 official road sources covering 49 states and Washington, DC, and shows what each one publishes, credited and linked. Here is every source, what it covers, its terms and how it is doing right now.
How the site works
- Official sources only. Every closure, crash, work zone and chain control comes from the agency that runs the road: a state DOT, its 511 service, a city transportation department, the National Park Service. The page shows the agency's own words, its times and, where it publishes one, a link to its page.
- News is kept apart. Local news reports of crashes appear labelled as news, with the outlet named and linked. They never count in the numbers, the pass status or any "closed" or "clear" answer.
- One data service. The feeds arrive through Roadscore, the network's data service, which reads each agency on its own schedule, puts them in one format and drops the duplicates when two feeds report the same event. The pages refresh every minute; each agency publishes at its own pace, and each event shows when its agency last updated it.
- "Not covered" is not "all clear". There is no national feed: each state publishes its own, and not every state publishes every layer. A page says when a layer is not covered in a state, and only says "nothing reported" where a source is connected and publishing.
- A silent feed is flagged. A statewide work zone feed never has zero entries, so when one sends nothing, the page says the feed has stopped instead of showing an empty road. When a source fails, the last good data stands in for up to an hour, with its time shown; after that the page says it has no data.
- Rules are sourced and dated. Every rule in the guides and on the state pages (chain laws, move over laws, phone laws, speed limits) comes from a statute, a DOT, a state police or a DMV, with the date it was checked. What could not be confirmed on an official page is left out and said to be.
Live road sources
| Source | Covers | Now | Credit and terms |
|---|---|---|---|
| State DOT work zone feeds (WZDx) | Work zones and lane closures: 25 states | Publishing11,013 events · October 27, 2026, 1:12 PM EDT | Work Zone Data Exchange feeds, US state departments of transportationCC0 1.0 (declared in each feed's feed_info, the only licence the USDOT WZDx specification allows; Ohio and Oregon feeds behind free keys, also CC0) |
| NYC DOT | Work zones and lane closures: New York | Publishing3,870 events · October 27, 2026, 1:12 PM EDT | NYC Department of Transportation, NYC Open DataNYC Open Data Law (NYC Admin. Code §23-502(d)): no registration, licence or restrictions on use; credited as NYC DOT, NYC Open Data |
| State 511 system | Work zones and lane closures: 9 statesCrashes and incidents: 12 states | Publishing3,019 events · October 27, 2026, 1:11 PM EDT | State DOT 511 systems (DriveNC, 511GA, AZ511, NVroads, UDOT Traffic, CTroads, 511 Idaho, Alaska 511)No data licence; each state's 511 developer API (free key). CTroads terms forbid redistribution or commercial use without CTDOT's written consent; the other states publish no reuse terms |
| VDOT SmarterRoads | Work zones and lane closures: VirginiaCrashes and incidents: Virginia | Publishing2,101 events · October 27, 2026, 1:04 PM EDT | VDOT SmarterRoadsVDOT SmarterRoads data terms; credited as VDOT SmarterRoads with a link to smarterroads.vdot.virginia.gov |
| State 511 systems (CARS: 511NY, INDOT, KDOT, MnDOT, MassDOT, NDOT, TDOT) | Crashes and incidents: 9 statesWork zones and lane closures: Connecticut, Massachusetts, Nebraska, New Jersey, New York, Tennessee | Publishing1,806 events · October 27, 2026, 1:09 PM EDT | Indiana DOT, Kansas DOT (KanDrive), Minnesota DOT (511MN) and New York State DOT with TRANSCOM (511NY, including its New Jersey, Connecticut and Pennsylvania events), CARS 511 event data, public domain; MassDOT (Mass511), Nebraska DOT (Nebraska 511) and Tennessee DOT (Tennessee 511 / SmartWay), CARS 511 public event reportscarsapi_v1 events marked PUBLIC_DOMAIN; gateway reports are the DOTs' public 511 data, credited to each DOT with a link to its 511 site |
| Caltrans | Work zones and lane closures: CaliforniaChain controls: California | Publishing872 events · October 27, 2026, 1:08 PM EDT | California Department of Transportation (Caltrans)Caltrans Conditions of Use (dot.ca.gov/conditions-of-use): public domain information, may be distributed or copied as permitted by law |
| DriveTexas.org | Work zones and lane closures: TexasCrashes and incidents: Texas | Publishing726 events · October 27, 2026, 12:24 PM EDT | DriveTexas.orgDriveTexas.Org Data Sharing and Use Agreement (TxDOT): revocable, non-transferable licence to use, copy and distribute; no sub-licensing, sale or lease without TxDOT's written consent; no TxDOT name or logo without consent; descriptions and road names may be adapted to common usage only. Key expires each 31 March (renewal email on 1 March) |
| Michigan DOT (MiDrive) | Work zones and lane closures: MichiganCrashes and incidents: Michigan | Publishing489 events · October 27, 2026, 1:12 PM EDT | Michigan DOT (MiDrive)No licence stated on MiDrive; michigan.gov policies reserve copying and commercial use to the State's written permission |
| Illinois DOT | Work zones and lane closures: Illinois | Publishing439 events · October 25, 2026, 8:00 PM EDT | Illinois Department of Transportation (IDOT)No licence stated; IDOT ArcGIS layers carry only a disclaimer (no warranty of accuracy) |
| CDOT / COtrip | Work zones and lane closures: ColoradoCrashes and incidents: ColoradoChain controls: Colorado | Publishing416 events · October 27, 2026, 1:00 PM EDT | CDOT / COtripCDOT data-sharing API subscription (manage-api.cotrip.org); credited as CDOT / COtrip with a link to cotrip.org |
| Oregon DOT (TripCheck) | Work zones and lane closures: OregonCrashes and incidents: OregonChain controls: Oregon | Publishing243 events · October 27, 2026, 1:09 PM EDT | Oregon Department of Transportation (ODOT) TripCheck, and the local agencies reporting to itODOT Developer Portal terms of use: public and private businesses may use and circulate the data if they credit the providing agency, mirror it on their own servers and repeat ODOT's disclaimer |
| California Highway Patrol | Crashes and incidents: California | Publishing233 events · October 27, 2026, 1:11 PM EDT | California Highway Patrol (CHP), via Caltrans QuickMapPublic domain (CHP and Caltrans Conditions of Use: state information, may be distributed or copied as permitted by law); read via Caltrans QuickMap |
| DDOT (TOPS permits) | Work zones and lane closures: District of Columbia | Publishing228 events · October 26, 2026, 6:29 PM EDT | District Department of Transportation (DDOT), TOPS permits via DC GIS, CC BY 4.0CC BY 4.0 (opendata.dc.gov); credit DDOT / Open Data DC |
| Maryland CHART | Work zones and lane closures: MarylandCrashes and incidents: Maryland | Publishing185 events · October 27, 2026, 1:11 PM EDT | Maryland CHART, Maryland Department of TransportationRoad closures: Public Domain (opendata.maryland.gov). Open events from CHART's export service: no licence stated |
| WSDOT | Crashes and incidents: WashingtonChain controls: Washington | Publishing183 events · October 27, 2026, 1:10 PM EDT | Washington State Department of Transportation (WSDOT)No licence stated on the Traveler Information API or its keyless outputs; WSDOT asks that permission be sought to use content from its site |
| Data provided by 511.org | Work zones and lane closures: CaliforniaCrashes and incidents: California | Publishing169 events · October 27, 2026, 1:01 PM EDT | Data provided by 511.org (Metropolitan Transportation Commission)511 Data Disseminator Agreement: credit "data provided by 511.org" with a link; not to be sold standalone as received. WZDx feed CC0 |
| ALGO Traffic (ALDOT) | Work zones and lane closures: AlabamaCrashes and incidents: Alabama | Publishing164 events · October 27, 2026, 1:10 PM EDT | ALDOT and ALEA, ALGO Traffic (University of Alabama CAPS)No licence or terms published; credited to ALDOT / ALGO Traffic with a link to each event |
| MoDOT | Crashes and incidents: Missouri | Publishing156 events · October 27, 2026, 10:41 AM EDT | Missouri Department of Transportation (MoDOT) Traveler InformationNo licence stated on MoDOT's traveler map feed (its WZDx feed is CC0, read by the wzdx source) |
| 511MT / SD511 | Work zones and lane closures: Montana, South DakotaCrashes and incidents: Montana, South DakotaChain controls: Montana | Publishing125 events · October 27, 2026, 12:50 PM EDT | Montana DOT (511MT) and South Dakota DOT (SD511)No licence; MDT terms of use: public service, information as is. SD511 states none. Credited with a link to each 511 site |
| Courtesy of the Arkansas Department of Transportation | Work zones and lane closures: ArkansasCrashes and incidents: Arkansas | Publishing119 events · October 27, 2026, 9:48 AM EDT | Courtesy of the Arkansas Department of TransportationIDrive Arkansas acceptable use policy: credit "Courtesy of the Arkansas Department of Transportation" with a link to idrivearkansas.com; do not present as your own; NOT to be displayed in association with any advertising (exclude Arkansas data from ad-bearing pages) |
| RIDOT (Rhode Island) | Work zones and lane closures: Rhode IslandCrashes and incidents: Rhode Island | Publishing100 events · October 24, 2026, 12:00 AM EDT | Rhode Island Department of Transportation (RIDOT), dot.ri.gov/travelNo published terms (RIDOT traveler information pages); shown with credit on the network's sites only |
| NMRoads (NMDOT) | Work zones and lane closures: New MexicoCrashes and incidents: New Mexico | Publishing97 events · October 27, 2026, 6:48 AM EDT | New Mexico DOT (NMDOT), NMRoads, CC0CC0 1.0 (stated in the feed) |
| WV511 (WVDOT) | Work zones and lane closures: West VirginiaCrashes and incidents: West Virginia | Publishing84 events · October 27, 2026, 12:50 PM EDT | West Virginia DOT (WVDOT), WV511No licence or terms published; credited to WVDOT / WV511 with a link |
| National Park Service | Also used beside the states' own feeds | Publishing53 events · October 26, 2026, 8:00 PM EDT | National Park ServiceUS federal government work (public domain); credited as National Park Service with a link to the park's page |
| National Weather Service | Also used beside the states' own feeds | Publishing25 events · October 27, 2026, 1:09 PM EDT | NOAA / National Weather ServicePublic domain (US federal government work, weather.gov disclaimer); no implied NWS endorsement, NWS name and logo not used |
| WYDOT (wyoroad.info) | Crashes and incidents: WyomingChain controls: Wyoming | Publishing10 events · October 27, 2026, 1:11 PM EDT | Wyoming Department of Transportation (WYDOT), wyoroad.infoNo licence stated; WYDOT disclaimer: data provided as is |
| ODOT (OHGO) | Crashes and incidents: Ohio | Publishing9 events · October 27, 2026, 1:12 PM EDT | Ohio Department of Transportation (ODOT), OHGOOHGO API terms of use (free key, ODOT may revoke access); no reuse licence stated for incidents (OHGO's WZDx feed is CC0, read by the wzdx source) |
| KYTC (Kentucky) | Crashes and incidents: Kentucky | Publishing7 events · October 27, 2026, 1:10 PM EDT | Kentucky Transportation Cabinet (KYTC), CC0CC0 1.0 (KYTC open data, stated on the ArcGIS item); credited to KYTC |
| New England Compass (MaineDOT, NHDOT, VTrans) | Crashes and incidents: Maine, New Hampshire, Vermont | Publishing4 events · October 27, 2026, 7:51 AM EDT | Maine DOT, New Hampshire DOT and Vermont Agency of Transportation (Tri-State), New England CompassTri-State Developer Portal agreement: use, reproduction and redistribution granted (commercial use acknowledged); credit MaineDOT, NHDOT and VTrans as the provider; no state logos or trademarks; do not claim ownership |
| CBP border wait times | Also used beside the states' own feeds | Connected, nothing now0 events | U.S. Customs and Border Protection (CBP) Border Wait TimesPublic domain: a work of the US Federal Government (17 U.S.C. 105), see https://www.cbp.gov/site-policy-notices |
| HDOT (GoAkamai) | Work zones and lane closures: Hawaii | Not responding0 events | Hawaii DOT (HDOT), GoAkamai lane closuresNo licence or terms published; credited to HDOT / GoAkamai |
| Iowa DOT 511 | Crashes and incidents: Iowa | Connected, nothing now0 events | Iowa Department of Transportation (Iowa DOT), 511 events, CC BY 4.0CC BY 4.0 (Iowa DOT open data); Iowa DOT GIS data and 511 data feed terms; credit Iowa DOT with a link to 511ia.org |
"Now" is the number of events the source is publishing at this moment and the time of its latest one. Terms as recorded by Roadscore from each source's licence or agreement; where none is recorded yet, the source's own site states its terms. Local news reports (29 now) are shown apart and never counted.
Reference data and other services
Weather warnings and advisories, through its public API.
FHWA, Toll Facilities in the United States ↗
Every tolled road, bridge and tunnel, who runs it and which transponders it takes.
Toll schedules of the Pennsylvania Turnpike, the NJ Turnpike Authority and the NY State Thruway ↗
The year's car tolls, entry to exit, from each authority's own rate tables; VDOT SmarterRoads for Virginia's live express lane prices.
U.S. Energy Information Administration ↗
Weekly retail gas and diesel prices.
Alternative Fuels Data Center (U.S. Department of Energy) ↗
Public EV charging stations.
U.S. Customs and Border Protection ↗
Wait times at the land ports of entry from Canada and Mexico.
State statutes, DOTs, state police and DMVs
The rules in the guides and on each state page: chain laws, move over laws, phone laws, speed limits. Each is linked where it is used, with the date it was checked.
U.S. Census Bureau and OpenStreetMap contributors ↗
State boundaries (Census cartographic boundary files, through us-atlas), which place each event in its state; the base map (OpenFreeMap or MapTiler, © OpenStreetMap contributors); and the names of a few toll road exits.
Corrections
Live Roads USA is not an official service: when a road differs from what an agency reports, the agency's own site and its signs come first. Agencies that want a direct line for corrections, or to publish closures that never reach a feed, can reach us through partners. Developers can use the same data through the public API.