This article is from the source 'guardian' and was first published or seen on . It last changed over 40 days ago and won't be checked again for changes.
You can find the current article at its original source at https://www.theguardian.com/australia-news/2017/jul/13/melbournes-peak-hour-trains-at-a-standstill-after-computer-glitch
The article has changed 5 times. There is an RSS feed of changes available.
Version 0 | Version 1 |
---|---|
Melbourne train services resume after IT glitch brings network to a standstill | |
(about 2 hours later) | |
Melbourne’s train services have resumed after a network wide technical glitch, but long delays are expected as thousands of commuters try to squeeze aboard. | |
A computer fault shut down every rail line at the start of peak hour, leaving passengers stranded between stations and on platforms. | |
Services resumed shortly after 5.30pm, but Metro Trains was still warning commuters to allow for extra time and to defer travel where possible. | |
The peak hour debacle also affected Melbourne’s tram networks, with Yarra Trams also saying “high demand” was contributing to major delays.Uber prices skyrocketed, with a five-minute trip – which would usually cost about $8 to $10 – shooting up to about $43. | |
Commuters were not impressed with the delays and many took the opportunity to vent on social media or poke fun. | |
Update: Services are now running. In other capital cities, that is. Not Melbourne. #MetroTrains | |
Leaked footage of #MetroTrains attempting to get their system back online. pic.twitter.com/kWspagMrLz | |
You had one job @metrotrains #MetroTrains pic.twitter.com/vR67V2gmQz | |
It is believed the TCMS, the network’s automated control centre, was behind the failure with controllers left staring at blank screens when it went offline. The trains were required to halt for safety reasons as controllers had no way of knowing where they were. |