Ping times Jan 28 onwards

MarkE · Jan 28, 2009, 13:49:28

Quote from: Rik on Jan 28, 2009, 13:02:21
Today's is down to the router upgrade, Mark, as detailed in 'Announcements'.

ah ok,only ping times have gone whack to multiplay.co.uk

Reply from 85.236.96.22: bytes=32 time=59ms TTL=124
Reply from 85.236.96.22: bytes=32 time=68ms TTL=124
Reply from 85.236.96.22: bytes=32 time=64ms TTL=124
Reply from 85.236.96.22: bytes=32 time=41ms TTL=124

Sebby · Jan 28, 2009, 13:49:58

Let IDNet know.

MarkE · Jan 31, 2009, 13:52:13

Quote from: Sebby on Jan 28, 2009, 13:49:58
Let IDNet know.

been there got the tshirt and coat and soon walking shoes...

multiplay.co.uk

Reply from 85.236.96.22: bytes=32 time=136ms TTL=124
Reply from 85.236.96.22: bytes=32 time=97ms TTL=124
Reply from 85.236.96.22: bytes=32 time=88ms TTL=124
Reply from 85.236.96.22: bytes=32 time=87ms TTL=124

router rebooted numerous times pings ingame of 140ms well done Idnet!!!

Rik · Jan 31, 2009, 13:56:21

I don't think it's as simple as IDNet:

ping multiplay.co.uk

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

Reply from 85.236.96.22: bytes=32 time=34ms TTL=124
Reply from 85.236.96.22: bytes=32 time=34ms TTL=124
Reply from 85.236.96.22: bytes=32 time=23ms TTL=124
Reply from 85.236.96.22: bytes=32 time=25ms 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 = 23ms, Maximum = 34ms, Average = 29ms

but if you're not happy then your best bet is to try another ISP.

Ray · Jan 31, 2009, 14:09:14

Something seems to be amiss somewhere, Rik, my pings are not good at the moment, although I don't game so they don't affect me.

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

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

Reply from 85.236.96.22: bytes=32 time=28ms TTL=124
Reply from 85.236.96.22: bytes=32 time=48ms TTL=124
Reply from 85.236.96.22: bytes=32 time=82ms TTL=124
Reply from 85.236.96.22: bytes=32 time=62ms 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 = 28ms, Maximum = 82ms, Average = 55ms

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

Reply from 212.58.224.138: bytes=32 time=81ms TTL=122
Reply from 212.58.224.138: bytes=32 time=110ms TTL=122
Reply from 212.58.224.138: bytes=32 time=104ms TTL=122
Reply from 212.58.224.138: bytes=32 time=107ms 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 = 81ms, Maximum = 110ms, Average = 100ms

Simon · Jan 31, 2009, 14:31:17

Can't profess to know what it means, but for what it's worth:

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

Reply from 85.236.96.22: bytes=32 time=34ms TTL=124
Reply from 85.236.96.22: bytes=32 time=38ms TTL=124
Reply from 85.236.96.22: bytes=32 time=39ms TTL=124
Reply from 85.236.96.22: bytes=32 time=39ms 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 = 34ms, Maximum = 39ms, Average = 37ms

Rik · Jan 31, 2009, 14:35:20

I'm not seeing an issue, Ray, and we should be on the same pipe:

ping multiplay.co.uk

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

Reply from 85.236.96.22: bytes=32 time=24ms TTL=124
Reply from 85.236.96.22: bytes=32 time=23ms TTL=124
Reply from 85.236.96.22: bytes=32 time=22ms TTL=124
Reply from 85.236.96.22: bytes=32 time=22ms 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 = 22ms, Maximum = 24ms, Average = 22ms

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=25ms TTL=122
Reply from 212.58.224.138: bytes=32 time=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=22ms TTL=122
Reply from 212.58.224.138: bytes=32 time=24ms 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 = 22ms, Maximum = 25ms, Average = 23ms

If it continues, run a longer ping, eg 10-20 pings, then let support have the result.

