M32 traffic: Latest on motorway delays after police incident and crash

The M32 closed early this morning
Watch more of our videos on Shots! 
and live on Freeview channel 276
Visit Shots! now

A police-led incident closed the M32 in both directions this morning - leading to long queues from the turn-off from the M4 and on the A4174 as motorists looked for other routes into the city centre.

National Highways confirmed the road was closed shortly after 6am this morning. It closed at Junction 3 for St Pauls, before reopening at around 7.30am.

Hide Ad
Hide Ad

In a separate incident, there was also an accident between Junction 1 for Filton and Junction 2 for Eastville this morning. All lanes are now open - however, there was heavy congestion wth two miles of queues, warned Highways England.

In a tweet at 7.30am, it said: “All lanes are now running on the #M32 southbound between J1 #Filton and J2 #B4469#Eastville following an earlier collision. There are 2 miles of congestion following this incident so please allow time for these delays to clear.”

At 8am, the body tweeted an update on the earlier M32 closure. It said: “Police led incident has now cleared and the road has reopened in both directions on the #M3 within J3 #Bristol#A4320. Delays should now start to ease. Have a safe onward journey.”

There is congestion leading up to Junction 3 on the southbound of the M32There is congestion leading up to Junction 3 on the southbound of the M32
There is congestion leading up to Junction 3 on the southbound of the M32

Just after 9.30am, Inrix shows traffic is struggling to recover, stating: “Slow traffic due to earlier police incident on M32 in both directions at J3 A4320 Easton Way (St Pauls). Congestion to southbound to J2. All lanes have been re-opened.

“Traffic is still struggling to recover, not helped by usual rush hour delays.”

More to follow

Related topics:

Comment Guidelines

National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.