A number of major broadband and phone providers (e.g. Sky Broadband and TalkTalk) have been affected in central South London after several core fibre optic cables were “damaged” by hungry rodents, which has kept thousands of customers offline since last night.
The problems appear to have started at around 9pm last night, although complaints subsided a few hours later as people went to bed. The outage is currently affecting a number of major areas including TULSE HILL, BALHAM, BRIXTON, NINE ELMS, STREATHAM, DULWICH, VAUXHALL, SOUTH CLAPHAM, FOREST HILL and BATTERSEA.
Unfortunately many will wake up this morning to find that their internet connection still hasn’t been restored. The good news is that engineers have been working through the night to resolve the breakage but so far none of the affected ISPs have been able to offer a clear ETA for the completed fix.
Update: South London.
Engineers have been on site overnight and repair work continues this morning, on damaged fibre cables. pic.twitter.com/DurSJhpEVr— Sky Help Team (@SkyHelpTeam) August 11, 2017
https://twitter.com/TalkTalk/status/895771964714962948
UPDATE 9:24am
Sky has just confirmed that the cause of this fault is “the work of rodents” (they must have been really hungry rats to eat through armoured fibre optic cables). We’re of course only assuming that it’s the fault of rats, although lots of other mammals come under the ‘rodents’ title but rats are usually the main culprit. It’s either that or Wombles, the Wombles of Wimbledon.. wombling free, naturally.
Some people also reference politicians as rodents so we might as well add them to the list too.
UPDATE 9:59am
The damaged cable appears to be owned by cable operator Virgin Media.
UPDATE 10:29am
Sky reports that the problem has been resolved. The following is what Sky told us after the event.
· There was a Sky Broadband and Sky Talk outage that affected an area in South London on the 10th and 11th August
· This was a result of rodent damage which caused a physical break to fibres, causing broadband and call services to go down at 9.25pm
· Engineers were at the scene by 11.00pm to fix the problem, and full service was back up and running and fully operational by 10.00am on the 11th
Comments are closed