Coverage and sources
Know what is behind a traffic report.
Traffic Sonar combines several kinds of road information. Their availability, update schedules and level of detail differ. A blank map is not proof that every road is clear.
Community observations
Signed-in users can report road events they observe. Their usefulness depends on people being nearby and sharing accurate, recent details. Reports can be incomplete or mistaken. Review the road, direction, original report time and later updates before deciding whether a report applies to you.
Live provider traffic
Signed-in features use TomTom for traffic and location or routing services. Provider incident detail varies by road and area. The live map and a scheduled briefing answer different questions: one shows available current conditions, while the other reflects conditions when the briefing was generated. Neither guarantees what you will encounter later.
Regional transportation feeds
Supported state feeds supplement other information with road incidents or closures in their jurisdictions. They do not provide identical coverage in every state, and an agency feed may cover major highways more fully than local streets. Check the source label and any agency link on the incident instead of assuming all events came from the same provider.
The app's data attribution page identifies its providers. State-feed availability can change as a source becomes unavailable or an integration is updated. Traffic Sonar is independent of the transportation agencies whose data it displays.
State feed coverage
These integrations supplement community reports and live provider traffic. This list describes sources supported by the app, not a real-time feed health report. Availability on an individual screen depends on its location, sign-in requirements and the source response.
Ohio: Ohio DOT / OHGO
Ohio information includes official incident and construction reports and sensor-based travel delays on monitored roads. A construction event and a sensor delay describe different things: the first identifies road work, while the second describes travel conditions where monitoring is available. A local street without a sensor delay is not necessarily uncongested.
Look for the Ohio DOT / OHGO label when reading a report. Use the official OHGO site to check the agency's view when planning an Ohio trip. Ohio DOT does not endorse Traffic Sonar.
Virginia: Virginia DOT
The Virginia integration uses VDOT incident information through SmarterRoads. Check the road, direction and event description rather than interpreting one marker as a statewide traffic summary. An incident record may explain an obstruction without describing every nearby queue or side street.
Look for Virginia DOT as the source. Check 511 Virginia for the agency's travel information. Data may be delayed, incomplete or inaccurate. Traffic Sonar is independent of VDOT and is not endorsed by it.
Massachusetts: MassDOT
The MassDOT Highway Division roadway-event feed covers MassDOT highways. It does not include every incident in Massachusetts. If you see no agency marker on a local road, do not interpret that as confirmation that the road is unaffected.
Look for MassDOT as the source and compare the event's direction and time with your trip. For the agency's view, visit Mass511. Traffic Sonar is independent of MassDOT and is not endorsed by it.
Colorado: CDOT / COtrip
The Colorado integration displays COtrip incidents originated by CDOT or the Colorado State Patrol. A periodically refreshed copy means a source change may not appear immediately. Read the source agency and event description before deciding whether it applies to your road and direction.
Look for the Colorado source label and check the official COtrip map for the agency's current information. The app's data attribution page provides the Colorado source notice. CDOT does not endorse Traffic Sonar.
Utah: UDOT Traffic
Reports are labeled UDOT Traffic / ADX or UDOT Traffic / UT-Construction. UDOT publishes both sets of records. The original reporting sources behind ADX have not been verified. See the Utah data attribution.
Other supported state sources
- California: Caltrans lane-closure information and CHP public incident summaries are separate feeds. A lane-closure record is not a complete account of every crash or delay, and CHP filters its public summaries. Check the specific Caltrans or CHP label.
- Nevada: Nevada 511 supplies NDOT-origin events and road conditions. Traffic Sonar filters the events by source; the displayed records are not every item available from every organization.
- Oregon: TripCheck reports come from ODOT and verified local public agencies, credited on the report. Traffic Sonar uses a periodically refreshed copy, so a recent source change may take time to appear.
- Washington: WSDOT highway alerts supplement other reports. A periodically refreshed copy can be delayed; an absent highway alert does not rule out a local problem.
- Arizona: AZ511 provides ADOT Event Reporting System records. Traffic Sonar filters for verified ADOT sources and excludes recurring events whose schedules cannot be resolved. Those filters can make the app's selection different from the agency's full view.
- Alaska: Alaska 511.
- Georgia: Georgia 511 GA-Events.
- Idaho: Idaho 511 ERS notices.
- Kentucky: KYTC roadwork and closure notices.
- Maine, New Hampshire, and Vermont: New England Compass agency reports.
- Maryland: MDOT CHART incidents.
- New Mexico: NMRoads roadwork and closure notices.
- North Carolina: DriveNC events and notices.
- North Dakota: NDRoads alerts and closures.
- Pennsylvania: PennDOT / 511PA reports.
- Wisconsin: WisDOT / 511WI events and work zones.
- TRANSCOM region: Eligible government road-agency incidents.
For states not listed here, do not assume a dedicated state-agency integration is available. Community and provider coverage is separate. Follow current signs and road conditions, and use the source link on a report when you need to compare details.
Why a map can look empty
- You are browsing as a guest: provider traffic requires sign-in.
- There are no available community observations in the displayed area.
- Your map position or filters exclude the relevant event.
- Location permission is unavailable, or a source request failed.
- The incident has not reached the source yet, or was removed after an update.
Before relying on an empty view, confirm your location, filters and account state. If loading fails, try again when connected. Do not treat missing data as a traffic-safety assurance.
Example: two markers on the same road
A community marker might describe a lane blocked near an exit, while an agency marker describes a longer work zone. These may overlap without being duplicates: the source, affected direction and observation time can differ. Read both descriptions before choosing which one matters to your trip.
Coverage correction
If a source label or location appears wrong, send a correction with the road, direction, approximate time and a screenshot with personal details removed.