Pings

[mrapoc]

nice one idnet! 

[Scott]

nice one idnet! 

ergo...everbody STOP bloody pinging telehouse ?!?! 

[karvala]

nice one idnet! 

ergo...everbody STOP bloody pinging telehouse ?!?! 

LOL, there wasn't a really a problem at all; a malicious rival decided to start a rumour to get everyone to ping telehouse to make it look like there was one.   

[Scott]

D'Oh ! It's a new take on the bot-net DDOS attack ! The DUPE !
Dumb User Ping Exploit

...*runs*...

[mrapoc]

  lol

[maxping]

Simon if you find the problem is it likely to bring the general ping speeds down?

The reason i ask is my pings are now always over 50ms where they were always 30 - 40ms.

I don't know if i am the only one who has found this.

[karvala]

Simon if you find the problem is it likely to bring the general ping speeds down?

The reason i ask is my pings are now always over 50ms where they were always 30 - 40ms.

I don't know if i am the only one who has found this.

Yes, I've found exactly the same thing; my pings, even after being on interleaving (must remember to get that switched off again), were only 25-26ms typically (and 16-17ms before interleaving), but in the last week or so  they've increased to around 35ms on average, for no obvious reason.

[mrapoc]

sit tight guys  im sure they will fix it
damn connection errors on server 

[Bill]

Simon if you find the problem is it likely to bring the general ping speeds down?

Let's show a little confidence and make it "... when you find the problem...", eh? 

Apart from the spike, my pings have stayed where they always were:

C:\WINDOWS>tracert idnet.net

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

  1     1 ms   <10 ms   <10 ms  192.168.1.1
  2    15 ms    16 ms    14 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    15 ms    14 ms    14 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    16 ms    16 ms    16 ms  redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
  5    15 ms    15 ms    16 ms  idnet.net [212.69.36.10]

Trace complete.

[maxping]

My pings are still sticking to the usual 50 with the odd spike.

Tracing route to 212.69.36.10 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2    49 ms    50 ms    50 ms  212.69.63.45
  3    51 ms    49 ms    49 ms  212.69.40.1
  4    49 ms    50 ms    49 ms  212.69.63.1
  5    50 ms    50 ms    50 ms  212.69.36.10



  1     *        *        *     Request timed out.
  2    48 ms    48 ms    49 ms  212.69.63.45
  3   364 ms   266 ms   329 ms  212.69.40.1
  4    49 ms    50 ms    49 ms  212.69.63.1
  5    50 ms    51 ms    49 ms  212.69.36.10


  1     *        *        *     Request timed out.
  2    50 ms    50 ms    48 ms  212.69.63.45
  3    51 ms    50 ms    49 ms  212.69.40.1
  4    49 ms    49 ms    50 ms  212.69.63.1
  5    49 ms    51 ms    51 ms  212.69.36.10

[browney]

Its getting to the point now were my friend on plusnet has a lower ping that me on the OC3D server which is hosted by IDNet

[maxping]

Beat this if you can  


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

