My latency in the last 24 hours has been steadily rising. One of the services I regularly connect to is reporting a constant 450ms instead of the usual 50-125ms (at peek).
Pings to Jolt which are normally around 50ms are also very high:
C:\Users\zappaDPJ>ping www.jolt.co.uk
Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=124ms TTL=58
Reply from 82.133.85.65: bytes=32 time=126ms TTL=58
Reply from 82.133.85.65: bytes=32 time=121ms TTL=58
Reply from 82.133.85.65: bytes=32 time=121ms TTL=58
Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 126ms, Average = 123ms
C:\Users\zappaDPJ>tracert www.jolt.co.uk
Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 211 ms 133 ms 136 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 141 ms 152 ms 139 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 123 ms 151 ms 134 ms te2-3.cr05.hx2.bb.gxn.net [193.203.5.14]
5 131 ms 125 ms 121 ms vl3953.cr05.tn5.bb.gxn.net [62.72.137.29]
6 149 ms 158 ms 146 ms gi1-1-6.ar01.tn5.bb.gxn.net [62.72.140.142]
7 123 ms 124 ms 127 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
8 118 ms 112 ms 114 ms secure.jolt.co.uk [82.133.85.65]
Trace complete.
C:\Users\zappaDPJ>
Nothing has changed at my end and there are no announcements on the IDNet main site. I've rebooted the modem/router but the high pings remain.
Connection Speed 7968 kbps 448 kbps
Line Attenuation 26.0 db 12.5 db
Noise Margin 6.3 db 22.0 db
This speed test result doesn't look too bad:
Speed Down 5177.67 Kbps ( 5.1 Mbps )
Speed Up 369.72 Kbps ( 0.4 Mbps )
Is anyone else having problems?
Getting horrible latency issues here myself also.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings > ping www.jolt.co.uk
Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=126ms TTL=58
Reply from 82.133.85.65: bytes=32 time=129ms TTL=58
Reply from 82.133.85.65: bytes=32 time=128ms TTL=58
Reply from 82.133.85.65: bytes=32 time=131ms TTL=58
Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 131ms, Average = 128ms
C:\Documents and Settings > tracert www.jolt.co.uk
Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms linksys [192.168.2.1]
2 126 ms 142 ms 127 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 133 ms 130 ms 131 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 127 ms 134 ms 124 ms te2-3.cr05.hx2.bb.gxn.net [193.203.5.14]
5 134 ms 126 ms 130 ms vl3953.cr05.tn5.bb.gxn.net [62.72.137.29]
6 120 ms 116 ms 116 ms gi1-1-6.ar01.tn5.bb.gxn.net [62.72.140.142]
7 118 ms 118 ms 126 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14]
8 126 ms 124 ms 124 ms secure.jolt.co.uk [82.133.85.65]
Trace complete.
Ditto 25-10-08 20.12hrs
Tracert (Normally circa 28ms interleaved)
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 142 ms 144 ms 159 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 161 ms 150 ms 150 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 144 ms 143 ms 155 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 154 ms 138 ms 145 ms 212.58.238.149
6 139 ms 144 ms 328 ms 212.58.239.62
7 134 ms 139 ms 133 ms www-vip.telhc.bbc.co.uk [212.58.251.195]
BT Speedtest (Normally 6500-6700)
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 2408 kbps
Connection (Normal)
Connection Rate: 8128 Kbps
Line Attenuation: 37 dB
Noise Margin: 10 dB
Mines interleaved and o.k
C:\Documents and Settings\Steve>tracert www.jolt.co.uk
Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 80 ms 31 ms 31 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 31 ms 31 ms 31 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 33 ms 32 ms 31 ms te2-3.cr05.hx2.bb.gxn.net [193.203.5.14]
5 * 42 ms 31 ms vl3952.cr05.tn5.bb.gxn.net [62.72.137.9]
6 36 ms 33 ms 32 ms gi2-48-5.ar01.tn5.bb.gxn.net [62.72.140.14]
7 32 ms 31 ms 32 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
8 32 ms 35 ms 32 ms secure.jolt.co.uk [82.133.85.65]
Trace complete.
C:\Documents and Settings\Steve>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 32 ms 49 ms 32 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 266 ms 33 ms 31 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 33 ms 32 ms 32 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 32 ms 33 ms 33 ms 212.58.238.149
6 37 ms 33 ms 32 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
7 34 ms 36 ms 34 ms www-vip.cwwtf.bbc.co.uk [212.58.253.67]
Trace complete.
Problem posts are on telehouse-gw2-lo1.idnet.net [212.69.63.51].
Steve is on telehouse-gw2-lo2.idnet.net [212.69.63.55]
Dave
Well spotted. I'll give support a ring first thing Monday morning.
Thanks for the replies :)
It seems that a couple of users have been experiencing this. It's good that you seemed to have narrowed it down, so definitely let IDNet know and hopefully they can look into it and get it sorted. :)
Further problems as you can see from my modem log (assuming I'm interpreting things correctly) I'm losing sync. I'm also having massive timeouts (lag spikes).
Sun, 2008-10-26 00:04:18 - LCP down.
Sun, 2008-10-26 00:04:20 - Initialize LCP.
Sun, 2008-10-26 00:04:20 - LCP is allowed to come up.
Sun, 2008-10-26 00:04:55 - CHAP authentication success
Sun, 2008-10-26 00:46:21 - LCP down.
Sun, 2008-10-26 00:46:29 - Initialize LCP.
Sun, 2008-10-26 00:46:29 - LCP is allowed to come up.
Sun, 2008-10-26 00:46:43 - Administrator login successful - IP:
Sun, 2008-10-26 00:47:02 - Initialize LCP.
Sun, 2008-10-26 00:47:02 - LCP is allowed to come up.
Sun, 2008-10-26 00:47:22 - LCP down.
Sun, 2008-10-26 00:47:37 - Initialize LCP.
Sun, 2008-10-26 00:47:37 - LCP is allowed to come up.
Sun, 2008-10-26 00:47:45 - LCP down.
Sun, 2008-10-26 00:47:53 - Initialize LCP.
Sun, 2008-10-26 00:47:53 - LCP is allowed to come up.
Sun, 2008-10-26 00:48:26 - CHAP authentication success
However the latency issues have gone at this moment in time ???
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\zappaDPJ>ping www.jolt.co.uk
Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=13ms TTL=58
Reply from 82.133.85.65: bytes=32 time=13ms TTL=58
Reply from 82.133.85.65: bytes=32 time=14ms TTL=58
Reply from 82.133.85.65: bytes=32 time=14ms TTL=58
Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms
C:\Users\zappaDPJ>
The sync drops are 99% certain to be local. Looking at the timing, I'd say BT were working on your exchange.
Pings seem back to the recent interleaved baseline for my telehouse-gw2-lo1.idnet.net connection, but not to the 20s that I used to enjoy. Need to run PingGraph at length to see if I still get episodes over 100+. :o
BT speedtest is on the upper bumpstop. Yesterday's spread of degradation could hardly be exchange contention.
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 43 ms 42 ms 42 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 45 ms 43 ms 43 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 44 ms 45 ms 43 ms rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
5 45 ms 49 ms 44 ms 212.58.238.149
6 43 ms 44 ms 46 ms 212.58.239.62
7 44 ms 43 ms 46 ms www-vip.telhc.bbc.co.uk [212.58.251.195]
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 6745 kbps
Dave
Has anyone contacted IDNet?
I haven't Rik, I wanted to do some more testing today and I thought I'd wait until Monday as I'm a little uncertain of what level of support is available over the weekend. Would you suggest I call them today?
I wouldn't suggest calling, but an email - it will get picked up Monday morning as it wouldn't be considered an emergency. It would be worth pointing to this thread.
I'll do that now, thanks :) :thumb:
NP. :)
Just a quick note to say IDNet support were unable to identify any problems and that things do indeed seem to be back to normal after the weekend.
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\speedup>trace rt www.jolt.co.UK
Tracing route to www.jolt.co.UK [82.133.85.65]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 21 ms 21 ms 20 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 21 ms 21 ms 21 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 21 ms 21 ms 21 ms te2-3.cr05.hx2.bb.gxn.net [193.203.5.14]
5 22 ms 21 ms 21 ms vl3953.cr05.tn5.bb.gxn.net [62.72.137.29]
6 21 ms 22 ms 22 ms gi1-1-6.ar01.tn5.bb.gxn.net [62.72.140.142]
7 23 ms 21 ms 21 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
8 22 ms 23 ms 23 ms secure.jolt.co.uk [82.133.85.65]
Trace complete.
C:\Users\zappaDPJ>ping www.jolt.co.UK
Pinging www.jolt.co.UK [82.133.85.65] with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=20ms TTL=58
Reply from 82.133.85.65: bytes=32 time=20ms TTL=58
Reply from 82.133.85.65: bytes=32 time=20ms TTL=58
Reply from 82.133.85.65: bytes=32 time=21ms TTL=58
Ping statistics for 82.133.85.65:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milliseconds:
Minimum = 20ms, Maximum = 21ms, Average = 20ms
C:\Users\speedup>
I hope things are back to normal for the rest of you.
Deus ex machina. :(