Fixed
HCC still not repairing this safety defect - It's been years!
Reported via desktop in the Pothole category anonymously at 09:09, Friday 10 April 2026
Sent to Hampshire County Council 1 minute later. FixMyStreet ref: 9269008.
Why is this safety defect still unrepaired. It has been here for years marked as "Action scheduled" Then, ignored again for yet another year. Why?
When exactly will this scheduled action happen?
Once again the temporary infill has washed out of the multitude of patches forming the same, damaging pothole directly in the driving line, damaging vehicles & causing a safety issue.
Just get this patched properly, once & for all. To have this still here, ignored for so long is criminal neglect.
Updates
-
I'm sure it will be ignored for another year, damaging vehicles.
"Thank you for submitting your enquiry to Hampshire County Council Highways. Your enquiry reference number is 21886196
Enquiry Type: Carriageway Pothole Defect
Location: FARNHAM ROAD
Logged Date: 10/04/2026"
Posted anonymously at 09:24, Friday 10 April 2026
-
State changed to: In progress
Updated by Hampshire County Council at 09:31, Friday 10 April 2026
-
State changed to: Action scheduled
Updated by Hampshire County Council at 09:52, Friday 10 April 2026
-
Still open, via questionnaire, 14:59, Friday 8 May 2026
-
Absolutely disgusting this is still here after YEARS of being marked as "Action scheduled" by HCC.
At what point exactly will this action take place & this almost 8 year long safety defect be properly repaired?
Absolute disgrace.
Posted anonymously at 15:02, Friday 8 May 2026
-
State changed to: In progress
Updated by Hampshire County Council at 15:26, Friday 8 May 2026
-
Why are HCC still ignoring this large damaging safety defect?
Posted anonymously at 12:32, Saturday 16 May 2026
-
State changed to: Action scheduled
Updated by Hampshire County Council at 12:27, Wednesday 20 May 2026
-
This is yet again worse where infill washed out. WHEN will. HCC do their job & patch it properly? Disgraceful. "Action scheduled" for years, nothing done.
Posted anonymously at 15:10, Thursday 4 June 2026
-
Finally, after being ignored for years, this has been patched. There is absolutely no excuse for a simple repair like this to have taken so long.
State changed to: Fixed
Posted anonymously at 11:22, Saturday 6 June 2026
Only the original reporter may leave updates. If you made the original report please log in to leave an update.