Reply from 212.69.36.10: bytes=32 time=84ms TTL=60
Reply from 212.69.36.10: bytes=32 time=111ms TTL=60
Reply from 212.69.36.10: bytes=32 time=111ms TTL=60
Reply from 212.69.36.10: bytes=32 time=100ms TTL=60
Reply from 212.69.36.10: bytes=32 time=93ms TTL=60
Reply from 212.69.36.10: bytes=32 time=129ms TTL=60
Reply from 212.69.36.10: bytes=32 time=163ms TTL=60
Reply from 212.69.36.10: bytes=32 time=143ms TTL=60
Reply from 212.69.36.10: bytes=32 time=122ms TTL=60
Reply from 212.69.36.10: bytes=32 time=117ms TTL=60
Reply from 212.69.36.10: bytes=32 time=144ms TTL=60
Reply from 212.69.36.10: bytes=32 time=134ms TTL=60
Reply from 212.69.36.10: bytes=32 time=148ms TTL=60
Reply from 212.69.36.10: bytes=32 time=124ms TTL=60
Reply from 212.69.36.10: bytes=32 time=146ms TTL=60
Reply from 212.69.36.10: bytes=32 time=120ms TTL=60
Reply from 212.69.36.10: bytes=32 time=137ms TTL=60
Reply from 212.69.36.10: bytes=32 time=146ms TTL=60
Reply from 212.69.36.10: bytes=32 time=86ms TTL=60
Reply from 212.69.36.10: bytes=32 time=116ms TTL=60
Reply from 212.69.36.10: bytes=32 time=101ms TTL=60
Reply from 212.69.36.10: bytes=32 time=79ms TTL=60
Reply from 212.69.36.10: bytes=32 time=75ms TTL=60
Reply from 212.69.36.10: bytes=32 time=114ms TTL=60
Reply from 212.69.36.10: bytes=32 time=120ms TTL=60
Reply from 212.69.36.10: bytes=32 time=129ms TTL=60
Reply from 212.69.36.10: bytes=32 time=143ms TTL=60
Reply from 212.69.36.10: bytes=32 time=130ms TTL=60
Reply from 212.69.36.10: bytes=32 time=123ms TTL=60
Reply from 212.69.36.10: bytes=32 time=124ms TTL=60
Reply from 212.69.36.10: bytes=32 time=103ms TTL=60
Reply from 212.69.36.10: bytes=32 time=100ms TTL=60
Reply from 212.69.36.10: bytes=32 time=89ms TTL=60
Reply from 212.69.36.10: bytes=32 time=114ms TTL=60
Reply from 212.69.36.10: bytes=32 time=104ms TTL=60
Reply from 212.69.36.10: bytes=32 time=102ms TTL=60
Reply from 212.69.36.10: bytes=32 time=121ms TTL=60
Reply from 212.69.36.10: bytes=32 time=119ms TTL=60
Reply from 212.69.36.10: bytes=32 time=110ms TTL=60
Reply from 212.69.36.10: bytes=32 time=124ms TTL=60
Reply from 212.69.36.10: bytes=32 time=131ms TTL=60
Reply from 212.69.36.10: bytes=32 time=124ms TTL=60
Reply from 212.69.36.10: bytes=32 time=84ms TTL=60
Reply from 212.69.36.10: bytes=32 time=99ms TTL=60
Reply from 212.69.36.10: bytes=32 time=121ms TTL=60
Reply from 212.69.36.10: bytes=32 time=122ms TTL=60
Reply from 212.69.36.10: bytes=32 time=94ms TTL=60
Reply from 212.69.36.10: bytes=32 time=125ms TTL=60
Reply from 212.69.36.10: bytes=32 time=138ms TTL=60
Reply from 212.69.36.10: bytes=32 time=108ms TTL=60
Reply from 212.69.36.10: bytes=32 time=122ms TTL=60
Reply from 212.69.36.10: bytes=32 time=126ms TTL=60
Reply from 212.69.36.10: bytes=32 time=115ms TTL=60
Reply from 212.69.36.10: bytes=32 time=98ms TTL=60
Reply from 212.69.36.10: bytes=32 time=94ms TTL=60
Reply from 212.69.36.10: bytes=32 time=112ms TTL=60
Reply from 212.69.36.10: bytes=32 time=120ms TTL=60
Reply from 212.69.36.10: bytes=32 time=150ms TTL=60
Reply from 212.69.36.10: bytes=32 time=150ms TTL=60
Reply from 212.69.36.10: bytes=32 time=112ms TTL=60
Reply from 212.69.36.10: bytes=32 time=116ms TTL=60

[maxping]

This is strange i was going to turn the router off for the usual 30 mins ,i decided to do another test to check it before i did and its back to normal 


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

Reply from 212.69.36.10: bytes=32 time=56ms TTL=60
Reply from 212.69.36.10: bytes=32 time=48ms TTL=60
Reply from 212.69.36.10: bytes=32 time=48ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=48ms TTL=60
Reply from 212.69.36.10: bytes=32 time=52ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=50ms TTL=60
Reply from 212.69.36.10: bytes=32 time=52ms TTL=60
Reply from 212.69.36.10: bytes=32 time=50ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=50ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=47ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=50ms TTL=60
Reply from 212.69.36.10: bytes=32 time=53ms TTL=60
Reply from 212.69.36.10: bytes=32 time=50ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=48ms TTL=60
Reply from 212.69.36.10: bytes=32 time=48ms TTL=60
Reply from 212.69.36.10: bytes=32 time=51ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=48ms TTL=60

[cavillas]

Too many people are pinging, bringing the ping server down. 

[maxping]

I have just been on a server where i was playing with a ping of 50-60 then suddenly it went over 80 and didn't come down , i left the server.

Is there any news from IDNet ?

[maxping]

This is getting annoying the pings have gone back to the 50's i was getting again.

Is anyone else seeing this pattern of not just ping spikes but pings generally changing for long periods?

Could we not have regular feedback from IDNet even if it was just to say things are still being investigated.

To most users this may seem trivial but many of us use our machines for gaming as much as surfing and for us this is a big deal.

Ive had cr*p pings for nearly 2 weeks and we seem to be no nearer a solution .

For the non ADSL Guide users  - http://bbs.adslguide.org.uk/showthreaded.php?Cat=&Board=idnet&Number=2618723

[Simon_idnet]

Hi Guys

We are indeed deep into investigations. We have two independant teams of Cisco consultants evaluating the situation with us. Rather troubling is that neither of them agree that there is a problem and both have conflicting views as to the possible cause of the ping spikes.

The reason why they regard the situation as not being a problem is that the router in question is doing the right thing by treating pings as lowest priority. Bear in mind that game play uses UDP pakets; ICMP (ping) packets are not used for anything other than checking if a host (server or router) is live or not. Using ping to measure network performance is self-defeating due to its low priority rating.

I am not trying to say that the 'ping spikes' are unusual and we are trying to get the bottom of it. We are treating this as high priority even though it does not appear to be affecting most game players. Please check the OC3D forums and see here: http://bbs.adslguide.org.uk/showthreaded.php?Cat=&Board=idnet&Number=2630158

