Fixed
Metal barrier on vorner broken/removed
Reported via Android in the Pavement Defect category by simon davis at 08:53, Fri 14 January 2022
Sent to Bristol City Council less than a minute later. FixMyStreet ref: 3239602.
Safety barrier has been damaged/removed making it undafe for child pedestrians. This is on a major walking to school route.
Updates
-
A new enquiry has been raised for this issue.
Posted by Bristol City Council at 08:53, Fri 14 January 2022
-
This issue is currently under investigation. We'll provide updates on the outcome as soon as we can.
Posted by Bristol City Council at 10:14, Wed 19 January 2022
-
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 13:43, Thu 20 January 2022
-
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 13:43, Thu 20 January 2022
-
This enquiry is now closed. No further action is required.
State changed to: Fixed
Posted by Bristol City Council at 11:01, Wed 9 February 2022
-
It has NOT been fixed. The council have removed a second varrier so the issue is now worse than it was.
State changed to: Open
Posted by simon davis at 16:05, Sun 13 February 2022
Still open, via questionnaire -
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 16:05, Sun 13 February 2022
-
Stull not fixed. Please set status to reopened.
Posted by simon davis at 10:25, Tue 22 February 2022
-
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 10:25, Tue 22 February 2022
-
Still not fixed. This is a danger to life as it is on a busy junction and crossing next to a park and on a walk to school route
Posted by simon davis at 15:58, Mon 28 February 2022
-
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 15:59, Mon 28 February 2022
-
This has still not been fixed. Please give us a timescale for when it will be.
Posted by David Wilcox at 15:25, Thu 10 March 2022
-
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 15:25, Thu 10 March 2022
-
This has still not been fixed. Please give us a timescale for when it will be.
Posted by David Wilcox at 16:11, Thu 10 March 2022
-
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 16:12, Thu 10 March 2022
-
Still open, via questionnaire, 08:49, Mon 14 March 2022
-
This issue is currently under investigation. We'll provide updates on the outcome as soon as we can.
Posted by Bristol City Council at 09:32, Fri 25 March 2022
-
Why does it take over2 months to resolve this? This is on a main walking to school route; is on a main route to a busy park; is on a very busy road junction. This is a safety risk and must be prioritised urgently. If there is an accident this case will be published as evidence of a lack of urgency.
Posted by Simon Davis at 10:58, Fri 25 March 2022
-
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 10:58, Fri 25 March 2022
-
Still not fixed.
Posted by Simon Davis at 09:52, Mon 11 April 2022
Still open, via questionnaire -
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 09:52, Mon 11 April 2022
-
Still not fixed. Shocking.
Posted by Simon at 10:49, Mon 9 May 2022
Still open, via questionnaire -
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 10:49, Mon 9 May 2022
-
Still open, via questionnaire, 11:01, Mon 6 June 2022
-
Questionnaire filled in by problem reporter
State changed to: Fixed
Posted by Simon Davis at 11:37, Mon 4 July 2022
-
This enquiry is now closed. No further action is required.
Posted by Bristol City Council at 11:37, Mon 4 July 2022
This report is now closed to updates from the public. You can make a new report in the same location. Please reference 3239602 in your new report if it is an update on this one.