Open government data, decoded
Road works radar: where work zones and lane closures cluster
On Oct 9, 2026 the work-zone feeds of 14 state transportation departments listed 5,176 events in effect. 1,581 of them report some or all lanes closed or traffic alternating one way. These feeds follow the USDOT work zone data standard (WZDx). They are public, but every state publishes its own version, so they are hard to read together.
SnapshotWZDx feeds listed in the USDOT registryData period: work zones in effect at 22:10 UTC on Oct 9, 2026Retrieved Oct 9, 2026, 22:10 UTCretrieved Oct 9, 2026
Coverage first
This is a snapshot of 20 feeds that answered out of 43 rows in the registry. 15 are state DOT feeds, 5 are city, county or multi-state feeds. Large truck states such as California, Texas, Ohio, Pennsylvania, Illinois and Georgia are not on the map because their feeds need a key we do not have, are not in the registry, or blocked our request. Treat the map as "what these states publish", never as "where the work is". It is not live and not a routing tool.
Map: work-zone events in effect by state
Click a state or a table row. Darker means more events in that state's own feed. Grey means no readable statewide feed.
- 5 to 57 (3 states)
- 65 to 124 (3 states)
- 164 to 356 (3 states)
- 363 to 641 (3 states)
- 985 to 1,482 (2 states)
- No data
| State | Feed owner | Events in effect | Lane closures | Impact not reported | Over 90 days | Ends in 7 days | Restrictions |
|---|---|---|---|---|---|---|---|
| Delaware | Delaware DOT | 11 | 6 | 5 | 0% | 11 | none |
| Florida | Florida DOT | 1,482 | 99 | 1,383 | 83% | 192 | none |
| Hawaii | Hawaii DOT | stale feed | no data | no data | no data | no data | updated 2024-02-22 |
| Idaho | Idaho DOT | 164 | 58 | 49 | 53% | 56 | width, length, weight |
| Indiana | Indiana DOT | 985 | 252 | 733 | 62% | 131 | width, local access, height |
| Kansas | Kansas DOT | 356 | 192 | 130 | 87% | 13 | width, local access |
| Kentucky | Kentucky Transportation Cabinet | 116 | 0 | 116 | 72% | 12 | width |
| Louisiana | Louisiana DOTD | 5 | 0 | 4 | 0% | 5 | none |
| Maryland | Maryland DOT | 57 | 52 | 0 | 75% | 2 | none |
| Minnesota | Minnesota DOT | 451 | 132 | 313 | 60% | 51 | width, length, local access |
| Mississippi | Mississippi DOT | 124 | 22 | 100 | 0% | 0 | none |
| Missouri | Missouri DOT | 641 | 481 | 150 | 0% | 0 | none |
| North Carolina | North Carolina DOT | 363 | 249 | 77 | 77% | 54 | none |
| North Dakota | North Dakota DOT | 65 | 38 | 3 | 68% | 20 | width, height, length |
| Washington | Washington State DOT | 356 | 0 | 356 | 77% | 65 | none |
Lane closures counts events whose vehicle impact is some lanes closed, all lanes closed or alternating one-way. Over 90 days is the share scheduled to run longer than 90 days. Restrictions lists the types present in the feed (width, height, length, weight), most frequent first. Events in effect means start date on or before the retrieval time and end date later than it, or no end date. Each state decides what to publish, so a high count can mean more work or a more complete feed. Do not rank states by this column.
Lane impact: what the feeds say is blocked
Across the 14 fresh statewide feeds, the vehicle-impact field breaks down as below. "Unknown" is common: many agencies publish location and dates but not the lane detail.
Top states by number of events with lane closures or alternating traffic reported.
Where closures bunch up on the interstates
The interstates with the most lane-impact events in a state feed. For a truck, an interstate closure is a detour on a road with no ready alternative.
| Interstate | State feed | Events with lane impact |
|---|---|---|
| I-70 | Kansas | 20 |
| I-135 | Kansas | 16 |
| I-94 | Minnesota | 8 |
| I-65 | Indiana | 7 |
| I-69 | Indiana | 6 |
| I-35 | Kansas | 6 |
| I-94 | Indiana | 5 |
| I-80 | Indiana | 5 |
| I-70 | Missouri | 5 |
| I-40 | North Carolina | 5 |
| I-95 | Maryland | 3 |
| I-90 | Minnesota | 3 |
An event is one record in the feed, usually one work-zone segment. It is not a mile count. Only states whose feeds report lane impact and name the road with an interstate number appear.
Width, height and weight: the fields that stop a truck
Only 105 width values and 6 height values in the whole snapshot carry a number. Most work-zone records say "restriction" with no figure. Where a number exists, it matters.
| Feed owner | Restriction records by type | Width values | Narrowest listed | Height values | Lowest listed |
|---|---|---|---|---|---|
| North Dakota DOT | reduced width 65, reduced height 65, reduced length 65, gross weight limit 65, axle load limit 65 | 26 | 11.0 ft | 4 | 15.3 ft |
| Indiana DOT | reduced width 197, local access only 12, reduced height 2 | 0 | no numeric value | 0 | no numeric value |
| Maricopa County DOT | reduced width 141, reduced height 5, reduced length 2 | 0 | no numeric value | 0 | no numeric value |
| Idaho DOT | reduced width 76, reduced length 5, reduced weight 2, reduced height 2 | 69 | 9.0 ft | 2 | 17.0 ft |
| Minnesota DOT | reduced width 72, reduced length 6, local access only 2 | 0 | no numeric value | 0 | no numeric value |
| Kansas DOT | reduced width 44, local access only 14 | 0 | no numeric value | 0 | no numeric value |
| Kentucky Transportation Cabinet | reduced width 11 | 10 | 8.0 ft | 0 | no numeric value |
Many feeds name a restriction type with no numeric value. Only records with a value in a plausible range (width 6 to 16 ft, height 8 to 20 ft after unit conversion) count as values. Zero values for a state means the feed did not give a number, not that no restriction exists.
| Road | State feed | Width | Direction | Listed end date |
|---|---|---|---|---|
| US-68 | Kentucky | 8.0 ft | eastbound | Jun 15, 2027 |
| SH-97 | Idaho | 9.0 ft | southbound | Oct 17, 2026 |
| US-93 | Idaho | 9.0 ft | northbound | Oct 18, 2026 |
| US-93 | Idaho | 9.0 ft | southbound | Oct 18, 2026 |
| KY-245 | Kentucky | 10.0 ft | northbound | Nov 1, 2026 |
| KY-79 | Kentucky | 10.0 ft | northbound | Nov 30, 2026 |
A standard trailer body is 102 inches, 8.5 feet, wide. Any listed width below that is a place where a normal trailer may not fit. Check the permit or the agency's own restriction notice before you route there.
How long work zones last
Of 5,176 events in effect across the fresh statewide feeds, 3,240 (63%) are scheduled to run longer than 90 days from start to end and 612 end within the next 7 days.
That mix is the useful bit. A zone that has run for months is part of your lane, not a surprise: build it into the rate you quote. A zone that ends this week is not worth a detour. Feeds that list no end date count as in effect until they drop the record, so a long-lived "no end" record may already be gone on the ground.
Calculator: what a work zone costs you
Put your own hourly truck cost on a delay, then compare waiting with a detour.
Example values pre-filled so you can see the arithmetic. Replace each one with your own.
Cost of the delay
enter numbers
- Truck hours lost
- Per truck
- One pass
Formula: trucks x passes x weeks x minutes / 60 x cost per hour. Detour compares one pass of waiting with extra miles x cost per mile. Nothing you type leaves this page.
Which feeds we read, and which we could not
Read in this snapshot:
| Place | Feed owner | Feed last updated | Freshness |
|---|---|---|---|
| Delaware | Delaware DOT | 2026-10-09 | Updated within 7 days |
| Florida | Florida DOT | 2026-10-09 | Updated within 7 days |
| Hawaii | Hawaii DOT | 2024-02-22 | Stale |
| Idaho | Idaho DOT | 2026-10-09 | Updated within 7 days |
| Indiana | Indiana DOT | 2026-10-09 | Updated within 7 days |
| Kansas | Kansas DOT | 2026-10-09 | Updated within 7 days |
| Kentucky | Kentucky Transportation Cabinet | 2026-10-09 | Updated within 7 days |
| Louisiana | Louisiana DOTD | 2026-10-09 | Updated within 7 days |
| Maryland | Maryland DOT | 2026-10-09 | Updated within 7 days |
| Minnesota | Minnesota DOT | 2026-10-09 | Updated within 7 days |
| Mississippi | Mississippi DOT | 2026-10-09 | Updated within 7 days |
| Missouri | Missouri DOT | 2026-10-09 | Updated within 7 days |
| North Carolina | North Carolina DOT | 2026-10-09 | Updated within 7 days |
| North Dakota | North Dakota DOT | 2026-10-09 | Updated within 7 days |
| Washington | Washington State DOT | 2026-10-09 | Updated within 7 days |
| Texas (local feed) | City of Austin | 2026-10-09 | Updated within 7 days |
| several states or local (local feed) | CivicLink | 2026-10-09 | Updated within 7 days |
| Arizona (local feed) | Maricopa County DOT | 2026-10-09 | Updated within 7 days |
| several states or local (local feed) | NHDOT/VTAOT/MEDOT | 2026-10-09 | Updated within 7 days |
| Missouri (local feed) | St. Charles County | 2026-10-09 | Updated within 7 days |
Not read
| Feed owner | Place | Why not |
|---|---|---|
| Iowa DOT | Iowa | Server refused the request (HTTP 403) |
| New Jersey Institute of Technology | New Jersey | Feed returned unreadable data or did not answer |
| New Mexico DOT | New Mexico | Server refused the request (HTTP 403) |
| New York DOT | New York | Feed returned unreadable data or did not answer |
| Oklahoma DOT | Oklahoma | Server refused the request (HTTP 403) |
| Utah DOT | Utah | Server refused the request (HTTP 403) |
| Wisconsin DOT | Wisconsin | Server refused the request (HTTP 403) |
| Colorado DOT | Colorado | Needs its own key |
| Colorado DOT | Colorado | Needs its own key |
| IDOT | Illinois | Needs its own key |
| Illinois Tollway | Illinois | Needs its own key |
| Massachusetts DOT | Massachusetts | Needs its own key |
| Metropolitan Transportation Commission San Francisco | California | Needs its own key |
| Michigan DOT | Michigan | Needs its own key |
| Michigan Department of Transportation | Michigan | Inactive or unsupported format/version |
| National Park Service | Nps | Needs its own key |
| Ohio DOT | Ohio | Needs its own key |
| Oregon DOT | Oregon | Needs its own key |
| Pennsylvania Turnpike Commission | Pennsylvania | Needs its own key |
| PurposeBuilt Systems, LLC | N/A | Inactive or unsupported format/version |
| Quebec City | N/A | Inactive or unsupported format/version |
| Texas DOT | Texas | Needs its own key |
| Virginia DOT | Virginia | Needs its own key |
The USDOT registry lists each feed with a flag saying whether it needs its own key. We did not register for state keys. Where a server blocked or failed our request we say so rather than guess.
What to do with a work-zone feed
- Quote the zone, not the surprise. If a lane you run crosses a zone with a long scheduled end, add the delay minutes to your rate or your transit time.
- Check restrictions before a wide or tall load. A restriction record without a number is a flag to call the state, not a green light.
- Count the hour. Delay hours are truck-hours. The calculator turns them into dollars with your cost per hour.
- Do not use this page for tonight. It is a snapshot. Use the state 511 site or your telematics for same-day routing.
- Charge for delay you cannot avoid. If a work zone makes you late at the dock, document it. Detention and layover rules may apply.
Why this matters for your money
A work zone is a cost you pay by the hour. At the example numbers in the calculator, six trucks losing 20 minutes four times a week for ten weeks lose 80 truck-hours; at $75 an hour that is $6,000 of cost you do not invoice. The numbers are examples, but the arithmetic is yours to rerun with your own cost per hour and the zones on your lanes.
Most carriers feel delay as a late load and a short week, not as a line in the books. When it is not measured it is not priced into rates, so it quietly eats margin on the same lanes again and again. A free audit lays your last loads next to the delay, detention and deadhead that sit behind them.
Questions
What is WZDx?
WZDx is the Work Zone Data Exchange, a USDOT data standard for publishing road work as a machine-readable feed. State and local agencies publish their own feeds and USDOT keeps a registry of them. We read the registry and the feeds that need no key.
Why is my state missing or empty?
A feed may need its own access key, may block automated requests, may not be in the registry, or may not have been updated recently. The Not read table above lists what we could not read and why. Hawaii, for example, is listed as stale if its feed is old.
Can I compare one state with another?
Not by count. Each agency decides what to publish and how to split a project into records. A state with more events may simply publish more detail. Compare a state with itself over time, or use the interstate table for hot spots within a state.
Does a lane closure mean a delay?
No. A closure is a closed lane, not a measured delay. The calculator uses minutes you enter from your own trips. The feed does not measure delay.
Do these records show oversize or permit routes?
Only where a feed publishes a width, height, length or weight restriction. See the width and height section for what the snapshot contains and its limits. For permits and bridge limits, see the road restrictions page.
Related guides and tools
- Road restrictions: oversize, overweight and permit links by state
- Bridge conditions: structurally deficient bridges by state
- Truck parking: where parking is tight
- Detention pay: when a delay at the dock is billable
- Deadhead miles: the cost of a detour in empty miles
- Cost per mile calculator: find your own cost per hour and per mile
- Intelligence hub: all the open-data pages in one list
Where the numbers come from
See what your last 20 loads show.
One short form. We reply by email with the next step, and a one-page report follows. Free, no obligation.
Mon-Fri, 9:00 a.m.-5:00 p.m. Eastern Time (Raleigh, NC). Voicemail is answered the next business day.