Live Alerts
Live incidents near your scheme cameras
Priority alerts
Ranked by danger, confidence, then newestQueues
Longest delay first. Click one to find it on the map.Lengths and speeds come from live traffic data, updated every 2 minutes. A delay marked "about" is worked out from the queue's length and speed against this scheme's normal speed of 50 mph.
Traffic flow
Contains National Highways data.
Total queue length
Delay
Day by day
Every day as a table
| Day | Time with a queue | Longest queue | Longest delay |
|---|
Traffic flow
| Road and direction | Vehicles counted | Busiest hour | Over 6.6 m | Average speed | Counter |
|---|
Contains National Highways data. Counters measure vehicle length, not type: "over 6.6 m" is lorries, buses and coaches.
By road
Click a road to see it on its own.
| Road | Time with a queue | Longest queue | Longest delay |
|---|
Readings
| When | Road | Length | Speed | Delay |
|---|
Readings come from live traffic data, saved every 2 minutes since 9 October 2026. Delays are estimates, worked out from each queue's length and speed against the scheme's normal speed at the time.
Schemes
System health
What is actually working, not just whether this page loaded. Refreshes on its own every 30 seconds.
What these mean
- Dashboard server
- The thing serving this page. If this is down you would not be reading it.
- Alert collector
- The separate program that polls for incidents. It runs on the server alongside the dashboard and restarts itself if it crashes. If it stops, the board freezes and looks calm rather than broken. This is the one worth watching.
- Traffic data feed
- The live traffic data feed. A fault here means it is not answering our requests, so nothing new arrives however healthy everything else looks.
- Latest alert
- Age of the newest incident. Quiet roads look the same as a broken feed, so read this next to the two above rather than on its own.
- Schemes being watched
- How many schemes are enabled. A disabled scheme is not polled at all.
Accounts
Anyone can request an account, but nobody can sign in until you approve it and choose which schemes they see. An operator with no schemes allocated sees an empty board, so allocate schemes at the same time as approving.
Add a scheme from a camera schedule
Add a new job by uploading a list of its cameras. Every camera is shown on a map for you to check before anything is saved. Existing schemes are never changed.
How to fill in the camera list
- Download the template and open it in Excel.
- Leave row 1 (the headings) exactly as it is. Delete the three example rows underneath.
- Add one row for each camera:
Column What to type Example scheme The job name. The same on every row. A38 Derby Junctions camera The camera name or number. CAM 1 road The road the camera is on. A38 marker post The nearest marker post, ending in its letter (A or B). P224/7A latitude
longitudeLeave empty. Only fill these in for a camera with no marker post. 52.91234
-1.47890 - Save it: File → Save As, and for the file type choose CSV (Comma delimited) (*.csv). If Excel warns about losing features, click Yes.
- Choose the file below. Check the pins on the map, drag any that are in the wrong place, then press Create scheme.
Marker posts need the letter on the end. P224/7 will not be found, P224/7A will. The letter is printed on the post: A and B are the two sides of the main carriageway. Not sure which side? Use A. The pin lands a few metres away and you can drag it across.
The road must be the road the marker post is on, for example M5, not the junction or a nearby road.
If it says the headings are missing, the file was not saved as CSV (Comma delimited), or row 1 was changed. Save it again as in step 4.
| Camera | Road | Marker post | Status |
|---|
Green came from the marker post, amber wants a look, teal you positioned yourself. Drag any pin to correct it.
Existing schemes
Cameras
Drag a camera to move it, or type a new marker post in the table (with its letter, like P224/7A) and press Enter to move it there. Click Add camera then click the map to put a new one down. The shaded circle is the alert radius, so an incident has to fall inside one of these to reach the board.
Two is the usual setting and filters out one-off false alerts. Drop it to 1 on a quiet road, where a real incident may only ever be confirmed once, at the cost of letting more noise through. Leave blank to use the default.
Alerts on any other road are rejected before they reach the board, even if a camera happens to be close by. Leave this blank to accept everything, which is how it behaves now.
Used on Congestion Maps to work out the delay: the time through a queue at its current speed, compared with driving the same stretch at this speed. Set it to the limit through the works, for example 40, 50 or 60. Leave blank for 50.
| Camera | Marker post | Position |
|---|
Audit log
Ingest log
Settings
System settings
Visible alert categories
Choose which alert types appear in Live Operations.