Five-hour REM outage traced to equipment failure and truck strike near Gare Centrale
If you rode the REM this week, you likely sat through one of the longest service disruptions since the light-rail network opened. A five-hour outage hit the system after an equipment failure combined with a truck striking the REM viaduct near Gare Centrale, according to reports citing Radio-Canada. Trains slowed or stopped between Côte-de-Liesse and Deux-Montagnes, leaving commuters stranded during a window that stretched across both midday and evening travel.
The dual cause, a mechanical failure paired with a structural strike from a truck, sets this incident apart from routine delays. Pulsar, the operator owned by CDPQ Infra, confirmed the disruption and gave an explanation for what it called a communication outage affecting signal systems.
Key takeaways
- Check REM’s real-time status page or the Transit app before heading to Gare Centrale-area stations, since the network gives no advance warning for equipment-related stoppages.
- Build in a 20 to 30 minute buffer if you rely on the Côte-de-Liesse to Deux-Montagnes segment during peak hours, given the corridor’s exposure to viaduct-level incidents.
- Keep a backup route in mind, such as the 747 bus or a downtown-bound commuter train, for days when REM alerts mention “equipment failure” or “signal issue.”
- Report elevator or accessibility equipment problems immediately through the REM customer service line, since outages like the Édouard-Montpetit elevator failures have gone unresolved for extended periods.
- Track REM’s published reliability figures if you depend on the line daily. Recurring breakdowns suggest riders should treat published on-time percentages as directional, not guaranteed.
What happened: timeline of the equipment failure and truck collision at the viaduct
The disruption began when a truck struck the REM viaduct near Gare Centrale, according to Radio-Canada’s reporting. The collision happened at a location where the elevated guideway crosses over a roadway, a structural pinch point that has drawn scrutiny before in discussions about the network’s exposure to vehicle traffic below.
Shortly after, an equipment failure compounded the problem. Pulsar has not detailed whether the truck strike caused the equipment issue directly or whether the two events were coincidental, but the timing meant crews had to address both a physical impact assessment and a system-level malfunction at the same time. That combination stretched recovery time to roughly five hours, an unusually long window for a network built around frequency and automation.
Service impact between Côte-de-Liesse and Deux-Montagnes
Trains on the Deux-Montagnes branch bore the brunt of the slowdown. Riders reported extended wait times and reduced service frequency between Côte-de-Liesse and Deux-Montagnes, the northern leg of the REM network that serves commuters heading into and out of downtown Montreal. Some trains ran at reduced speed through the affected zone as crews inspected the viaduct and worked to restore signal communication, while others were held at stations until Pulsar cleared the segment for normal operation.
For riders trying to reach Gare Centrale during the outage, the practical effect was longer commutes layered on top of uncertainty, since REM’s app and station displays did not offer a clear estimated resolution time for much of the disruption window.
Pulsar’s explanation for the communication outage
“There was an equipment failure that affected our communication systems,” a Pulsar spokesperson said in comments reported by Radio-Canada, describing the incident as a signal-related outage rather than a total system shutdown.
That framing matters for how you interpret the disruption. A communication outage in a driverless system like REM doesn’t just slow trains down. It can force the network into a cautious, reduced-speed mode as a safety default, since trains rely on constant data exchange with control systems to maintain spacing and speed without a human operator on board.
What the CDPQ Infra-owned operator said about signal and system recovery
Pulsar said crews worked to restore full signal communication across the affected segment before returning trains to standard operating speed, according to the same Radio-Canada report. The company did not specify what triggered the initial equipment failure, nor did it confirm whether the truck strike on the viaduct played a direct role in the communication breakdown. Full recovery took approximately five hours from the first reported issue to normal service resumption.
A pattern of recurring breakdowns on Montreal’s REM network
This is not the first extended outage on the REM, and that context matters for anyone weighing whether to depend on the line for time-sensitive travel. The network has faced a string of flagged incidents since launching its initial segments, including mechanical issues and accessibility equipment failures at several stations.
Previous incidents: Édouard-Montpetit elevator failures and other flagged outages
The Édouard-Montpetit station, one of the deepest transit stations in North America, has dealt with elevator failures that left riders with mobility needs without a functional way to reach platform level. Given the station’s depth, an elevator outage there is not a minor inconvenience. It can mean the difference between using the station at all and having to route around it entirely. Other flagged outages across the network have included signal disruptions and shorter equipment-related delays, though the five-hour Gare Centrale incident stands out for its duration and dual cause.
What reliability data suggests about the network’s first years of operation
Early-stage reliability issues are common for new transit systems, particularly ones built around full automation like REM. But the frequency of flagged incidents, including elevator outages at Édouard-Montpetit and signal failures near Gare Centrale, suggests a pattern rather than isolated bad luck. Riders and transit watchers have started referring to these events collectively as REM’s recurring breakdowns, a label that reflects accumulated frustration more than a formal designation from CDPQ Infra or Pulsar.
The table below compares the two most recent high-profile incidents by cause, duration, and affected segment, based on available reporting.
| Incident | Cause | Duration | Affected segment |
|---|---|---|---|
| Gare Centrale viaduct disruption | Equipment failure plus truck strike on viaduct | Approximately 5 hours | Côte-de-Liesse to Deux-Montagnes |
| Édouard-Montpetit elevator failures | Mechanical/accessibility equipment breakdown | Extended, recurring | Édouard-Montpetit station access |
Why light-rail automation makes REM vulnerable to single points of failure
REM runs without onboard operators, which means the system depends entirely on centralized signal and communication infrastructure to keep trains moving safely. When that infrastructure fails, as it did in the Pulsar communication outage this week, there’s no human driver to fall back on for manual operation across the affected segment. Trains either slow down dramatically or stop, because the automated system defaults to caution rather than risk.
This is a structural trade-off, not a flaw unique to REM. Fully automated metro systems in cities like Vancouver and Copenhagen have faced similar vulnerabilities, where a single equipment failure at a critical node can ripple across an entire line. The difference is that REM is still in its early operational years, and each high-profile outage adds to a public perception that the network hasn’t yet worked out those single points of failure.
Commuter and business impact across the affected corridor
Commuters between Côte-de-Liesse and Deux-Montagnes lost hours during the disruption, with some riders switching to buses or rideshares to reach downtown appointments and workplaces near Gare Centrale. For businesses in the immediate area, particularly retail and food service tenants inside Gare Centrale itself, reduced foot traffic during the outage window translated to a measurable dip in midday and evening customer volume, though no official figures on lost revenue have been released.
Employers with staff commuting from the Deux-Montagnes corridor also felt the effect indirectly, as employees arrived late or had to leave early to avoid compounding delays during evening peak hours.
What REM and Quebec transit authorities are doing to prevent repeat disruptions
CDPQ Infra and Pulsar have not published a detailed corrective action plan specific to this incident as of this report. Given the pattern of recurring breakdowns, riders and local officials are likely to push for clearer public disclosure around root causes, particularly whether the truck strike near Gare Centrale points to a broader need for protective barriers or clearance signage at viaduct crossings elsewhere on the network.
Until REM publishes a formal reliability report addressing both the equipment failure and the structural risk from vehicle traffic near its viaducts, your best protection as a rider is building flexibility into your commute and monitoring service alerts directly through Pulsar’s channels.
Frequently asked questions
What caused the REM disruption near Gare Centrale?
A combination of an equipment failure affecting communication systems and a truck striking the REM viaduct near Gare Centrale caused the disruption, according to Radio-Canada’s reporting on Pulsar’s statements.
How long was REM service disrupted this time?
The disruption lasted approximately five hours, with service slowed or stopped between Côte-de-Liesse and Deux-Montagnes during that window.
Is the REM known for frequent breakdowns?
The network has faced multiple flagged incidents since launch, including elevator failures at Édouard-Montpetit station and prior signal-related outages, which riders and transit observers describe as a pattern of recurring breakdowns.
What is Pulsar’s role in operating the REM?
Pulsar, owned by CDPQ Infra, operates the REM network and is responsible for day-to-day service, including responding to equipment failures and communicating status updates to riders.
Are REM’s equipment failures linked to a design or maintenance issue?
Neither Pulsar nor CDPQ Infra has confirmed a specific design or maintenance root cause for this incident. The recurring nature of outages across the network, however, has raised questions among riders about whether current maintenance schedules and infrastructure protections, such as viaduct clearance near roadways, are sufficient for a fully automated system still in its early years of operation.