Severn Trent issue apology in response to Stourbridge burst main
The water company has apologies to customers around their loss of water and has said it is working to get the issue resolved as soon as possible.
An apology has been offered to people in Stourbridge left without water after a burst water main.
Severn Trent Water has offered the apology after around 8,500 properties are estimated to have been affected across parts of the DY5, DY6, DY8 and DY9 postcode areas.
The issue has seen people queueing for bottles of water and schools and businesses closed.
Severn Trent said it was working to fix what it described as a complicated issue and repair and said it was working to get supply back up as soon as possible.
A spokeswoman for Severn Trent said: “We’re really sorry to those customers who are currently without water, this is proving to be an incredibly complicated issue and repair, but our number priority remains getting everyone’s water back on as quickly as we can.
.jpg?trim=0,4,336,0&width=640&quality=65)

“We have a huge number of specialist teams in the area, we’re continuing to move water through the network and we’re using a fleet of more than 30 tankers.
“While this has helped us to restore supplies to the majority of customers, we know there are a number of customers with little or no water.
“We have bottled water stations open, and we’re continuing to deliver to our most vulnerable registered customers to provide the local community with bottled water.
“We know how frustrating and difficult this has been, and we want to assure everyone we’re doing everything we can to get customer supplies back on and we appreciate everyone’s continued patience as we do this.”
Severn Trent also said that bottled water was currently available at Sainsbury’s car park in Amblecote until 10pm, with water having been available until 4pm at King George V park in Wordsley.
Comment Guidelines
Iconic Media 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.
