Ping problems on gw5/adsl max location poll

[Steve]

I couldn't see any results of the last poll on pings until I'd voted,whether that's a browser issue or the way the forum software is setup I don't know. I know on previous polls I could see the results prior to voting but not anymore

[Gary]

I couldn't see any results of the last poll on pings until I'd voted,whether that's a browser issue or the way the forum software is setup I don't know. I know on previous polls I could see the results prior to voting but not anymore

Same here Steve, I cant see the results unless I vote

[Glenn]

It depends how the poll is set up, in the first place, as the are different options on views available.

[pup]

oh well its not the end of he world!

[Steve]

Thanks Glenn I've never needed to look there. That's two we've had recently I wonder what an inactive member would say

[Lance]

I've amended the poll so now the option to view results should be available

[karser]

Sorry my fault I did put it on show results only after vote, didnt think those who didnt need to vote would be interested. As it stands it seems there is no pattern so would effectively rule out a routing issue as the sole culprit

[pup]

I didn't mean to create such a fuss 

[Gunnar]

Hiya Folks,

Just voted. I'm on GW5 and in North East Essex - which I've assumed is East.
I noticed last night whilst playing Online that my pings were a little erratic...jumping from low teens to high twenties/thirties/forties every 30 secs or so.  I was hosting and my chums were getting lag because of it....first time in a while.
I'm currently at work so don't know what it's like today.

Cheers,
Pete.

[Gary]

Pings and trace for me this morning

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

C:\Users\>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=68ms TTL=59
Reply from 212.69.36.10: bytes=32 time=72ms TTL=59
Reply from 212.69.36.10: bytes=32 time=86ms TTL=59
Reply from 212.69.36.10: bytes=32 time=113ms 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 = 68ms, Maximum = 113ms, Average = 84ms

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

C:\Users\>tracert www.idnet.net

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   100 ms    98 ms    90 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   104 ms    93 ms   104 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   152 ms   182 ms   219 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    98 ms   103 ms   115 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   120 ms   125 ms   124 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\>

[Ray]

Everything is fine here.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms 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 = 17ms, Maximum = 18ms, Average = 17ms



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

  1    88 ms    99 ms    99 ms  router [***.***.*.**]
  2    21 ms    21 ms    22 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    35 ms    22 ms    25 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    24 ms    21 ms    20 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    25 ms    19 ms    21 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    22 ms    19 ms    18 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Gary]

Everything is fine here.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms 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 = 17ms, Maximum = 18ms, Average = 17ms



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

  1    88 ms    99 ms    99 ms  router [***.***.*.**]
  2    21 ms    21 ms    22 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    35 ms    22 ms    25 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    24 ms    21 ms    20 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    25 ms    19 ms    21 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    22 ms    19 ms    18 ms  www.idnet.net [212.69.36.10]

Trace complete.

But its not for me Ray and I have no idea why,  so called congestion is so low at my exchange  it would not cause these issues last night at 11pm my thoughput was a third of what it should be, I'm on the south coast between Portsmouth and Chichester, and everyday I get issues now, and this morning its awful, what makes me feel uneasy though, is people who have migrated away seem to be reporting pings, latency and speed as fine, I was going to sit and wait but Aquiss looks like they may be getting my cash at this rate. 

[tomharrison]

I agree. Things are still bad for me too :

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

  1     2 ms     1 ms     1 ms  192.168.0.1
  2   108 ms   100 ms    86 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    54 ms    63 ms    57 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    33 ms    67 ms    60 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    97 ms    92 ms   104 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    85 ms    93 ms   103 ms  www.idnet.net [212.69.36.10]

Trace complete.


Pings were in the 200ms region throughout yesterday and throughput was beyond a joke. I've rebooted the router numerous times and even had IDNet switch off interleaving on my line to try and reduce latency. Not that that made any difference .

I hope IDNet can get to the bottom of this. In the almost 3 years I've been with them, I've never experienced so many problems as we have seen in the last couple of months .

[Simon]

Hiya Folks,

Just voted. I'm on GW5 and in North East Essex - which I've assumed is East.
I noticed last night whilst playing Online that my pings were a little erratic...jumping from low teens to high twenties/thirties/forties every 30 secs or so.  I was hosting and my chums were getting lag because of it....first time in a while.
I'm currently at work so don't know what it's like today.

Cheers,
Pete.

  Pete! 

[Simon]

I was going to sit and wait but Aquiss looks like they may be getting my cash at this rate. 

Interesting, perhaps, that the people who have reported improvements have both gone to Enta resellers.

[Rik]

Hi Pete and welcome to the forum.

[Gary]

Interesting, perhaps, that the people who have reported improvements have both gone to Enta resellers.

Could be Simon, ideally I would like to stay and wait it out and see what happens, its ok on a Sunny day I go in the garden but this morning its wet, and trying to do banking and ordering my medication was hell, suddenly its dropped again and seems faster   when it effects my life lines like banking and medical stuff it p*isses me off. Oh well I would go online and game but that would be cr@p   maybe more sedatives are needed  

[Gary]

Sorry where are my manners,  Pete 

[Gunnar]

 8) Thanks Guys  8)

So are there still residual problems with GW5 ?  Or is it just random ?
I haven't tried the old switch it off, leave it for 30 mins and switch it on trick yet !

Cheers,
Pete.

[Rik]

We're told that there are no problems within the IDNet network, but some people are still experiencing problems.

[Gunnar]

Oooh.     
I'll check my connection tonight and see if yesterday evening was just a blip for me.

Cheers,
Pete.

[Rik]

NP.

[Ray]

  Pete and

[karser]

Just got on the net, my router has been off overnight:

C:\Documents and Settings\Karser>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=168ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=161ms TTL=59
Reply from 212.69.36.10: bytes=32 time=136ms 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 = 136ms, Maximum = 174ms, Average = 159ms

Waiting for a reply on the email I sent friday with more tests, if they arent prepared to at least try to switch me to a different gw, even if its just to prove me wrong about it being all gw5 & max, after I've already asked twice if they will move me, then its time to ask for my mac code I think.

[Rik]

I understand. If what we have been told is right, it really shouldn't affect things if you're on a different realm, but it has to be worth a try.