High pings again

[karser]

Thats one of the companies I've been looking at if I cant get it fixed here soon.

[Simon]

I'm not so sure it is a bt problem, I'm now migrated away and my pings are back to low levels again, even with interleaving currently switched on. I'm seeing no slowdowns, no spikes and there appears to be no sign of the 'exchange congestion' that customer support here had suggested the problem was.

Was that from WBC back to Max, or Max to Max?

[Rik]

When did you migrate?

[juiceuk]

  Oops. I jumped the gun a bit last night as the high pings only lasted a short while. Drink is

[Rik]

 

[Pmx]

That's max to max, which is all that is available on my exchange. The migration went through on Thursday. 

[Rik]

Interesting, thanks.

[Turin]

Would just like to add that i migrated last week because of the high ping problem and now i have no problems either.Ping is low and steady with no spikes etc....I guess the mystery deepens

[Rik]

Where to?

[Turin]

Aquiss

[Rik]

Thanks. 

[Turin]

No problem.If this ping issue get's sorted out i'll be back with you guys in a flash 

[Rik]

It's interesting me that both people who've migrated and resolved their problems have gone to Enta resellers. I wonder if IDNet can draw any conclusions from that?

[dujas]

I think multplay.co.uk website and game servers are hosted on enta.net (if that's where they play)? Pings pass via their hops when tracerouting their IPs at least.

[Rik]

Interesting, thanks.

[Turin]

My server isn't with Multiplay.It's with Killercreation if that's any help.

[Rik]

Could you do me a favour and ping www.idnet.net, then paste the results here please? If you could manage a tracert as well, that would be great.   If you have results from when you were with IDNet, that would be even better.

[Turin]

I havn't kept any of my old ping result's i'm afraid.Here's what i have now though...

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

Reply from 212.69.36.10: bytes=32 time=18ms TTL=55
Reply from 212.69.36.10: bytes=32 time=17ms TTL=55
Reply from 212.69.36.10: bytes=32 time=17ms TTL=55
Reply from 212.69.36.10: bytes=32 time=18ms TTL=55

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


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

 1     1 ms    <1 ms     1 ms  menu [192.168.1.254]
 2    19 ms    17 ms    21 ms  lns09.inx.dsl.enta.net [78.33.38.162]
 3    19 ms    17 ms    17 ms  gi4-40.interxion.dsl.enta.net [78.33.38.161]
 4    19 ms    17 ms    17 ms  te2-3.interxion.core.enta.net [87.127.236.209]
 5    20 ms    18 ms    19 ms  te5-1.gs1.core.enta.net [87.127.236.85]
 6    20 ms    17 ms    19 ms  te5-4.telehouse-east2.core.enta.net [78.33.35.217]
 7    19 ms    19 ms    17 ms  idnet-gw-b.lonap.net [193.203.5.133]
 8    19 ms    17 ms    18 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 9    21 ms    19 ms    19 ms  www.idnet.net [212.69.36.10]

[Rik]

Smooth. Thanks for that. The more data we can collect, the more chance IDNet have of tracing the problem.

[karser]

Did you go with the gaming package or the normal ones?, & if your results are that good why would you come back later?

[Simon]

Aquiss

They were on my shortlist before I joined IDNet, so I'd be interested to hear how they perform. 

[Turin]

I went with a gaming package.The only thing i don't like is the support forum leaves alot to be desired and i've heard mixed review's regarding phone support.It's purely customer support that would bring me back to idnet and although i'm getting good ping time's etc they're not far off from what i had originaly with idnet before all this ping issue cropped up.

[Simon]

Well, of course, IDNetters leaves other customer support forums way behind. 

[Sebby]

They were on my shortlist before I joined IDNet, so I'd be interested to hear how they perform. 

They would perform the same as any other Enta reseller.

[Pmx]

As requested earlier, this is my ping/trace into idnet now, with interleaving on. Below is how it was when I was with Idnet, as you can see the difference is pretty significant!

ping idnet.com

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

Reply from 212.69.36.10: bytes=32 time=29ms TTL=55
Reply from 212.69.36.10: bytes=32 time=26ms TTL=55
Reply from 212.69.36.10: bytes=32 time=26ms TTL=55
Reply from 212.69.36.10: bytes=32 time=26ms TTL=55

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


tracert idnet.com

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

 1    <1 ms    <1 ms    <1 ms  192.168.1.1
 2    28 ms    27 ms    27 ms  lns05.inx.dsl.enta.net [78.33.38.146]
 3    27 ms    26 ms    26 ms  gi4-44.interxion.dsl.enta.net [78.33.38.145]
 4    29 ms    30 ms    26 ms  te2-3.interxion.core.enta.net [87.127.236.209]
 5    33 ms    32 ms    31 ms  te5-1.gs1.core.enta.net [87.127.236.85]
 6    31 ms    29 ms    34 ms  te5-4.telehouse-east2.core.enta.net [78.33.35.21
7]
 7    29 ms    32 ms    31 ms  idnet-gw-b.lonap.net [193.203.5.133]
 8    31 ms    28 ms    28 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 9    31 ms    30 ms    30 ms  www.idnet.net [212.69.36.10]

Trace complete.

Hi all, unfortunately having only been with IDNET for 1 month I've decided to migrate away as the standard of connection has been pretty awful throughout.

We're on a fairly short line and generally connect at 8128 to the exchange, and before moving to IDNET would get pings of 15-25 to the bbc etc along with speeds up 6-7mb. Since moving over it's been awful, with speeds regularly below 2-3mb and sometimes way lower at less than 300k!! Pings have also been really high making game playing pretty much impossible, this is a typical ping result:

C:\Users\Paul>tracert bbc.co.uk

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

 1     3 ms     1 ms     1 ms  192.168.1.1
 2   120 ms   102 ms   101 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
 3   123 ms   101 ms   101 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   123 ms   101 ms   101 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
 5   124 ms   101 ms   101 ms  212.58.238.129
 6   129 ms   101 ms   101 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=136ms TTL=59
Reply from 212.69.36.10: bytes=32 time=59ms 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 = 59ms, Maximum = 136ms, Average = 105ms


Just thought I'd post feedback, on the plus side the customer support people at idnet have been really helpful but the long and the short of it is that the connection has never been right, which is a shame.