Back to all reports

Flooding outside 72 Bedminster Road, blocking pavement and part of road

Reported in the Flooding category anonymously at 19:16, Friday 12 June 2020

Sent to Bristol City Council less than a minute later

The drains near 72 Bedminster Road are not draining the water out of the road, and it has caused the pavement and part of the road to be flooded. I have been out with a spade and fork to unblock the surface of the drains...but there doesn't seem to be a problem there. However I can't see them properly because of the dirty water. I wonder if they are blocked by residue from the building works across the road, the work at the Premier store and the work at 72? The blockage could be further up the drain. I can't do any more to help...sorry. Hopefully the evidence in the photo will confirm there is a problem...even if someone inspects it on a dry sunny day! Many thanks

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 18:16, Friday 12 June 2020

  • A new enquiry has been raised for this issue.

    Posted by Bristol City Council at 08:40, Monday 15 June 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 11:54, Monday 27 July 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 11:54, Monday 27 July 2020

  • These photos were taken yesterday. Pathway (very busy pathway) is impassable...and access to crossing is impossible. This is a crossing heavily used by children going to Parson St Primary school. This is forcing them to cross elsewhere.

    Posted anonymously at 18:25, Friday 28 August 2020

  • A citizen has provided a follow-up to the original enquiry.

    Posted by Bristol City Council at 18:25, Friday 28 August 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:12, Tuesday 1 September 2020

  • So...it's now Oct 3rd and nothing has changed! Just a reminder to those that are de-prioritising this work: *) This crossing is used by many many people to access their local shops. *) The pavement is used by many more people for the same reason *) And most importantly, the crossing is used each morning and afternoon by lots of children and families that attend Parson St Primary School just up the road. The lack of action is now forcing these people either onto a busy road or to cross in dangerous places. This work needs doing NOW ...not at a future date that fits in with the contractors!!! I have added more pictures...tell me honestly that you think this is ok to wait yet more weeks or months! Yes...I am angry, and I absolutely should be. I just did some shopping for an old lady who can't get to the shops as a result of this negligence. I'm happy to help her but I shouldn't have to. This is a disgrace, and you (council) need to do something about it NOW!

    Posted anonymously at 10:15, Saturday 3 October 2020

  • A citizen has provided a follow-up to the original enquiry.

    Posted by Bristol City Council at 10:15, Saturday 3 October 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 09:44, Monday 5 October 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:10, Monday 5 October 2020

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

    State changed to: Fixed

    Posted by Bristol City Council at 14:46, Tuesday 3 November 2020

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