Ping times Jan 28 onwards

[Mohux_Jnr]

This is getting silly, 5pm everyday the pings go through the roof, been fine all day but come tea time...150 guaranteed 

[Glenn]

I'm back to a 200ms average

[Rik]

Same here.

[esh]

Ditto :S

I did a 30 minute offline to see if that helped, but no such luck yet. I'd post another pretty graph but I think you can all anticipate what it would look like.

[davej99]

This is getting silly, 5pm everyday the pings go through the roof, .......

Ditto. Pings rise to circa 200 from 40's. Speeds drop from 6500 to 3500-4500.

I have noticed this trend for about a year. I have speculated, without foundation, that late in the day biz users overlap with early in the evening domestic users. Tech support tell me it is exchange congestion, but it seems others see a similar trend.

[Rik]

This?

[attachment deleted by admin]

[davej99]

This is the result of about a years worth of ThinkBroadband speed checks versus time of day.

[attachment deleted by admin]

[Rik]

Could I ask that anyone seeing ping problems pass on their information to IDNet, so that any issues internal to their network can be traced. It may be that this is down to BT exchange congestion, but the more data that they have, the more readily IDNet can look at their own system.

PingGraph or similar is ideal, or multiple ping repeats, eg ping www.idnet.net -n 100. If we all use idnet.net as the target, it will eliminate as many outside factors as possible.

Thanks.

[Rik]

This is the result of about a years worth of ThinkBroadband speed checks versus time of day.

Got something a bit bigger, Dave?

[Glenn]

Just sent the support team mine

[attachment deleted by admin]

[Mohux_Jnr]

Tech support tell me it is exchange congestion

I think its because the man at idnet that sits there all day typing in 20 to everybodies ping requests goes home for his tea .

[davej99]

Got something a bit bigger, Dave?

I have had it enlarged. 

[Rik]

I can read that now.

[uxbod]

Sending 5, 100-byte ICMP Echos to 212.69.36.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/36 ms

[psp83]

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   166 ms   182 ms   159 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   583 ms   512 ms   262 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   150 ms   145 ms   132 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   144 ms   135 ms   135 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   125 ms   122 ms   123 ms  www.idnet.net [212.69.36.10]

Trace complete.


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   104 ms    97 ms    89 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   100 ms    93 ms    95 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   104 ms   100 ms   338 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    96 ms    95 ms    90 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    95 ms   102 ms   101 ms  www.idnet.net [212.69.36.10]

Trace complete.


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   158 ms   147 ms   136 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   132 ms   133 ms   148 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   142 ms   131 ms   135 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   150 ms   171 ms   162 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   114 ms   127 ms   121 ms  www.idnet.net [212.69.36.10]

Trace complete.

[shazzy]

yer back to a high latency again.

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   158 ms   197 ms   169 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   155 ms   157 ms   145 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   176 ms   159 ms   153 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   170 ms   161 ms   120 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   147 ms   178 ms   177 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Sharon>


[Myst]

Target Name: gameserver.killercreation.co.uk
         IP: 81.19.219.120
  Date/Time: 05/02/2009 20:19:41 to 05/02/2009 20:21:56

1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  www.routerlogin.com [192.168.0.1]
2  179 ms  329 ms  194 ms  180 ms  204 ms  188 ms  200 ms  187 ms  192 ms  205 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
3  179 ms  203 ms  206 ms  181 ms  436 ms  183 ms  209 ms  187 ms  183 ms  197 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4  180 ms  205 ms  200 ms  174 ms  200 ms   *      202 ms  192 ms  189 ms  195 ms  ae0-4.rt2.the.uk.goscomb.net [193.203.5.197]
5  182 ms  207 ms  203 ms  169 ms  198 ms  181 ms  210 ms  195 ms  191 ms  189 ms  tele-north.killercreation.co.uk [77.75.109.198]
6  172 ms  205 ms  201 ms  168 ms   *      182 ms  201 ms  202 ms  189 ms  192 ms  gameserver.killercreation.co.uk [81.19.219.120]

Ping statistics for gameserver.killercreation.co.uk
Packets: Sent = 10, Received = 9, Lost = 1 (10.0%)
Round Trip Times: Minimum = 168ms, Maximum = 205ms, Average = 190ms

This is to my game server

[Rik]

Thanks, Myst. Any idea what your 'normal' ping would be?

[Myst]

Fluctuates between 52-60 as a rule

[Rik]

Thanks. 

[Joel]

holy sh*t!!

pinging 380 to maidenhead, 470 to London!!!

What on earth is going on???!!!  

[Steve]

This is typical for me over the last few days, sorry they're in the wrong order for the time frame.

[attachment deleted by admin]

[zappaDPJ]

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

C:\Users\zappaDPJ>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   167 ms   168 ms   167 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
 3    92 ms    86 ms   100 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   256 ms   160 ms   164 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5   123 ms   127 ms   137 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6   153 ms   168 ms   165 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\zappaDPJ>

[kempez]

I'll add mine to the list

Pinging www.l.google.com [66.102.9.147] with 32 bytes of data:
Reply from 66.102.9.147: bytes=32 time=1657ms TTL=247
Reply from 66.102.9.147: bytes=32 time=1649ms TTL=247
Reply from 66.102.9.147: bytes=32 time=1171ms TTL=247
Reply from 66.102.9.147: bytes=32 time=890ms TTL=247

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

Rebooted, now

Pinging www.l.google.com [66.102.9.104] with 32 bytes of
Reply from 66.102.9.104: bytes=32 time=343ms TTL=247
Reply from 66.102.9.104: bytes=32 time=85ms TTL=247
Reply from 66.102.9.104: bytes=32 time=48ms TTL=247
Reply from 66.102.9.104: bytes=32 time=39ms TTL=247

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

C:\Users\Matt>ping www.google.co.uk

Pinging www.l.google.com [66.102.9.147] with 32 bytes of
Reply from 66.102.9.147: bytes=32 time=37ms TTL=247
Reply from 66.102.9.147: bytes=32 time=60ms TTL=247
Reply from 66.102.9.147: bytes=32 time=59ms TTL=247
Reply from 66.102.9.147: bytes=32 time=52ms TTL=247

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

And a couple run from the diagnostics of my router for good luck:

Pinging 66.102.9.147 with 64 bytes of Data:
Receive reply from 66.102.9.147, time=70ms
Receive reply from 66.102.9.147, time=70ms
Receive reply from 66.102.9.147, time=90ms
Receive reply from 66.102.9.147, time=50ms
Receive reply from 66.102.9.147, time=90ms
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss)

Pinging 212.69.36.86 with 64 bytes of Data:
Receive reply from 212.69.36.86, time=80ms
Receive reply from 212.69.36.86, time=30ms
Receive reply from 212.69.36.86, time=50ms
Receive reply from 212.69.36.86, time=30ms
Receive reply from 212.69.36.86, time=60ms
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss)

Don't know if it will help, but there it is.

[Simon]

Thanks, Kempez, and