Ping times Jan 28 onwards

[DarkStar]

Had drops outs around 2am this morning according to the router logs but pings are looking now:

Ian



[attachment deleted by admin]

[Rik]

Just guessing here, but I'm wondering whether IDNet re-booted their routers in the small hours as part of the resolution.

[Rik]

I was wrong, something happened but IDNet don't yet know what and are waiting to hear from BT.

[Glenn]

By 10pm last night, my pings were up in the 190ms region on DSL4, then about 10 minutes later they dropped right off to around 30ms, so I think someone must have adjusted something.

[Rik]

Mine seem to be close to normal now, with occasional spikes. It's still being tweaked this morning.

[Simon]

Not sure if this is related to pings, but I'm noticing quite a bit of lag when posting on the forum - up to 20 seconds from hitting the 'Post' button, to the post appearing.

[Rik]

That seems to be a server issue, Simon, it had started last week.

[Simon]

Just to add to the list then. 

[Rik]

Indeed.

[Matt M]

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 341 ms 196 ms 81 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 39 ms 39 ms 40 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 42 ms 42 ms 41 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 41 ms 39 ms 44 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 42 ms 41 ms 41 ms www.idnet.net [212.69.36.10]

Trace complete.

Tracing route to www.overclock3d.net [212.69.36.86]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 105 ms 256 ms 148 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 111 ms 126 ms 120 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 124 ms 135 ms 145 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 125 ms 131 ms 122 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 121 ms 132 ms 113 ms oc2.overclock3d.net [212.69.36.86]

Trace complete.

Tracing route to www.l.google.com [66.102.9.99]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 276 ms 79 ms 85 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 90 ms 85 ms 108 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 106 ms 97 ms 99 ms 195.66.224.125
5 69 ms 74 ms 82 ms 209.85.252.40
6 122 ms 126 ms 119 ms 209.85.251.190
7 153 ms 146 ms 150 ms 64.233.174.187
8 151 ms 127 ms 118 ms 64.233.174.18
9 81 ms 88 ms 103 ms 66.102.9.99

Trace complete.

some of mine

[conneh]

My internet went down for about an hour? at like 1ish... thinking this was sorting the problem.

However, pings are back to 150!

Tracing route to www.dustworld.net [193.238.84.199]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2   147 ms   241 ms   154 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   154 ms   152 ms   159 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   163 ms   156 ms   156 ms  ae0-4.rt2.the.uk.goscomb.net [193.203.5.197]
  5   208 ms   159 ms   158 ms  ge-0-0-479.rt0.iph.uk.goscomb.net [77.75.109.98]

  6   145 ms   169 ms     *     dustworld.net [193.238.84.199]
  7   138 ms   186 ms   153 ms  dustworld.net [193.238.84.199]

Trace complete.

[Sebby]

I wonder if IDNet merely reversed whatever they were trying to do when it broke everything, which has meant that pings are back to how they were?

[Rik]

Or the mass re-connections after the outage have unbalanced the network again? I really don't know.

[Sebby]

Could be.

[shazzy]

Really nasty latency at the moment also.

Code Select Expand


Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Sharon>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  192.168.0.1
  2   170 ms   171 ms   429 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   168 ms   161 ms   162 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   170 ms   174 ms   169 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   172 ms   165 ms   162 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   169 ms   171 ms   167 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Sharon>


[Rik]

I'm seeing the same sort of numbers, Shazzy.

[Matt M]

similar here

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=252ms TTL=59
Reply from 212.69.36.10: bytes=32 time=200ms TTL=59
Reply from 212.69.36.10: bytes=32 time=178ms TTL=59
Reply from 212.69.36.10: bytes=32 time=355ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 178ms, Maximum = 355ms, Average = 246ms

[karser]

Ok things have gone truly pear shaped now, went to browse today & was slow as hell, saw my ping times were up, & thought I'd better try some speed tests, this really isnt good.

http://www.thinkbroadband.com/speedtest/results/id/123367215162998231047.html



C:\Documents and Settings\Karser>ping www.multiplay.co.uk

Pinging core1.multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=169ms TTL=124
Reply from 85.236.96.22: bytes=32 time=161ms TTL=124
Reply from 85.236.96.22: bytes=32 time=168ms TTL=124
Reply from 85.236.96.22: bytes=32 time=170ms TTL=124

Ping statistics for 85.236.96.22:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 161ms, Maximum = 170ms, Average = 167ms

C:\Documents and Settings\Karser>ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=162ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms TTL=59
Reply from 212.69.36.10: bytes=32 time=164ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 162ms, Maximum = 165ms, Average = 163ms

0.3Mbps download on an 8mb connection & pings over 160, which is as bad as 56k pings used to be.

[Rik]

You need to let IDNet know, we can't do anything to help from here.

[Rik]

I've just reset my PPP session (no reboot) and pings have dropped back to 24ms average. 

[conneh]

Just got off the phone to IDNet...

Problem would of been sorted today, however a router went down at lunch time which has caused it to take abit longer - people should sort to see normal pings today, however some will not experince this untill tomorow - and it may even creep into Thursday. Hope this helps.

[Rik]

Thanks for that. 

[conneh]

Sorry for sounding a bit stupid... but what do you mean by restarting your 'PPP' session?

[esh]

Easiest way to restart PPP is turn off and on your router.

It's still nasty for me here. I'll keep an eye out. 200ms+

[Rik]

Sorry for sounding a bit stupid... but what do you mean by restarting your 'PPP' session?

It's not stupid. There are two elements to your connection, the ADSL link, the connection between you and the exchange (which governs your speed), and the PPP session, your connection into IDNet and thus the web. It was the PPP which failed due to the router issue. Some routers will allow you to reset the PPP session independently of the ADSL connection. If you can do this, it has the advantage of not disturbing the connection speed.