Ray · Jan 31, 2009, 15:10:10

Strange, Rik, mine are still about 3 times higher than yours, they're usually about the same as yours. $:-\$

Rik · Jan 31, 2009, 15:12:30

It's definitely one for support if it continues, Ray. (Do you think I have a charmed path?

)

Ray · Jan 31, 2009, 15:13:52

Quote from: Rik on Jan 31, 2009, 15:12:30
It's definitely one for support if it continues, Ray. (Do you think I have a charmed path? )

Yes, Rik, I reckon you've got your own private pipe into Idnet.

Rik · Jan 31, 2009, 15:22:07

Simon brought a bit of wet string over at Xmas...

Simon · Jan 31, 2009, 15:22:36

I'd rather have had a hamper!

David · Jan 31, 2009, 15:25:15

If I had a hamper,I,d hamper out danger

Rik · Jan 31, 2009, 15:26:01

You watched American Folk too, eh?

David · Jan 31, 2009, 15:29:50

Its no picnic being me you know........we all have our crosses to bear and I dont like making a fuss

Ray · Jan 31, 2009, 15:31:13

Just got these results using WinMTR: -

[attachment deleted by admin]

David · Jan 31, 2009, 15:33:01

Thats nice Ray

MarkE · Jan 31, 2009, 15:56:15

I take it this problem wouldnt be caused by the idnet new service rollout of adsl2? Just hair pullingly annoying,even webpages are crawling.

Rik · Jan 31, 2009, 16:00:30

No, there is no rollout unless you're on a WBC-enabled exchange and signed up to test.

MarkE · Jan 31, 2009, 19:04:06

Well I have left a message on Simons answerphone regarding this problem

Reply from 85.236.96.22: bytes=32 time=171ms TTL=124
Reply from 85.236.96.22: bytes=32 time=122ms TTL=124
Reply from 85.236.96.22: bytes=32 time=132ms TTL=124
Reply from 85.236.96.22: bytes=32 time=108ms TTL=124

Rik · Jan 31, 2009, 19:05:35

Don't be surprised if you don't hear before Monday, pings are not normally regarded as an emergency.

MarkE · Jan 31, 2009, 19:41:44

Quote from: Rik on Jan 31, 2009, 19:05:35
Don't be surprised if you don't hear before Monday, pings are not normally regarded as an emergency.

No but maybe customers taking their good money elsehwere might be? I have a national team match tomorrow for the uk,and its currently up to 200ms,i cant even barely browse the web
isnt that the barest i should be able to do on a £34 a month connection?

I just also tried pinging www.idnet.net and got

Reply from 212.69.36.10: bytes=32 time=94ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=120ms TTL=59

Lance · Feb 01, 2009, 00:06:49

Mark, I see from reading back through the posts that you have tried rebooting your router several times - but have you left it off for half hour or so? I know this is normally the method to clear a stale session but it can also help with other issues.

FWIW here is my ping to the same IP address in your post above:

C:\Users\Lance>ping 85.236.96.22

Pinging 85.236.96.22 with 32 bytes of data:
Reply from 85.236.96.22: bytes=32 time=31ms TTL=124
Reply from 85.236.96.22: bytes=32 time=30ms TTL=124
Reply from 85.236.96.22: bytes=32 time=31ms TTL=124
Reply from 85.236.96.22: bytes=32 time=30ms 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 = 30ms, Maximum = 31ms, Average = 30ms

Sebby · Feb 01, 2009, 01:56:56

Quote from: MarkE on Jan 31, 2009, 19:41:44

No but maybe customers taking their good money elsehwere might be? I have a national team match tomorrow for the uk,and its currently up to 200ms,i cant even barely browse the web
isnt that the barest i should be able to do on a £34 a month connection?

I just also tried pinging www.idnet.net and got

Reply from 212.69.36.10: bytes=32 time=94ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=120ms TTL=59

All we can advise is that you get in contact with IDNet, which you have.

ducky22 · Feb 01, 2009, 15:06:25

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:\>