Quote:
Originally Posted by pabscars
Was there a firmware update at approx 3:30am yesterday morning, the little red spikes are evident on all of yesterdays post's
|
missed that as i rebooted router a couple of mins before, that is why i have 2 packet loss periods at that time. (maybe my super hub is super and rebooted all your connections)
last night was well poor, had to turn xbox off at about 9.45pm as the planes in battlefiled 1943 was impossible to fly with that lag freeze. pathpings wouldn't even resolve to the final hop during that bad period
[img]Download Failed (1)[/img]
Tracing route to bbc.co.uk [212.58.254.251]
over a maximum of 30 hops:
0 workhorse-PC [192.168.0.2]
1 10.34.248.1
2 * manc-core-1b-ae3-2527.network.virginmedia.net [82.8.209.61]
3 manc-bb-1b-as0-0.network.virginmedia.net [212.43.163.66]
4 * manc-bb-1a-ae0-0.network.virginmedia.net [62.253.187.177]
5 glfd-bb-1b-ae1-0.network.virginmedia.net [213.105.175.146]
6 glfd-tmr-1-ae5-0.network.virginmedia.net [213.105.159.46]
7 redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 workhorse-PC [192.168.0.2]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 10.34.248.1
0/ 100 = 0% |
2 31ms 0/ 100 = 0% 0/ 100 = 0% manc-core-1b-ae3-2527.network.virg
inmedia.net [82.8.209.61]
0/ 100 = 0% |
3 34ms 0/ 100 = 0% 0/ 100 = 0% manc-bb-1b-as0-0.network.virginmed
ia.net [212.43.163.66]
0/ 100 = 0% |
4 36ms 0/ 100 = 0% 0/ 100 = 0% manc-bb-1a-ae0-0.network.virginmed
ia.net [62.253.187.177]
0/ 100 = 0% |
5 42ms 1/ 100 = 1% 1/ 100 = 1% glfd-bb-1b-ae1-0.network.virginmed
ia.net [213.105.175.146]
0/ 100 = 0% |
6 40ms 0/ 100 = 0% 0/ 100 = 0% glfd-tmr-1-ae5-0.network.virginmed
ia.net [213.105.159.46]
0/ 100 = 0% |
7 31ms 0/ 100 = 0% 0/ 100 = 0% redb-ic-1-as0-0.network.virginmedi
a.net [62.253.185.78]
Trace complete.