strange ping issue

[munchies]

Hi all,

I,ve been with IDnet since the 15/1/08 after being with BT/nildram/enta/BE ISP,s and iv never had this b4. I only plug the router in when im using it, which is once a day for gaming usually but every time i connect up to IDnet im getting vastly diffrent pings, either 10ms 20ms or 40ms. Its like im being routed diffrently each time ? via diffrnet BT RAS,s maybe ?
The jump in ping is constant and allways b4 the first hop so probley from the BT side of things b4 it hit IDnet ? I,ve allways had a 10ms ping whatever ISP iv been with and knowing that it can be 10ms with IDnet is very annoying when it randomly conx at 20ms or even 40ms.
Has anybody else had this b4 or should i just go direct to IDnet support and see if it can be looked into as far as i know this shouldent be able to happen, surley it should allways go the shortest route availible
Not sure if it relivant but i allso have a diffrent static IP than the one i was sent in the welcome e-mail ?

Thanks in advance

Munchies 

[Sebby]

Hi, Munchies, and welcome!

Since some maintenance took place a few weeks ago, some users are finding that their pings are not what they used to be. The only thing I can suggest is to is give IDNet a call and let them know.

[Rik]

Hi Muchies

Welcome to the forum, have a karma. 

Something is wrong if your IP address is changing, IDNet only use static addresses. The first thing I would advise, therefore, is that you do a full virus and malware sweep, just in case something is hijacking your connection. If you drop me a PM with the addresses you have had recently, I can check whether they are IDNet addresses or not, but I think you need to contact support as soon as possible. An email might be the best way in this instance, suupport@idnet.net.

[munchies]

Hi all

Just to show what i mean via tracert,s, this was the last 3 logins to IDnet that i just done -

Tracing route to denethor.multiplay.co.uk [85.236.101.80]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    10 ms    10 ms    10 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    10 ms     9 ms     9 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4    10 ms    10 ms    11 ms  lonap1.enta.net [193.203.5.134]
  5    13 ms    10 ms    10 ms  te5-1.telehouse-north0.core.enta.net [87.127.246.122]
  6   263 ms   283 ms   299 ms  te5-2.global-switch.core.enta.net [87.127.236.42]
  7    11 ms    10 ms    10 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8    10 ms    10 ms    10 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9     9 ms    10 ms    10 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]
10    10 ms    10 ms    10 ms  denethor.multiplay.co.uk [85.236.101.80]

Pinging 85.236.101.80 with 32 bytes of data:

Reply from 85.236.101.80: bytes=32 time=10ms TTL=124
Reply from 85.236.101.80: bytes=32 time=9ms TTL=124
Reply from 85.236.101.80: bytes=32 time=10ms TTL=124
Reply from 85.236.101.80: bytes=32 time=9ms TTL=124

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

then i reconnect via router reboot or the bt test login -

Tracing route to denethor.multiplay.co.uk [85.236.101.80]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    43 ms    42 ms    51 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    47 ms    49 ms    50 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4    51 ms    52 ms    49 ms  lonap1.enta.net [193.203.5.134]
  5    40 ms    43 ms    46 ms  te5-1.telehouse-north0.core.enta.net [87.127.246.122]
  6    53 ms    50 ms    50 ms  te5-2.global-switch.core.enta.net [87.127.236.42]
  7    26 ms    23 ms    28 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8    41 ms    52 ms    52 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9    47 ms    43 ms    45 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]
10    35 ms    32 ms    33 ms  denethor.multiplay.co.uk [85.236.101.80]

Pinging 85.236.101.80 with 32 bytes of data:

Reply from 85.236.101.80: bytes=32 time=35ms TTL=124
Reply from 85.236.101.80: bytes=32 time=49ms TTL=124
Reply from 85.236.101.80: bytes=32 time=25ms TTL=124
Reply from 85.236.101.80: bytes=32 time=22ms TTL=124

Ping statistics for 85.236.101.80:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 49ms, Average = 32ms

Then a 3rd reconnect -

Tracing route to denethor.multiplay.co.uk [85.236.101.80]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    22 ms    24 ms    20 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    24 ms    21 ms    22 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4    22 ms    22 ms    23 ms  lonap1.enta.net [193.203.5.134]
  5    27 ms    24 ms    26 ms  te5-1.telehouse-north0.core.enta.net [87.127.246.122]
  6    25 ms    22 ms    23 ms  te5-2.global-switch.core.enta.net [87.127.236.42]
  7    22 ms    34 ms    23 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8    22 ms    23 ms    28 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9    25 ms    22 ms    25 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]
10    24 ms    21 ms    23 ms  denethor.multiplay.co.uk [85.236.101.80]

Pinging 85.236.101.80 with 32 bytes of data:

