Live measured status
District line status
We are not measuring the District line yet. Baselines need weeks of data before a score means anything, and we would rather show nothing than a number we do not trust.
TfL’s reason: District Line: Service will resume later this morning.
Live — last reading . Seven branches in each direction, so a delay on one branch need not mean a delay on yours.
The last 24 hours
Tue 3 Nov 03:40:00 → 03:30:00
Higher is better; the hairline is the threshold below which a line stops counting as running normally. A dashed stretch along the bottom is a period we have no score for, and it says which kind. No service is the small hours, when the line is not running. No data is us: either nothing reached us, or — more often — we had nothing to compare that stretch against, because a line TfL has declared disrupted for long enough loses those hours from what we count as normal. Neither is a delay, and we would rather show the hole than draw a line across it.
Declared against measured
Wed 28 Oct → Wed 4 Nov
- Good
- Minor delay
- Delayed
- Severe delay
- Nothing measured, or nothing running
Across this window, for 8 hours TfL declared a good service while we were measuring a real delay; and for 2 days TfL was reporting disruption that our measurements did not pick up, which is the direction we are likelier to be wrong in. Our band changes only once a condition has held for fifteen minutes, so this is a picture of sustained running rather than every flicker — the chart above is where a short sharp incident still shows. Every other page here asks you to take our word for it; this one is the argument with the evidence attached.
By direction
Towards central London
—
MeasuringNo data
Away from central London
—
MeasuringNo data
One direction can be in trouble while the other runs perfectly, which is exactly what a single line-wide status hides. Platform indicators name the destination rather than the direction — we will too, once the measurement service publishes where each direction ends.