Fixed
Torn up pavement
Reported in the Pavement Defect category anonymously at 09:12, Fri 17 May 2019
Sent to Bristol City Council 3 minutes later. FixMyStreet ref: 1632356.
The pavement opposite the Old Baptist Church where building work is taking place has been torn up due to lorries driving over the pavement. Area approx. 1m long, is a tripping hazard
Updates
-
Enquiry raised.
Posted by Bristol City Council at 08:15, Fri 17 May 2019
-
Under investigation.
Posted by Bristol City Council at 11:06, Fri 24 May 2019
-
Customer follow up.
Posted by Bristol City Council at 12:15, Wed 29 May 2019
-
Customer follow up.
Posted by Bristol City Council at 12:15, Wed 29 May 2019
-
Customer follow up.
Posted by Bristol City Council at 12:15, Wed 29 May 2019
-
Customer follow up.
Posted by Bristol City Council at 12:15, Wed 29 May 2019
-
2 potholes appeared today, has been damaged with a Kellaway lorry today , tarmac has sunk and there is a deep pothole which has been filled with stone by the developers today 28.5.19
Posted anonymously at 13:12, Wed 29 May 2019
-
2 potholes appeared today, has been damaged with a Kellaway lorry today , tarmac has sunk and there is a deep pothole which has been filled with stone by the developers today 28.5.19
Posted anonymously at 13:12, Wed 29 May 2019
-
2 potholes appeared today, has been damaged with a Kellaway lorry today , tarmac has sunk and there is a deep pothole which has been filled with stone by the developers today 28.5.19
Posted anonymously at 13:12, Wed 29 May 2019
-
2 potholes appeared today, has been damaged with a Kellaway lorry today , tarmac has sunk and there is a deep pothole which has been filled with stone by the developers today 28.5.19
Posted anonymously at 13:12, Wed 29 May 2019
-
Your enquiry has been investigated and deemed that no action is required at present.
State changed to: Fixed
Posted by Bristol City Council at 11:27, Thu 13 June 2019
This report is now closed to updates from the public. You can make a new report in the same location. Please reference 1632356 in your new report if it is an update on this one.