Drainage Gully on Pavement In-correctly Positioned. First reported to Council on 28th February 2017
Reported via desktop in the Roads/highways category anonymously at 14:14, Fri 1 December 2023
Sent to Royal Borough of Greenwich less than a minute later. FixMyStreet ref: 5272726.
Greenwich Council continue to mark this report as fixed. But the fact is that the GULLY IS STILL IN-CORRECTLY POSITIONED, and when it rains the water ``just forms a large pond on the pavement``. CONCLUSION:- Gully has been positioned too high to perform its job properly.
Reported via desktop in the Blocked Roadside Gully category anonymously at 19:25, Wednesday 13 September 2023 Sent to Royal Borough of Greenwich less than a minute later. FixMyStreet ref: 4991674.
Greenwich Council continue to mark this report as fixed. But the fact is that the GULLY IS STILL IN-CORRECTLY POSITIONED, and when it rains the water ``just forms a large pond on the pavement``. CONCLUSION:- Gully has been positioned too high to perform its job properly.
Updates
-
Still not fixed
Posted anonymously at 18:55, Thu 21 December 2023
-
Same problem, different day
Posted anonymously at 17:51, Wed 3 April 2024
-
Still not fixed
Posted anonymously at 22:32, Tue 9 April 2024
-
Still not fixed
Posted anonymously at 08:42, Wed 8 May 2024
-
Still not fixed
Posted anonymously at 22:06, Tue 14 May 2024
-
Still not fixed
Posted anonymously at 10:18, Thu 23 May 2024
-
Same problem, different day!!!
Posted anonymously at 22:19, Sun 26 May 2024
-
Still not fixed
Posted anonymously at 07:10, Wed 19 June 2024
-
Still not fixed
Posted anonymously at 21:30, Tue 2 July 2024
-
Still not fixed
Posted anonymously at 21:30, Tue 2 July 2024
-
Same problem, different day
Posted anonymously at 08:22, Sun 7 July 2024
-
Different day, but same problem still exists/not fixed
Posted anonymously at 08:23, Tue 9 July 2024
-
Still the same which means Greenwich Council are just ignoring this problem
Posted anonymously at 09:49, Thu 22 August 2024
-
Different day, but same problem still exists/not fixed
Posted anonymously at 08:22, Mon 26 August 2024
-
Different day, but same problem still exists/not fixed
Posted anonymously at 20:25, Sunday 16 February 2025
Provide an update
Your information will only be used in accordance with our privacy policy