Latency issues

[Desaan]

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

1    <1 ms    <1 ms    <1 ms  192.168.0.1
2    19 ms    19 ms    19 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
3    75 ms   188 ms    84 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4    21 ms    19 ms    19 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5    19 ms    19 ms    20 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6    19 ms    19 ms    19 ms  www.idnet.net [212.69.36.10]

Trace complete.

@dsl4 for me

[Rik]

GW6 latency is OK here but speeds are down.

[Simon]

Don't know if this is any help, but:

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

  1    <1 ms     1 ms    <1 ms  home [192.168.1.254]
  2    33 ms    31 ms    31 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    31 ms    31 ms    33 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    31 ms    31 ms    33 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    32 ms    31 ms    33 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    32 ms    33 ms    33 ms  www.idnet.net [212.69.36.10]

Trace complete.

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

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:

Reply from 212.58.254.252: bytes=32 time=33ms TTL=249
Reply from 212.58.254.252: bytes=32 time=32ms TTL=249
Reply from 212.58.254.252: bytes=32 time=31ms TTL=249
Reply from 212.58.254.252: bytes=32 time=33ms TTL=249

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

[Rik]

How's that compare to normal, Simon?

[Simon]

Sorry, couldn't tell you.  I never usually look at it.   

[Glenn]

I'm averaging 24ms, which is good for my line, but seeds have been up and down over the evening.

[Simon]

Speeds seem to have picked up a bit now, but can't do another BT speedtest yet.

[Rik]

ping www.idnet.net -n 10

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

Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59

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

Not very different to normal for me.

[robostac]

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

 1    <1 ms    <1 ms    <1 ms  moose.zoo.robostac.co.uk [192.168.0.254]
 2     2 ms     1 ms     1 ms  cust118-dsl93-89-131.idnet.net [93.89.131.118]
 3   129 ms    84 ms    49 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 4   136 ms   143 ms   129 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 5   101 ms   115 ms   108 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 6   127 ms   114 ms   108 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 7   132 ms   141 ms   136 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\robo>ping bbc.co.uk

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:
Reply from 212.58.254.252: bytes=32 time=126ms TTL=248
Reply from 212.58.254.252: bytes=32 time=201ms TTL=248
Reply from 212.58.254.252: bytes=32 time=260ms TTL=248
Reply from 212.58.254.252: bytes=32 time=228ms TTL=248

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


Not sure what it is normally, but I usually have a reliably low ping(less than 50ms) in games.

[Rik]

Speeds seem to have picked up a bit now, but can't do another BT speedtest yet.

I suspect that IDNet may be working...

[Simon]

So, someone else has been kicked out of their armchair? 

[Glenn]

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

 1    <1 ms    <1 ms    <1 ms  moose.zoo.robostac.co.uk [192.168.0.254]
 2     2 ms     1 ms     1 ms  cust118-dsl93-89-131.idnet.net [93.89.131.118]
 3   129 ms    84 ms    49 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 4   136 ms   143 ms   129 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 5   101 ms   115 ms   108 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 6   127 ms   114 ms   108 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 7   132 ms   141 ms   136 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\robo>ping bbc.co.uk

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:
Reply from 212.58.254.252: bytes=32 time=126ms TTL=248
Reply from 212.58.254.252: bytes=32 time=201ms TTL=248
Reply from 212.58.254.252: bytes=32 time=260ms TTL=248
Reply from 212.58.254.252: bytes=32 time=228ms TTL=248

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

The highlighted step comes up in most posts, maybe it is the cause of the problem?

[Rik]

So, someone else has been kicked out of their armchair? 

I'm still in mine.

[Sebby]

The highlighted step comes up in most posts, maybe it is the cause of the problem?

It looks like it, though I'm certainly no network expert!

[cash]

Same for me, first time ever having problems with IDnet in 2+ years.

Web / download appear to be working fine, any attempt to play wow results in massive latency and a dc within 10-20 seconds.

[zappaDPJ]

You can add me to the list. I thought my issue was exchange related because of a previous problem but having seen this thread it's fairly obvious we all have the same issue.

I've deleted all my test data now but I have the same problems as described, low latency through tracerts but 1000ms+ in Warcraft together with continual disconnects. Graphics rich websites also fail to fully resolve before a timeout.

Like other members here we were looking good for a first time take down (Freya with 1 add) so I'm not too happy  

[Sebby]

Same for me, first time ever having problems with IDnet in 2+ years.

Web / download appear to be working fine, any attempt to play wow results in massive latency and a dc within 10-20 seconds.

Welcome to the forum anyway, cash.

[Glenn]

Welcome to the forum Cash  

[Rik]

As my pings to IDNet are OK, I wonder whether this is a peering problem?

[zappaDPJ]

Welcome to the forum Cash  

Of course, how rude of me, I got so wrapped up in my problems I didn't notice our new posters.  to you all and welcome

[Desaan]

It looks like it, though I'm certainly no network expert!

Most network admins will tell you not to take too much notice of ping or tracerts as their request information is low on the traffic list but yet its always a good indicator of something not doing what it should be somewhere.  To me it looks like telehouse-gw3 could do with a kick up the arse  

[Sebby]

[Rik]

I'll send a size 12 straightaway.

[Desaan]

As my pings to IDNet are OK, I wonder whether this is a peering problem?

Telia (WoW EU ISP provider) have peering/gateways in central London so if Telia where having problems I'd imagine it to be more widespread than just IDNET users, which doesn't appear to be the case.

[Rik]

Bang goes another theory.