If these guys were affected then there would be a deafening clamour!

Maxping, your symptoms of consistently high pings do not line-up with a regular 5 second ping rise each minute. If you could please call Support then we'll run some line checks for you.

Will keep you updated.
Cheers
Simon

[browney]

I am from OC3D and so is jiffz who i play bf2 with, he also gets ping spikes.

I mean come on my friend on plusnet gets a 24ms ping now

[mrapoc]

these last couple of weeks i can play for 5 mins to 3 hours without a high ping but when it happens (which it usually does at random) it stays with me, usually resulting in abnormally slow downloads or streaming video (not just talking pings) but at other times it absolutely fine - any1 else feeling this random act of sorrow 

[maxping]

Maxping, your symptoms of consistently high pings do not line-up with a regular 5 second ping rise each minute. If you could please call Support then we'll run some line checks for you.

I will give CS a call but I'm not really getting consistently high pings its up and down like a yoyo but seems to stay high before dropping back.

[karvala]

Must admit I'm a bit confused by the Cisco response.  Is the suggestion that the ping spikes may be caused by spikes in TCP or UDP packets, consequently causing delays in the processing of ICMP packets?  If so, where are those packets coming from?

If that's not the case, then I fail to see how the fact that the router correctly assigns low priority to ICMP packets means that unrelated ping spikes are in their opinion somehow not a problem.  It's like a mechanic telling you the fact that your car is unable to enter 2nd gear isn't really a problem because the steering wheel still works.

[mrapoc]

nicely put lol

[maxping]

I will phone cs tomorrow as i finish early.

Heres tonights update.

Reply from 212.58.224.116: bytes=32 time=49ms TTL=249
Reply from 212.58.224.116: bytes=32 time=52ms TTL=249
Reply from 212.58.224.116: bytes=32 time=50ms TTL=249
Reply from 212.58.224.116: bytes=32 time=51ms TTL=249
Reply from 212.58.224.116: bytes=32 time=52ms TTL=249
Reply from 212.58.224.116: bytes=32 time=50ms TTL=249
Reply from 212.58.224.116: bytes=32 time=48ms TTL=249
Reply from 212.58.224.116: bytes=32 time=54ms TTL=249
Reply from 212.58.224.116: bytes=32 time=49ms TTL=249
Reply from 212.58.224.116: bytes=32 time=52ms TTL=249
Reply from 212.58.224.116: bytes=32 time=48ms TTL=249
Reply from 212.58.224.116: bytes=32 time=50ms TTL=249
Reply from 212.58.224.116: bytes=32 time=58ms TTL=249
Reply from 212.58.224.116: bytes=32 time=57ms TTL=249
Reply from 212.58.224.116: bytes=32 time=57ms TTL=249
Reply from 212.58.224.116: bytes=32 time=48ms TTL=249
Reply from 212.58.224.116: bytes=32 time=53ms TTL=249
Reply from 212.58.224.116: bytes=32 time=50ms TTL=249
Reply from 212.58.224.116: bytes=32 time=52ms TTL=249
Reply from 212.58.224.116: bytes=32 time=51ms TTL=249
Reply from 212.58.224.116: bytes=32 time=72ms TTL=249
Reply from 212.58.224.116: bytes=32 time=61ms TTL=249
Reply from 212.58.224.116: bytes=32 time=62ms TTL=249
Reply from 212.58.224.116: bytes=32 time=52ms TTL=249
Reply from 212.58.224.116: bytes=32 time=50ms TTL=249
Reply from 212.58.224.116: bytes=32 time=51ms TTL=249
Reply from 212.58.224.116: bytes=32 time=72ms TTL=249
Reply from 212.58.224.116: bytes=32 time=107ms TTL=249
Reply from 212.58.224.116: bytes=32 time=95ms TTL=249
Reply from 212.58.224.116: bytes=32 time=65ms TTL=249
Reply from 212.58.224.116: bytes=32 time=56ms TTL=249
Reply from 212.58.224.116: bytes=32 time=94ms TTL=249
Reply from 212.58.224.116: bytes=32 time=55ms TTL=249
Reply from 212.58.224.116: bytes=32 time=53ms TTL=249
Reply from 212.58.224.116: bytes=32 time=54ms TTL=249
Reply from 212.58.224.116: bytes=32 time=54ms TTL=249
Reply from 212.58.224.116: bytes=32 time=50ms TTL=249

[philco]

I too am having problems with pings but i wouldn't descibe them as ping spikes. from 10am to 6pm my ping usually rises to 150ms and during the evenings it is generally ok  but will occasionally go back up to 150ms for a minute or so.

I spoke to support and they suggested it was linked to the current ping spike problems but simon seems to suggest in his post these symptoms are not related.

Not sure what to do now 

Recently a typical day looks like this ...

PS this is effecting gaming and browsing speeds too so not just ICMP but also UDP and TCP packets

[attachment deleted by admin]

[maxping]

*Edited version below*