High pings again

Rik · Aug 01, 2009, 09:59:37

Quote from: Azy on Jul 31, 2009, 20:19:57
its looking better and my sync is now 3487 instead of around 2800

Much as I'm sure IDNet wouldn't mind getting the thanks for that

, sync speed is a purely local function, between you and the exchange.

MarkE · Aug 01, 2009, 16:18:20

Pinging multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=164ms TTL=124
Reply from 85.236.96.22: bytes=32 time=161ms TTL=124
Reply from 85.236.96.22: bytes=32 time=155ms TTL=124
Reply from 85.236.96.22: bytes=32 time=129ms TTL=124

psp83 · Aug 01, 2009, 16:22:06

My pings are also higher than normal today. Putting that down to weird things happening to my line/package at the mo.

Rik · Aug 01, 2009, 16:29:14

Mine, boringly, are still the same as ever. Are you seeing any packet loss, Paul?

psp83 · Aug 01, 2009, 17:47:08

Quote from: Rik on Aug 01, 2009, 16:29:14
Mine, boringly, are still the same as ever. Are you seeing any packet loss, Paul?

nope, just random pings.

one time its around 13ms and next around 80ms.

Rik · Aug 01, 2009, 17:56:53

All I can suggest is following the diagnostic process in the sticky, and let support have the results. These things should have been resolved.

MarkE · Aug 01, 2009, 19:24:03

"should have" being the optimal point here,pretty damn well infuriated with this whole debacle

Rik · Aug 01, 2009, 19:30:30

Imagine how we feel, Mark.

gwidnet · Aug 02, 2009, 14:22:49

mmm.. my son tells me his ps3 playing has taken a turn for the worse.

Interestingly now on speedtest net I am now directed to Coventry as the server to test instead of Maidenhead, and since this change happened, my pings have fallen off from a rock steady 31-32 now to 40-70, and today 92ms.

To my mind it seems that something must have changed to now always suggest Coventry instead of Maidenhead?

dujas · Aug 02, 2009, 14:29:52

Try ping www.idnet.net from the command prompt, it should be in the 20-35ms range.

zappaDPJ · Aug 02, 2009, 14:42:46

The speedtest.net reports for latency/pings are usually way off, particularly to the London server. As dujas has said you should use the ping command get an accurate representation of your current ping.

ping -n 50 will return 50 pings if you want more data. (The spaces in the command line are important.)

gwidnet · Aug 02, 2009, 14:48:54

pings

Strange, we never had any problems until I was sent to Coventry!

Glenn · Aug 02, 2009, 14:59:43

GW, can you follow the sticky support maybe able to help you.

gwidnet · Aug 02, 2009, 15:08:10

Ok thanks, have done btw tracert doesn't seem to work on mac terminal.

Glyn

dujas · Aug 02, 2009, 15:13:37

I'd reboot your router and see if it cures the problem, if it doesn't, or it re-appears later, then you need to contact support. Rik's guide is for a Windows user, you'll need to use the traceroute command rather than tracert.

Rik · Aug 02, 2009, 15:14:43

I'm not sure if there's an equivalent on the Mac, but I'm sure a Mac user will soon tell us.

It's important that no-one else is using the network when you run the tests.

RonGodwin · Aug 02, 2009, 15:32:09

Quote from: Rik on Aug 02, 2009, 15:14:43
I'm not sure if there's an equivalent on the Mac, but I'm sure a Mac user will soon tell us. It's important that no-one else is using the network when you run the tests.

For Mac users... go into the Hard Disk icon > locate Applications file > locate Utilities file > locate Network Utility (you can run pings... traceroute from there

Rik · Aug 02, 2009, 15:33:31

Thanks, Ron.

gwidnet · Aug 02, 2009, 15:35:11

Yep thanks Ron

Dopamine · Aug 03, 2009, 14:36:01

My pings are high again, and browsing sluggish to find pages. Throughput once pages have been found is OK. Have the problems still not been fixed, or is it just me?

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

Reply from 212.69.36.10: bytes=32 time=158ms TTL=59
Reply from 212.69.36.10: bytes=32 time=166ms TTL=59
Reply from 212.69.36.10: bytes=32 time=162ms TTL=59
Reply from 212.69.36.10: bytes=32 time=170ms TTL=59

Rik · Aug 03, 2009, 14:39:38

We're told they have been, so I can only suggest you ask IDNet, sorry.

Dopamine · Aug 03, 2009, 14:55:04

Support = platitudes and apologies, no resolution. I really can't face another wasted phone call today, so....

Rebooted router, problem solved........ until tomorrow?

Come on IDNet, maybe you should order up a bulk load of MACs in anticipation of demand.

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

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=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=13ms TTL=59

gwidnet · Aug 03, 2009, 15:59:40

Not too much success with support, but seems like a very pleasant chap.
I'm on GW5 did I see on thinkbroadband that the high pings were mainly on GW5?

pings still very erratic, some down at 32, but some well over 100 still, and this mornign were up near 300.

I've never had this issuebefore in 3 and a half years with idnet.

Rik · Aug 03, 2009, 16:11:07

It shouldn't matter which realm you're on, GW, these days logins are on a round-robin between the two centrals. AFAIK, the network is now rebalanced and there is no congestion. If you continue to see issues, all I can suggest is you follow the diagnostics in the sticky and let support have the results.

Gary · Aug 03, 2009, 16:49:08

Pings high again here

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=162ms TTL=59
Reply from 212.69.36.10: bytes=32 time=153ms TTL=59
Reply from 212.69.36.10: bytes=32 time=183ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms 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 = 153ms, Maximum = 183ms, Average = 168ms