Dan416
Senior Member
Yeah since it was a CN issue the Milton trains seemed to be largely unaffected. My 17:55 train departed a few minutes late, but tbh that's pretty normal for that train. But Union itself was packed with delayed passengers today.
|
|
|
GO Transit: Service thread (including extensions)
- Thread starter drum118
- Start date
anb
Active Member
So this is basically the transit version of the Rogers outage that happened last year.
Seriously though after this, there will for sure be some people who will turn away from the train and going back/going to start driving again or carpool. This might be where they pull the 30 min all day service to Bramalea/Unionville and bring back 15 min all day to Oakville and Oshawa to try to win some riders back.
Usually I don't agree with some of your opinions, but this has to be some of the worst luck and now its somewhat understandable.It's not Kitchener. It is literally everything.
werid this usually only happens when I ride
Seriously though after this, there will for sure be some people who will turn away from the train and going back/going to start driving again or carpool. This might be where they pull the 30 min all day service to Bramalea/Unionville and bring back 15 min all day to Oakville and Oshawa to try to win some riders back.
littlewill1166
Active Member
The 17:55 train was cancelled, you were on the 17:25 train leaving 35 minutes late.
It was technically 8-15 minute peak service depending on how you measure it.
Transsee shows the 88c using Highway 115 and Highway 401.
Dan416
Senior Member
That's strange. I was checking gotracker.ca here and there and it didn't mention any Milton line trains being cancelled. And the departure board once I got to Union around 5:30 showed 17:55 and it didn't have any notes that it was cancelled. It just said to go to platform 4 for the 17:55 train. Whereas Lakeshore line departures did mention cancellations and adjustments. All that matters was that there was a train at 17:55.
littlewill1166
Active Member
I'd try claiming the service guarantee, you're probably eligible.
Dan416
Senior Member
On the train they said it applied, which confused me, since the train was only late like 5 minutes from my perspective. Could be why they mentioned it.
Sunnyside
Active Member
… Did GO just run all trains today in the dark then…?
reaperexpress
Senior Member
GO Tracker was completely wrong throughout the crisis. I was following GO Tracker throughout the evening and there was very little correlation between it and the Union departure board. Even the departure board would change the stopping pattern for individual trains from one minute to another.
GO was writing timetables on the fly and assigning trains to it in real time. It was honestly wild to see them writing them in real time in the trip planner. Here's an example of them rewriting the 17:21 schedule, which was originally The PM Peak express to Niagara Falls.
When they put it on the departure board they were still in the process of updating the schedule. The train was still shown as an express train, and for whatever reason the train's return trip from Niagara was partially shown as well.
A few minutes later the new schedule was ready, with all stops to Niagara Falls, and a separate return trip later in the evening. The departure times were mostly copied from the original express train's timetable, which resulted in totally unrealistic travel times from Union to Clarkson. Mimico to Long Branch in 2 minutes would be an average speed of 150 km/h including the dwell at Long Branch. But that didn't matter since the train was half an hour late anyway. The priority was presumably just writing a schedule as quickly as possible with the correct stops.
I can only imagine how hectic it was for GO's planners and dispatchers last night, their workload was probably ten times normal - every train (except perhaps some Milton line trains) had to be manually rescheduled.
For whatever reason, only about half of the changes were making it into GO Tracker and lots of trains simply disappeared off the tracker, though they were in fact still running. My guess is that this is when trains dropped off when they abandoned their original schedule (relative to which they were several hours late), and the new schedule never made it into GO Tracker for some reason.
Last edited:
chrisw
Active Member
Some information from the Star
Jonny5
Senior Member
Some downsteam effects still in play this morning.
crs1026
Superstar
Pretty much, yes. Or the last great hydro blackout.
Perhaps, but they will then encounter highway gridlock and delays because of truck rollovers or fatal accidents, fires, flooding, blizzards, or whatever. GO's reliability is still what it is - pretty good but not perfect.
This event is mostly notable because such events are rare and we are brought to a standstill when they do happen. Hopefully it's a one-of, and appropriate root cause analysis and corrective action happens. Both CN and ML have mutual self interest to not let this get away from them.
First world problem.
- Paul
T3G
Senior Member
turbanplanner
Senior Member
T3G
Senior Member
Well, if such a person does actually exist (which I highly doubt), they are in for a rude awakening next time they find themselves in rush hour traffic on the 401.