Road surface rapidly deteriorating
Reported via Android in the Potholes & road surface category by Cllr Sarah Moore at 09:23, Monday 2 March 2020
Sent to Bath and North East Somerset Council 3 minutes later. Council ref: 2033697.
The surface of the road by this junction is rapidly deteriorating with a large hole in the surface containing large stones that are getting flicked up onto the pavement when vehicles drive over it, making it dangerous for pedestrians, cyclists and road users
Thank you for this report. We will review the details and carry out an inspection of the site if required.
9 out of 10 Potholes & Road Surface reports are updated within 10 working days once we decide what action to take. To find out what we do and why it might take longer, please visit https://www.bathnes.gov.uk/ fmsroads
If you have more information about the issue you can add an update to this report.
State changed to: In progress
Posted by Bath and North East Somerset Council at 09:26, Monday 2 March 2020
We've looked into this report and passed the details on to our contractor. They will plan and carry out any work needed. 4 out of 5 issues are updated within 30 working days.
To find out what we do and why it might take longer, please visit https://www.bathnes.gov.uk/ fmsroads01
We'll update this report when the contractor has completed their work.
State changed to: Action scheduled
Posted by Bath and North East Somerset Council at 13:48, Monday 2 March 2020
Our contractor has now completed their work. If this issue reoccurs please log a new report.
Thank you for using Fix My Street. Reporting issues like this online can help us deal with them more efficiently.
To find out more about what we do, please visit https://www.bathnes.gov.uk/ fmsroads04
State changed to: Fixed
Posted by Bath and North East Somerset Council at 09:59, Thursday 5 March 2020
The surface has not been touched at all since I reported it
State changed to: Open
Posted by Cllr Sarah Moore at 09:42, Monday 30 March 2020
Still open, via questionnaire
+1. This hasn't been fixed.
Posted anonymously at 15:42, Tuesday 18 August 2020
Provide an update