Reply from 85.236.101.80: bytes=32 time=24ms TTL=124
Reply from 85.236.101.80: bytes=32 time=23ms TTL=124
Reply from 85.236.101.80: bytes=32 time=21ms TTL=124
Reply from 85.236.101.80: bytes=32 time=21ms TTL=124

Ping statistics for 85.236.101.80:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 24ms, Average = 22ms

each time i connect to IDnet its diffrent and these arnt just random tracert/pings, these are consistant numbers untill i reconnect to IDnet via a router reboot/bt speedtest.

You can clearly see that each connect is quite diffrent and there seems to be some packetloss too recently. unfurtanatly i joined IDnet after the router maintenace happend so i have nothing to compare it too from pre router maintenace.

sorry for the long tracert posts

[munchies]

Hi rik,

just to confirm my IP address isnt changing every time, i only have 1 IP since iv been with IDnet but its not the IP that i was sent in my welcome to IDnet e-mail.

sry for any confusion there my writing skills are,nt very good at the best of times :p

Munchies.

[Rik]

Ah, that's OK on the IP address then. That could have been a serious problem.

What happens with a tracert to www.bbc.co.uk or www.idnet.net?

Here's some comparisons from my line, which is interleaved, therefore pings are 10-20ms slower than they should be:

tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.251.206]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  home [192.168.1.254]
  2    26 ms    23 ms    23 ms  telehouse-gw2.idnet.net [212.69.63.55]
  3    24 ms    23 ms    23 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4    24 ms    23 ms    25 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5    23 ms    25 ms    23 ms  212.58.238.149
  6    25 ms    25 ms    23 ms  212.58.239.62
  7    26 ms    23 ms    25 ms  www4.telhc.bbc.co.uk [212.58.251.206]

Trace complete.

tracert www.idnet.net

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

  1    <1 ms     1 ms    <1 ms  home [192.168.1.254]
  2    23 ms    23 ms    23 ms  telehouse-gw2.idnet.net [212.69.63.55]
  3    29 ms    23 ms    23 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4    25 ms    25 ms    25 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    25 ms    25 ms    25 ms  212.69.63.209
  6    25 ms    25 ms    25 ms  www.idnet.net [212.69.36.10]

Trace complete.

tracert denethor.multiplay.co.uk

Tracing route to denethor.multiplay.co.uk [85.236.101.80]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  home [192.168.1.254]
  2    27 ms    23 ms    23 ms  telehouse-gw2.idnet.net [212.69.63.55]
  3    24 ms    23 ms    23 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4    24 ms    25 ms    25 ms  lonap1.enta.net [193.203.5.134]
  5    26 ms    25 ms    27 ms  te5-1.telehouse-north0.core.enta.net [87.127.246.122]
  6    27 ms    25 ms    23 ms  te5-2.global-switch.core.enta.net [87.127.236.42]
  7    26 ms    23 ms    23 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8    24 ms    23 ms    23 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9    24 ms    23 ms    23 ms  po0-1-650-cr1.ixnlon.as35028.net [85.236.110.6]
10    24 ms    25 ms    25 ms  denethor.multiplay.co.uk [85.236.101.80]

[munchies]

The results are the same with bbc/idnet, either a constant 10ms / 20ms or randomly high 30-50ms depending on what seems to be diffrent routing from the BT side of things b4 it hits IDnet
It would take me another 30mins to reconnect 3 times to get the tracerts to post tho.
I have interleaving off with all these tracerts btw.
Would you agree that pings should be pretty constant each time some1 connets to an ISP tho and such large jumps in ping shouldent technicly be possible ?
What do you think is the best route to take from here, would support actually be able to look into routing pre IDnet to see why this is happening ?
I do understand that pings would change with congestion but these changes in ping are all within 30mins and can be reproduced at any time.

Munchies

[Rik]

I'd suggest you let IDNet have your tracerts, and ask them if they can see what is happening. I just wonder if it's possible that the DSLAM is a bit congested, and you are connecting on different paths, giving you different results. TBH, this needs to be looked at with tools we don't have as users.

[psp83]

Since the router/switches upgrades took place,

multiplay.co.uk pings have been all over the place but i get a nice steady 14-17ms ping to jolt, bbc, etc

Perhaps IDnet should be alerted to this and routing to multiplay servers to be re routed?

[ducky22]

I think interleaving may be set to 'auto' on your line. So when you reconnect, its turn its self on or off depending on the condition of the line at that time.

Might be best to check this with IDNet or you can find out yourself depending on what router you have.

[munchies]

ok thanks for your help everybody 

I must just confirm that multiplay pings are fine for me, this is some thing thats happening to any network IP its just a server i use alot so that IP was to hand at the time

Munchies

[munchies]

Hi ducky,
Interleaving is set to off since a few days after i joined IDnet and i checked the router stats after each  login to do the tracerts and its allways been set to off.

Munchies

[Rik]

I've alerted support to this and Paul's post.

[shazzy]

