In a 2026-10-08 feature for The Daily WTF, Remy Porter describes an incident reported by Robert G. A carriage assigned to Robert’s booked train was not scheduled to continue with that service. The replacement carriage missed its planned arrival, leaving him at a station and forcing a new booking.

In a region with a strong rail network, the disruption added about 30 minutes to a journey lasting several hours. Robert used the operator’s app to reserve a place on the next train, received confirmation, and waited with coffee. Less than 30 minutes later, he boarded and found another passenger at the assigned seat.

Both passengers showed app confirmations, then email confirmations with fuller details. Each document named the same seat, and both reservations carried exactly the same timestamp to the second. The train had enough open seats for everyone, so they did not share the seat.

Porter identifies the likely defect as a basic race condition. Separate requests can check that a seat is free before either request records the booking, then both can create reservations. The system apparently kept two reservation records, so one did not replace the other. Porter questions why a problem likely to recur has not been fixed. Two explanations seem equally plausible: the operator either tolerates the failure or carries a software backlog where this bug ranks low. That reasoning stays speculation.