What it shows
Where the [anomaly engine](/docs/anomaly-engine) judges one shipment, the congestion radar looks across many: when a lane or hub starts running slower than its own recent norm, that is a signal worth seeing before your next booking. It surfaces on [/network-status](/network-status) as a live read of where slowdowns are building.
Where it comes from
The radar is built from TrackJet's own observed transit times — the same anonymous corpus behind the [delivery forecast](/docs/delivery-probability). A lane "lights up" when its recent transits drift above its established baseline by a meaningful margin. There is no purchased congestion feed underneath; this is signal we can stand behind because we measured it.
How to read it
Treat it as a leading hint, not a control tower. A flagged lane means recent shipments on it have been slower than usual — useful for choosing a routing or setting a customer expectation. It does not tell you the cause (weather, labour, customs, capacity), and an un-flagged lane is not a guarantee of speed.
Honest limits
The radar can only see lanes TrackJet has enough recent data on. Thin lanes don't appear — absence on the radar means "not enough signal", not "all clear". And like every estimate here, it is descriptive of what we have observed, never a promise about your specific box. For per-shipment timing use the [delivery forecast](/docs/delivery-probability); for a calendar-driven border risk see [customs friction](/docs/customs-friction).