Ping times Jan 28 onwards

[Lance]

Mine are back to normal too!

[VaderDSL]

Mine have gone back up 

[Rik]

Same here. I'm about to fire off my last email of the day to support.

[Glenn]

This what I have got, the spike is happening approx every 25 minutes

[attachment deleted by admin]

[Rik]

Bit different to the pattern I am seeing, Glenn...

[attachment deleted by admin]

[DarkStar]

All gone haywire again


C:\Documents and Settings\Owner>ping idnet.co.uk

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

Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=98ms TTL=59
Reply from 212.69.36.10: bytes=32 time=146ms 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 = 98ms, Maximum = 146ms, Average = 129ms


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

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

Reply from 212.58.224.138: bytes=32 time=136ms TTL=122
Reply from 212.58.224.138: bytes=32 time=146ms TTL=122
Reply from 212.58.224.138: bytes=32 time=158ms TTL=122
Reply from 212.58.224.138: bytes=32 time=159ms 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 = 136ms, Maximum = 159ms, Average = 149ms

Ian

[g7pkf]

Mine look ok (on GW5)


C:\Users\Dean>ping idnet.co.uk -t

Pinging idnet.co.uk [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 17ms, Average = 15ms
Control-C
^C
C:\Users\Dean>

[Rik]

Haywire reported.

[Mohux_Jnr]

Now I am not one to moan as you can probably see from my post count but I am sure somebody worded the recent e-mail I recieved wrongly, downgrade surely would have been more appropriate.
I am hoping this will only be short term until the techies are back at their stations on Monday as I have generally, before the recent change been happy with the service.

C:\Users\Jons>ping idnet.co.uk

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=164ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms 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 = 119ms, Maximum = 164ms, Average = 139ms

My download speeds are also all over the place, averaging 2.5 Meg compared to the high 6 Meg prior to the upgrade. I hope this is not the norm for what we can expect from the recent changes?.

[Rik]

I'm sure it isn't the norm, or what was planned, but rather some sort of teething problems. Capacity has been increased with a new 155M central plus the Gigabit Hostlink, so it won't be any congestion problems, but rather, I suspect, some unexpected interaction between the new routers and the existing network. But I'm only guessing, until IDNet say something, that's all I can do.

How's your dad, I haven't seen him in lately?

[Mohux_Jnr]

Thanks for the response Rik, he is fine, saw him today and he was still sat in the usual spot in front of a PC monitor . We are both in the same town so I suspect he has been experiencing the same issues so my guess is it will not be long before you hear from him, I am just suprised he has not beaten me to it!.

He is slipping 

[mrapoc]

Just came across this thread and unfortunately im going to have to jump on the bandwagon of the bad ping brigade 

iv contacted support and asked if there is anything I can do to help remedy my problem

but yeh

gaming pings have been steadily increasing over the last months from a good 30ms average to a 70ms average

[Simon_idnet]

Looks like we need to do more work on getting the Centrals balanced properly. We'll be making this the priority over the next few days.
Simon

[MarkE]

Back to the dial up days (nearly!)... Already checked with various computers and only one turned on at a time. Browsing is also laggy. Anyone else having problems today? Download speed down from 830k/second to 45k/second.

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2   166 ms   182 ms   178 ms  telehouse-gw4-lo2.idnet.net [212.69.63.97]
  3   148 ms   165 ms   156 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   164 ms   147 ms   139 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  5   156 ms   142 ms   121 ms  212.58.238.133
  6   149 ms   136 ms   141 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

M:\>

Welcome to my world as of the past few days ...






uk server  and my ping time is over 150ms and unplayable

[cjenkins]

Yep back to black 

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

Reply from 212.58.224.138: bytes=32 time=162ms TTL=121
Reply from 212.58.224.138: bytes=32 time=174ms TTL=121
Reply from 212.58.224.138: bytes=32 time=130ms TTL=121
Reply from 212.58.224.138: bytes=32 time=153ms TTL=121

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

I'd prefer Simon's response if it said "We'll be making that the priority this evening".

[neocr0n]

I know simon_idnet has already replied but I thought I would post my results too.  Currently reside In the North East.  I've had gaming ping problems for 3/4 days now.  Times varey but mainly between 3 and 9pm.

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

  1    11 ms     4 ms     3 ms  router [192.168.0.1]
  2   103 ms   284 ms   133 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   147 ms   139 ms   132 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243

  4   116 ms   111 ms   125 ms  lonap2.enta.net [193.203.5.135]
  5   125 ms   119 ms   273 ms  te4-4.telehouse-east.core.enta.net [87.127.236.
7]
  6   118 ms   102 ms   107 ms  te5-4.global-switch.core.enta.net [87.127.236.8
]
  7   101 ms    88 ms    81 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8    75 ms    66 ms    57 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9   106 ms   111 ms   110 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]

