News and Announcements2025-06-17T22:15:48-04:00

News and Announcements

This page provides the latest news and updates regarding DEP functionality and data, as well as known issues and data outages. Check back frequently for updates.

Last updated: June 17, 2025

Sign up today to receive email notifications of RM3P news and announcements

January 31, 2024 – Real-Time NWS Weather Alerts Unavailable [Resolved on 4/30/2024]

On January 31, 2024, the DEP automated monitoring system detected an outage caused by National Weather Service (NWS) change to their API for the NWS Weather Alerts. This change resulted in NWS Weather Alerts no longer being ingested into DEP and no longer available in the DEP API in real-time. Historical data prior to January 31, 2024, is still available in the DEP. The current resolution time is unknown.

January 18, 2024 – VDOT Environmental Sensor Stations Metadata Corrected

On January 18, 2024, VDOT corrected the Environmental Sensor Stations (ESS) metadata to properly geolocate stations by repairing the order of the latitude/longitude values in metadata.

November 30, 2023 – New Precipitation on Roadway Data Set Now Available

As of November 30, 2023, the DEP API now includes precipitation on roadway data set expressed as precipitation rate per roadway segment.

October 20, 2023 – Transurban Detector Data Outage [Resolved on 2/15/2024]

Starting around October 20, 2023, the DEP automated monitoring system detected a drop in the number of detector data records arriving to DEP resulting in less than 1% of expected data being available in DEP. Transurban resolved the issue on December 3, 2023. Currently there is a gap in Transurban detector data for this time period. Transurban has provided a backfill that is expected to be processed and DEP gap eliminated by February 16, 2024.

June 29, 2022 – Transurban Detector Timestamps Issue [Resolved on 6/15/2024]

Some of the Transurban Express Lanes detector start and end timestamps are not set correctly. Transurban has identified the root cause and is working to resolve this reported issue. In the meantime, a DEP API user has suggested that using 60-second interval between detector start and end timestamps is a generally accurate assumption for most use cases.

Go to Top