Back to all reports

Kerb edge (dropped kerb) loose, raised and upside down.

Reported via iOS in the Pavement Defect category anonymously at 22:42, Monday 24 February 2020

Sent to Bristol City Council 3 minutes later

To correct earlier report-should be HOLMES GROVE, Henleaze.

RSS feed of updates to this problem Receive email when updates are left on this problem.

Updates

  • A new enquiry has been raised for this issue.

    Posted by Bristol City Council at 22:45, Monday 24 February 2020

  • This issue is currently under investigation. We'll provide updates on the outcome as soon as we can.

    Posted by Bristol City Council at 07:58, Friday 28 February 2020

  • This issue has been reallocated to the relevant officer or team for action. They'll update you on progress.

    Posted by Bristol City Council at 11:38, Monday 2 March 2020

  • A job has been raised with our contractors to action this issue and appropriate repairs or maintenance will be undertaken as soon as they can.

    Posted by Bristol City Council at 10:58, Friday 27 March 2020

  • A job has been raised with our contractors to action this issue and appropriate repairs or maintenance will be undertaken as soon as they can.

    Posted by Bristol City Council at 10:58, Friday 27 March 2020

  • This enquiry is now closed. No further action is required.

    State changed to: Fixed

    Posted by Bristol City Council at 14:09, Monday 30 March 2020

  • This enquiry is now closed. No further action is required.

    Posted by Bristol City Council at 23:05, Monday 27 April 2020

  • Unable to check as self isolating.

    Posted anonymously at 00:03, Tuesday 28 April 2020

  • This enquiry is now closed. No further action is required.

    Posted by Bristol City Council at 14:51, Tuesday 26 May 2020

  • Still unable to check as isolating. Is there anyone in Henleaze that could check please?

    Posted anonymously at 15:51, Tuesday 26 May 2020

This report is now closed to updates. You can make a new report in the same location. Please reference 2019830 in your new report if it is an update on this one.