TTC Service Alerts & Closures

Live TTC service status

Checking the live TTC feed…

How TTC alerts work

Every line has one of three states: good service, delays, or no service. No service covers an unplanned outage and a line closed for the night alike, because either way there is no train to board; the alert itself says which. Behind the board sit the individual alerts: no-service, delay, detour and construction notices, each naming the line and, where the TTC gives them, the stations affected.

Reroute reads the TTC’s own alerts service first, with the standard GTFS-realtime feed behind it. The two are merged rather than substituted, so an outage on one feed cannot hide an alert on the other, and when Reroute has to fall back it flags the board as degraded instead of passing old data off as live.

Planned subway closures

Planned closures are announced ahead of time, which is why “TTC closures this weekend” is worth checking before a Saturday trip. Reroute lists a planned closure as an upcoming closure until it starts, and it never changes a line’s status or your trip plan early. Once the closure begins it becomes a live alert everywhere at once: on the board above, on the map, and in route planning.

Each line’s own page lists its stations in order, which is the quickest way to see where a closed stretch starts and ends: Line 1 Yonge–University, Line 2 Bloor–Danforth, Line 4 Sheppard, Line 5 Eglinton, Line 6 Finch West, or all of them on the TTC subway map.

TTC delays: today versus the usual

The board above is today: what the feed says right now. For how a line usually behaves, each line page carries a delay-risk read built from real TTC incident history. It is a relative index, how a line’s delay risk compares to a typical trip, and never a percentage chance that your trip is late.