My pings are a little high but then I only migrated yesterday so I'm not sure if this plays a part of why or not.  I thought I'd post some traces incase they help.

Code Select Expand


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

C:\Users\shazzy>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.251.203]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    38 ms    49 ms    46 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    46 ms    46 ms    43 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  4    40 ms    48 ms    45 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5    35 ms    32 ms    31 ms  212.58.238.133
  6    44 ms    40 ms    32 ms  212.58.239.58
  7    61 ms    56 ms    53 ms  www3.telhc.bbc.co.uk [212.58.251.203]

Trace complete.

C:\Users\shazzy>tracert 85.236.101.80

Tracing route to denethor.multiplay.co.uk [85.236.101.80]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    57 ms    51 ms    47 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    46 ms    49 ms    45 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  4    49 ms    50 ms    53 ms  lonap1.enta.net [193.203.5.134]
  5    55 ms    47 ms    44 ms  te5-1.telehouse-north0.core.enta.net [87.127.246
.122]
  6    53 ms    53 ms    58 ms  te5-2.global-switch.core.enta.net [87.127.236.42
]
  7    56 ms    52 ms    60 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8    61 ms    58 ms    55 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9    33 ms    35 ms    33 ms  po0-1-650-cr1.ixnlon.as35028.net [85.236.110.6]

10    51 ms    59 ms    61 ms  denethor.multiplay.co.uk [85.236.101.80]

Trace complete.

C:\Users\shazzy>tracert www.idnet.net

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

  1     *        *        *     Request timed out.
  2    55 ms    50 ms    48 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    60 ms    59 ms    54 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  4    64 ms    57 ms    52 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    44 ms    36 ms    37 ms  212.69.63.225
  6    62 ms    55 ms    56 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\shazzy>

[Lance]

Hi Munchies

I used to have the same thing as you, with the pings changing (but being constant) each time the router was rebooted or switched on. I later found this was due the the actual router (a linksys) developing a fault. I wonder if this could be the case here?

[shazzy]

My ping is fine today.  Just one of them things no doubt.

[Rik]

Have you reconnected? Maybe you're on a different VP?

[shazzy]

Been connected for around 55 hours now hehe, no reconnections.

[Rik]

Bang goes another theory.

[kev445]

Something isn't right somewhere...

Our ping used to be a steady 16-17ms to sites such as the bbc.co.uk and to our domain name. However peak times the ping now seems to be fluctuating between 16ms – 45ms, with fluctuating download speeds...

I don't believe this is a central capacity issue, but something to do with the upgrades which were carried out. I have experienced a similar issue when we upgraded our network to gigabit when we left flow control switched on (flow control is a real menace)!

We are leaving IDNet on Wednesday, however I thought I would post my experience to help backup the claims being made here.

[Rik]

On the evidence we've seen so far, the problems seem to be occurring in the BT network, but I know Simon is monitoring the situation and this thread.

[kev445]

Just for comparison we have an ADSL line with another provider, their ping times are not affected by this problem... This to me indicates it is a problem exclusively with IDNet.

Both ADSL connecting connect into the same DSLAM at the exchange; don't ask me how I know this as it is a very long story, it involved a lift and shift.

[psp83]

Something has changed. Just logged into my pc from work and done a ping test and my pings have dropped 

PING 85.236.96.22 (85.236.96.22): 56 data bytes
64 bytes from 85.236.96.22: icmp_seq=0 ttl=125 time=10.0 ms
64 bytes from 85.236.96.22: icmp_seq=1 ttl=125 time=10.0 ms
64 bytes from 85.236.96.22: icmp_seq=2 ttl=125 time=10.0 ms
64 bytes from 85.236.96.22: icmp_seq=3 ttl=125 time=10.0 ms

--- 85.236.96.22 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 10.0/10.0/10.0 ms

[shazzy]

I just upgraded my firmware so did another trace and I've noticed a drop in my ping times.  Considering I'm on interleaving, they're really good to what I'm used to!

Code Select Expand


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\sharon>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.253.70]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    35 ms    36 ms    34 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    37 ms    34 ms    36 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  4    38 ms    35 ms    36 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5    35 ms    34 ms    33 ms  212.58.238.133
  6    36 ms    34 ms    36 ms  212.58.239.222
  7    40 ms    41 ms    40 ms  www1.cwwtf.bbc.co.uk [212.58.253.70]

Trace complete.

C:\Documents and Settings\sharon>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.253.70] with 32 bytes of data:

Reply from 212.58.253.70: bytes=32 time=36ms TTL=249
Reply from 212.58.253.70: bytes=32 time=35ms TTL=249
Reply from 212.58.253.70: bytes=32 time=34ms TTL=249
Reply from 212.58.253.70: bytes=32 time=35ms TTL=249

Ping statistics for 212.58.253.70:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 36ms, Average = 35ms

C:\Documents and Settings\sharon>

[Rik]

Looks like a result.