10    83 ms    78 ms    75 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete

[zappaDPJ]

My latency has been fine until today, now it's abysmal 

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

C:\Users\zappaDPJ>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=112ms TTL=124
Reply from 85.236.96.22: bytes=32 time=87ms TTL=124
Reply from 85.236.96.22: bytes=32 time=87ms TTL=124
Reply from 85.236.96.22: bytes=32 time=100ms 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 = 87ms, Maximum = 112ms, Average = 96ms

C:\Users\zappaDPJ>tracert www.multiplay.co.uk

Tracing route to core1.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   114 ms   134 ms   108 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   120 ms   114 ms   122 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    81 ms    78 ms    79 ms  lonap2.enta.net [193.203.5.135]
  5   101 ms   103 ms   100 ms  te4-4.telehouse-east.core.enta.net [87.127.236.9
7]
  6    95 ms   102 ms    90 ms  te5-4.global-switch.core.enta.net [87.127.236.82
]
  7    78 ms    76 ms    80 ms  te1-1.interxion.core.enta.net [87.127.236.86]
  8    74 ms    68 ms    59 ms  gi4-3.enta-transit.as35028.net [84.45.252.122]
  9   176 ms   187 ms   223 ms  po0-1-651-cr.ixnlon.as35028.net [85.236.110.11]

10    84 ms    85 ms    95 ms  www1.multiplay.co.uk [85.236.96.22]

Trace complete.

C:\Users\zappaDPJ>

[Lance]

Mine are high again on DSL4...

C:\Users\Lance>ping idnet.net -n 10

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=177ms TTL=59
Reply from 212.69.36.10: bytes=32 time=162ms TTL=59
Reply from 212.69.36.10: bytes=32 time=181ms TTL=59
Reply from 212.69.36.10: bytes=32 time=164ms TTL=59
Reply from 212.69.36.10: bytes=32 time=182ms TTL=59
Reply from 212.69.36.10: bytes=32 time=167ms TTL=59
Reply from 212.69.36.10: bytes=32 time=182ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=179ms 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 = 162ms, Maximum = 182ms, Average = 174ms

[Glenn]

Mine rose too

[attachment deleted by admin]

[Lance]

Attached is my latest graph, showing things settled down again about 21:50 but had a bit of a rough patch at about 22:12 for quarter of an hour or so.

[attachment deleted by admin]

[Simon_idnet]

Tonight's re-balancing of the Centrals seems to have worked. We'll be keeping a close eye on the situation to make sure that it doesn't happen again. Apologies for the poor performance this evening.
Simon

[Lance]

Thanks Simon. My pings on the whole are back to normal for my line (between 30ms and 35ms) but I'm still getting short periods - 20 seconds at a time - where I get pings in excell of 100ms.

[mrapoc]

C:\Users\Sam>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=49ms TTL=59
Reply from 212.69.36.10: bytes=32 time=51ms TTL=59
Reply from 212.69.36.10: bytes=32 time=50ms TTL=59
Reply from 212.69.36.10: bytes=32 time=47ms 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 = 47ms, Maximum = 51ms, Average = 49ms

Used to be 25-30 ms 

[Lance]

My last post should read in excess, not excell! Stupid left and right hands!

[Sebby]

I always write words that I didn't mean to, Lance.