The Virginia DOT account is reporting Road Closures that do not exist. Significantly disrupting routing. The reported maintenance / closure is not true. I am guessing that the Virginia DOT account has been hacked. This has been happening for the last 3 days. Specifically Hwy 15 near Culpeper, VA. I know this personally as I travel that road almost every day, and I traveled that route this morning and yesterday as well. There is no road maintenance and no road closures despite the reporting in Waze from the Virginia DOT account.
I flagged all of the markers as Not There, but it doesn’t appear to do any good. Also, I don’t see a way in the web interface to flag a bad report.
Thank you for this report. I do know our Virginia and regional teams are working through this issue to try to remove as many of the errant closures as possible.
More likely there is an issue with the automated feed of closures that flows from VaDOT to Waze. Either someone has entered information incorrectly or Waze is misinterpreting what VaDOT is sending.
We’ve seen this in other states where a “shoulder closed” gets flagged somehow as “entire roadway closed”
This has been raised with staff and we’re waiting on an investigation
The team is investigating, and has already forced the removal of all existing closures from this feed. It’s a new feed that was just activated on the 5th of August.
We’re getting in contact with the partner now, and won’t reactivate until these issues have been resolved.
It was not a hack according to VDOT, just somehow the feed was turned on and all the alternating closures were set as full closures. Most of the URs for the last two days have been about this problem and I removed about 1800 closures earlier this morning. Thanks for Brett getting the feed paused and then getting the last of the closures pulled.