network issue in south london/croydon ?

Anyone else seeing problems in this area ?
I've been seeing massive packet loss and wildly fluctuating latency all day today:

9508 packets transmitted, 7314 packets received, 23.1% packet loss
round-trip min/avg/max/stddev = 11.228/125.985/1606.179/113.873 ms

Service status of course says "no known problems" :/

The awesomeness continues :/

should be around 9ms avg:
64 bytes from 194.164.181.96: icmp_seq=16 ttl=54 time=112.179 ms
64 bytes from 194.164.181.96: icmp_seq=17 ttl=54 time=133.296 ms
64 bytes from 194.164.181.96: icmp_seq=18 ttl=54 time=14.942 ms
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
64 bytes from 194.164.181.96: icmp_seq=21 ttl=54 time=75.615 ms
Request timeout for icmp_seq 22
64 bytes from 194.164.181.96: icmp_seq=23 ttl=54 time=29.083 ms
64 bytes from 194.164.181.96: icmp_seq=24 ttl=54 time=134.389 ms
64 bytes from 194.164.181.96: icmp_seq=25 ttl=54 time=71.812 ms
64 bytes from 194.164.181.96: icmp_seq=26 ttl=54 time=265.071 ms
64 bytes from 194.164.181.96: icmp_seq=27 ttl=54 time=197.114 ms
64 bytes from 194.164.181.96: icmp_seq=28 ttl=54 time=12.024 ms
64 bytes from 194.164.181.96: icmp_seq=29 ttl=54 time=72.719 ms
64 bytes from 194.164.181.96: icmp_seq=30 ttl=54 time=40.635 ms
Request timeout for icmp_seq 31
64 bytes from 194.164.181.96: icmp_seq=32 ttl=54 time=68.576 ms
64 bytes from 194.164.181.96: icmp_seq=33 ttl=54 time=499.966 ms
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
64 bytes from 194.164.181.96: icmp_seq=36 ttl=54 time=20.347 ms
64 bytes from 194.164.181.96: icmp_seq=37 ttl=54 time=214.747 ms
64 bytes from 194.164.181.96: icmp_seq=38 ttl=54 time=229.112 ms
64 bytes from 194.164.181.96: icmp_seq=39 ttl=54 time=435.995 ms
Request timeout for icmp_seq 40

pings have been all over the shop today, but once 6pm rolled around the network has reverted to being totally unusable again :/

More comedy, just got this on the service liar^H^H^H^Hstatus:

http://i775.photobucket.com/albums/yy39/droptical/Sc...

What did they say when you rang them?

The regular call centre script: "are all the lights on etc. etc., no reported problems in that area."

Eng'r is booked to come out on Friday, but TBH this install has been wonky for > month by now; previously it's been just dropping out for a hour or three, they sent a replacement modem which didn't seem to fix it [rather the drop outs just stopped a week or two later], now it's this insane packet loss.
Even back when it was working I've never seen an upstream of > 400kbit (though downstream has typically been good to be fair).

Grumble, grumble

Hopefully with no reported problems it might mean you have a "proper" fault that they can actually fix rather than it being over-utilisation on your segment.

I hope so, but in the meantime I'll keep an eye on the correlation between Uselessness and Time Of Day: http://9600.org/virgin/

Having been reading virgin's own cable support forum I'm starting to get a very nasty feeling about all of this... there are a *lot* of people complaining about exactly the same problem, and not much in the way of resolution.

With Tivo being launched I can only see over utilisation problems getting worse / more common unless they add more capacity in busier areas.

The packet loss isn't relevant (they're droppable ICMP packets), but the latency does matter. Id the downstream is performing OK, then it's upstream congestion IMO. Something for VM to fix by way of investment.