Tech
Riders Waited for Buses That Never Came
WRENFIELD, Ont. — November 20, 2026 — The 7:10 bus to the hospital never came. Neither did the 7:25, or the 7:40. By 8 a.m., forty people were standing at the shelter on Cedar Street in minus twelve degrees, watching a screen that kept promising a bus in three minutes.
Rosa Delgado, 41, is a personal support worker. She takes the Number 4 to her first client of the day, an elderly man who needs help getting out of bed. She waited an hour and ten minutes.
“The screen said three minutes, then two minutes, then three minutes again,” she said. “It kept counting down and starting over. I called the office and nobody answered. My client waited in bed until ten. He is eighty-nine. He cannot get up on his own.”
Wrenfield is a fictional Ontario city of about 22,000 people, and its buses run on a real-time system. Riders check an app called RideWrenfield, or the screens at the shelters, and the app tells them where each bus is and when it will arrive. The times come from a live feed — a stream of location data sent from every bus, every few seconds, to a company called ClearRoute, which turns it into the arrivals riders see.
On Tuesday morning, the feed was lying. Buses that were sitting in the depot showed up on the app as three minutes away. Buses that were actually running showed up as cancelled. And buses that did not exist at all appeared on the schedule, gliding toward stops they would never reach.
Nobody at Wrenfield Transit noticed for the first two hours, because the dashboard in their own office reads from the same feed. Everything looked normal from the inside. It was the riders, standing in the cold, who knew something was wrong.
Elena Marsh, 58, missed a dialysis appointment she had waited three weeks for. Tom Okafor, 29, was two hours late for a job interview at a warehouse on the edge of town — his second interview in a month, and his last chance before his benefits ran out. A group of high school students waited forty minutes for a bus to their exams, then gave up and walked two kilometres through the snow.
“The app is the timetable now,” said Dana Whitaker, Wrenfield Transit’s operations director. “We took the paper schedules out of the shelters two years ago because everyone had the app. On Tuesday, the app told people a bus was coming, and people believed it, because it had always been right. Nobody had a backup plan, because nobody thought the timetable itself could be wrong.”
ClearRoute says someone got into the feed through a key — a long password that lets a computer system talk to another computer system — that had been left inside a public code repository by a contractor three years ago. The key was never changed. With it, anyone could send fake bus locations into the feed, and the system accepted them without checking whether the bus was real, whether it was on the road, or whether it was even in the city.
The buses were never hacked. The map was.
“It was not the buses that were broken,” said Dr. Lena Osei, a fictional researcher who studies how cities depend on software they do not own. “The buses were fine. The drivers were fine. What broke was the story the city tells its riders about where the buses are — and that story now comes from a feed the city does not control, protected by a key the city did not know was public. When the story is wrong, people stand in the cold waiting for something that is not coming, and they have no way to know.”
Wrenfield Transit says the feed is fixed, the key has been changed, and the paper schedules are going back into the shelters this week. ClearRoute says it is now checking every location against the bus’s real GPS and its assigned route before it appears on the app, and that any location that does not match will be flagged instead of displayed. The city says it will keep a phone line staffed during morning rush from now on, so riders can call a person when the screen does not make sense.
For the riders who waited on Tuesday, the fix comes too late for the appointments they missed. The bus they needed was never late. It was never there at all.
Across Canada, small cities have replaced paper timetables with live apps, because a live app is cheaper than a printed schedule and easier than a phone call. The convenience is real. So is the trade: the arrival time on the screen now comes from a data feed the city does not run, protected by a key the city may not know exists. When that feed is wrong, the riders keep waiting — and the buses keep not coming.
Lessons Learnt
- Treat every data feed like a door — and check who holds the key. If your app, your screens, or your website show live information from another company’s system, ask which keys and logins can change that feed. Rotate them regularly, and close any that belonged to a contractor whose work ended years ago.
- Check the data against reality before you show it. A bus location should match the bus’s real GPS, its route, and its schedule. If a feed says a bus is three minutes away for an hour, or a bus appears that does not exist, the system should flag it — not display it with confidence.
- Keep a backup riders can actually use. Paper schedules in the shelters, a staffed phone line, and a text-message alert cost little next to a live app. When the screen goes wrong, people need a second source of truth, not a second screen reading the same broken feed.
- Watch for the quiet failure, not just the outage. The app never went down on Tuesday. It kept working, and it kept lying. Monitor your feeds for impossible data — buses in two places at once, arrivals that never arrive — and alert a human the moment the numbers stop making sense.
Watching the perimeter — and what slips past it.
ODTN News note: ODTN.News is a fictional news platform set within the Operation: Defend the North universe. All names, organizations, quotes, and events in this article are entirely fictitious. Any resemblance to real people, companies, or incidents is purely coincidental. The cybersecurity challenges it represents are very real.