Disruption Events

The tube network is continually undergoing maintenance and as a result can be subject to delays and cancellations that between days. When disruptions are known in advance, (this) Disruption service can be queried to list them. Additionally, this service can also be queried to list all the disruptions that are occurring today or on a previous day.

There are two kinds of disruptions; delays through stations and delays when travelling between two particular stations. Both events serve to increase the travel time of any journey that looks to use the affected portion of the tube network:

• Delays to a station increase the journey time of all journeys that wish to pass through that station.
• Delays to a portion of the track between stations increase the time of any journey that uses that particular portion of the track.

Disruptions can affect either the whole tube network or only a particular line of the network. In the case of the latter, the statements above still apply, but only to journeys that rely on the affected line.

Querying

Query for the disruptions that are planned for a day in the future, are occurring today, or occurred on a day in the past: /disruptions/query?date=YYYY-MM-DD.

Parameters

• date: The date to check for disruption events. Must be between 2023-01-01 and 2024-12-31 (inclusive). Defaults to the present day if not provided.

Examples

• https://rse-with-python.arc.ucl.ac.uk/londontube-service/disruptions/query?date=2023-09-01 - retrieve the disruption events that occurred on 1st September 2023.
• https://rse-with-python.arc.ucl.ac.uk/londontube-service/disruptions/query?date=2024-09-01 - retrieve the disruption events that are scheduled for 1st September 2024.
• https://rse-with-python.arc.ucl.ac.uk/londontube-service/disruptions/query - retrieve the disruption events occurring today.

Return format

The response is a JSON file containing a list of all disruption events that are planned to taking place on that day (if the date is in the future), or a list of all disruption events that took or are taking place that day (if the date is the present day or in the past).

Events that are included in the response consist of the following fields:

• line: An integer corresponding to the index of one of the tube lines. If the field is present, the disruption event only applies to corresponding line. If the field is not present, the disruption applies to the entire tube network.
• stations: A list of 1 to 2 integer values, that correspond to indices of stations in the tube network. If 1 value is provided, this is a delay to all journeys through a station. If two values are provided, this is a delay to any journey that uses the direct connection between the two stations.
• delay: A numerical value. The usual travel time of the affected portions of the journey should be multiplied by this value to obtain the new travel time because of the delay. A value of 0 describes a closure.

For example, the event

{
    "line": 7,
    "stations": [255, 256],
    "delay": 2
}

means that travel time between stations 255 (Tooting Bec) and 256 (Tooting Broadway) using the Northern line should be multiplied by 2. Whereas the event

{
    "stations": [39],
    "delay": 0
}

means that all edges in the entire tube network connecting to station 39 (Camden Town) should be removed (that is, the station is closed).