Ping times Jan 28 onwards

[Rik]

No problems here.

[David]

None here either

[Ray]

Not very good here for some reason, Rik.

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

Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms 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 = 122ms, Maximum = 145ms, Average = 133ms

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

Reply from 212.58.224.138: bytes=32 time=154ms TTL=122
Reply from 212.58.224.138: bytes=32 time=143ms TTL=122
Reply from 212.58.224.138: bytes=32 time=145ms TTL=122
Reply from 212.58.224.138: bytes=32 time=173ms TTL=122

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

[Rik]

I've just re-tested, Ray:

ping www.idnet.net -n 20

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

Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=164ms TTL=59
Reply from 212.69.36.10: bytes=32 time=114ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=134ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=180ms TTL=59
Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms TTL=59
Reply from 212.69.36.10: bytes=32 time=164ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=135ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=179ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=186ms TTL=59
Reply from 212.69.36.10: bytes=32 time=104ms TTL=59

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


Something odd is happening, I've advised support.

[Glenn]

>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=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=46ms TTL=59
Reply from 212.69.36.10: bytes=32 time=41ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms 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 = 29ms, Maximum = 46ms, Average = 36ms

[Rik]

I'm down to a 90ms average now...

[Ray]

There seems to be, Rik, I've just done a traceroute to multplay.co.uk

and this hop telehouse-gw3-g0-1-400.idnet.net is giving between 50 and 70% packet loss.

[Glenn]

>tracert www.multiplay.co.uk

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

  1     2 ms     1 ms     1 ms  home [192.168.1.254]
  2    46 ms    42 ms    37 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    28 ms    43 ms    42 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    31 ms    28 ms    31 ms  lonap2.enta.net [193.203.5.135]
  5    85 ms   207 ms    78 ms  te4-4.telehouse-east.core.enta.net [87.127.236.9
7]
  6   106 ms   230 ms   220 ms  te5-4.global-switch.core.enta.net [87.127.236.82
]
  7    47 ms    39 ms    38 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8   153 ms   206 ms   194 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9    31 ms    32 ms    33 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]

10    34 ms    34 ms    33 ms  www1.multiplay.co.uk [85.236.96.22]

[Rik]

I've passed that on, Ray.  

[Ray]

Cheers, Rik. 

[VaderDSL]

Getting very bad pings here also.

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

  1    <1 ms    <1 ms    <1 ms  linksys [192.168.2.1]
  2   530 ms   130 ms   133 ms  telehouse-gw4-lo2.idnet.net [212.69.63.97]
  3   169 ms   159 ms   145 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   173 ms   182 ms   183 ms  lonap2.enta.net [193.203.5.135]
  5   168 ms     *      153 ms  te4-4.telehouse-east.core.enta.net [87.127.236.97]
  6   181 ms   173 ms   169 ms  te5-4.global-switch.core.enta.net [87.127.236.82]
  7   179 ms   176 ms   184 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8   152 ms   133 ms   126 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9   155 ms   166 ms   175 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]
10   168 ms   166 ms   155 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete.

  1    <1 ms    <1 ms    <1 ms  linksys [192.168.2.1]
  2   165 ms   174 ms   265 ms  telehouse-gw4-lo2.idnet.net [212.69.63.97]
  3   174 ms   175 ms   174 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   178 ms   181 ms   156 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   176 ms   177 ms   172 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   155 ms   156 ms   160 ms  www.idnet.net [212.69.36.10]

Trace complete.

I'll give them a call tomorrow if it's still bad.

[shazzy]

Something definitly up today.  Experiencing 400+ ms pings in World of Warcraft. I'm usually 84-150ms

Code Select Expand


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

C:\Users\Sharon>tracert 85.236.96.22

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

  1     1 ms     1 ms     1 ms  192.168.0.1
  2   170 ms   299 ms   155 ms  telehouse-gw4-lo2.idnet.net [212.69.63.97]
  3   151 ms   147 ms   148 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   164 ms   158 ms   175 ms  lonap2.enta.net [193.203.5.135]
  5   319 ms   234 ms   214 ms  te4-4.telehouse-east.core.enta.net [87.127.236.9
7]
  6   176 ms   173 ms   177 ms  te5-4.global-switch.core.enta.net [87.127.236.82
]
  7   168 ms   176 ms   169 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8   139 ms   137 ms   142 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9   160 ms   167 ms   159 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]

10   168 ms   177 ms   172 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete.

C:\Users\Sharon>


[Rik]

If you have access to John Owen's PingGraph, it would be good to run that for an hour or two and let them see the results.

This is mine for the past 20 minutes.

[attachment deleted by admin]

[VaderDSL]

Will pinging the address every 10 seconds cause anything bad? like DDOS type response to the continued ping requests?

[Rik]

No, I've done it before at Simon's request.

[Lance]

My pings are poorly today as well, averaging about 130ms 

[Rik]

Can you run PingGraph for a while, Lance?

[Lance]

I suppose so!

[Rik]

The more evidence to IDNet, the better is should be in helping them find and fix.

[Lance]

Indeed. I've now downloaded and started it running.

[Rik]

I'm beginning to see a return to normal speeds, but the average is still >80ms.

[VaderDSL]

This is mine so far. Notice the three major time outs pushed the average way up.

[Rik]

Mine's a bit more erratic, only one timeout...

[attachment deleted by admin]

[DarkStar]

On Friday I had pings of between 180 and 298 , Yesterday they were under 40 for the first time ever, I usually ping at around 80 - give or take a bit. Just down a ping and I'm back to 150+  .
Have just downloaded the Ping Graph and will run that for a while.

Havn't posted a screeny of my ping results from the Command Prompt because I don't know how to do it. Do plenty of cut/copy and paste but cannot seem to figure this one out  

Probably the East wind and the snow. Got to blame something. Nice and white here now, as long as your indoors that is.

[Glenn]

where do you pings too?