London line status (TfL)
Each London Tube, Overground, Elizabeth line, DLR and tram line and its status as Transport for London publishes it (good service, delays, closures), with TfL's reason.
Three layers: the source (who publishes it, the terms, when it was read), the raw data as the publisher served it, and the processed data, what this site makes of it. The processing is where the value is: named fields, places joined, gaps marked, every value kept with its source and time.
1. The source
At a glance
| Field | Value |
|---|---|
| Publisher | Transport for London (TfL), Unified API |
| Source | https://api.tfl.gov.uk/ |
| Reader page | https://api-portal.tfl.gov.uk/ |
| Schedule | daily: once a day at data.b@'s morning wake (when the last read is more than 23.5 hours old): one GET of api.tfl.gov.uk/Line/Mode/.../Status, no key; the page reads it live in the browser |
| Owner | data.b@PrompTugal.dinis |
| Collector | sources/tfl-status/collect.mjs |
| Since | 2026-11-21 |
| Last read | 2026-11-21 09:20 UTC |
| Last run | ok: 1 requests ok, 0 failed |
| Now | 20 lines |
| Licence | The data: TfL Transport Data Service terms (OGL v2.0 based) (Transport for London). This page, the card and the records we add: CC BY 4.0. |
Reuse terms
TfL's Transport Data Service terms (based on the Open Government Licence v2.0 with TfL amendments): free to copy, publish, distribute, transmit and adapt the information and to exploit it commercially and non-commercially; credit "Powered by TfL Open Data"; at most 500 calls a minute per feed; no implied endorsement. Reuse: yes, with the credit "Powered by TfL Open Data"; commercial use allowed.
You are free to: Copy, publish, distribute and transmit the Information; Adapt the Information and Exploit the Information commercially and non-commercially
2. The raw data
The raw answer is TfL's line status list (about 30 KB), kept in the vault copy: the address.
3. The processed data
The collector reads TfL's status for the Tube, Overground, Elizabeth line, DLR and tram once a day and keeps each line's name, mode, status, severity, reason and period. Powered by TfL Open Data. The result: latest.json.
Each line and its status at the read. The live status is on London, live. The data: /api/v1/tfl-status/latest.json.
More about this source
What runs by code, by agents and by people
Code
- the collector reads the source once a day and keeps the archive; the page reads the live figures in the visitor's browser
Agents
- data.b@PrompTugal.dinis wrote the collector and card on 21 November 2026, for Dinis's London demos (tier 1 of board/team/data/london-feeds.md)
People
- Dinis Cruz chose tier 1 on 21 November 2026, about 09:16 UTC; no person has checked the values (not reviewed)
Cost
| Field | Value |
|---|---|
| per run tokens | 0 |
| per run model cost usd | 0 |
| runner | data.b@'s session |
| build tokens | not measured |
| note | Code only: no model is called when the data is collected. |
API addresses
These addresses stay for the life of v1 (the contract).
curl -s https://data.promptugal.news/api/v1/tfl-status/latest.json
curl -s https://data.promptugal.news/api/v1/tfl-status/reads.json | head -c 600
Vault
Vault not yet created. The collector writes the bytes of each read to a vault copy; until the vault exists they are not kept.
Last runs
| Time (UTC) | Requests ok | Requests failed | Reads with changed bytes |
|---|---|---|---|
| 2026-11-21 09:20 UTC | 1 | 0 | 1 of 1 |
Showing 1 of 1 runs kept. Full detail with sha256: reads.json.
Preview of the values
The first 5 of 20 entries in lines, as read 2026-11-21 09:20 UTC. Source: https://api.tfl.gov.uk/. Long values are shortened here; the file has them whole.