Report updates · 4 minute read
Is that traffic incident still active?
A report says what someone saw at a particular time and place. A later update may tell a different story. Read the sequence before you decide what the road looks like now.
Find the first report and the newest update
Start with the time the incident was first posted, then check the most recent entry in its story. A recent “still active” observation can be more useful than an old description. But even a fresh update is a snapshot: conditions may change again before you arrive. Compare the road name, direction, and nearby exit or intersection with your own route. A problem a few miles away or on the opposite side of a divided road may have a different effect on your trip.
Look for useful detail, such as which lane is affected or whether traffic is moving past the scene. A bare “still active” can keep a conversation current, but it cannot tell you the length of a queue or whether a road is passable. When details are sparse, treat the report as a reason to check further rather than a prediction of your arrival time.
When the updates disagree
Two people can see different parts of the same event. One driver may pass an open lane while another is still behind the queue. A “cleared” update may mean the hazard has been removed; it does not mean the backup vanishes immediately. Conversely, a report still marked active can be old if nobody nearby has checked it lately. Give newer observations more weight, but keep the difference between the incident and its remaining traffic effects in mind.
Traffic Sonar shows a report’s current status and its story so you can see that sequence. The timeline records community observations; it is not a guarantee that every step has been verified by a road authority. If the status and the latest entry conflict, check another source of current conditions before committing to a long detour.
What the severity label can tell you
Low, moderate, high, and severe labels help sort reports by apparent impact. They do not tell you exactly how many minutes you will lose. The same label can feel different depending on direction, time of day, and where you enter the road. Consider the label alongside the incident type and the latest update. A brief closure on your exact route may matter more to you than a severe slowdown well beyond your exit.
Help the next driver with a useful update
If you are safely stopped and have a recent observation, describe what changed in plain terms: the lane, direction, nearest landmark, and whether traffic is passing. Avoid guessing at causes or identifying people. If a report is inaccurate or abusive, use its flag control instead of repeating the claim. A clear, specific update is easier for someone else to weigh than several taps that say only “active.”
Never stop on a shoulder just to check or post a report. Posted signs, closures, and instructions from responders take priority over anything shown in an app.
Worked example: cleared scene, remaining queue
Imagine a community report posted at 16:10 says two lanes are blocked. At 16:35, another observation says the vehicles have been removed, but traffic is still slow. The newer entry describes a change at the scene; the older entry explains how the queue began. Neither observation establishes an exact travel-time delay now.
When you add an update, describe only the part you observed: “All lanes moving northbound near the exit at 16:35; queue remains behind it” gives more useful context than “everything clear.” These times are an example, not a live report.