High pings again

zappaDPJ · Jul 31, 2009, 15:19:32

Yeah

(and I'm still a little baffled by it to be honest).

Rik · Jul 31, 2009, 15:23:16

Is it holding at that level?

mynnydd · Jul 31, 2009, 15:28:05

oh my god, explain that one then

I only pay 'upto 8mb'

Dopamine · Jul 31, 2009, 15:31:01

I'm not a gamer so have never worried about pings, nor understand why they are important, but mine yesterday evening and now are around 300ms. Would this account for pages feeling sluggish to start opening? Once they commence loading, speed is fine, and throughput on my 7150 profile is averaging around 5mbps at the moment, so that is acceptable too.

A router reboot last night instantly returned pings to 35ms and throughput to 6.8mbps, but pings have slowly crept up since, and speed slowed. Is it time to give up on IDNet, or is the issue understood and being worked on?

Rik · Jul 31, 2009, 15:35:01

Understood and being worked on.

mynnydd · Jul 31, 2009, 15:37:22

Quote from: Rik on Jul 31, 2009, 15:23:16
Is it holding at that level?

245ms on speedtest.net
then 101ms on speed.io straight after
so I guess (as previously advised) a manual start up ping is the only reliable test.

karser · Jul 31, 2009, 15:39:24

Thankfully got my mac code today, they told me it was almost rebalanced just 2 days ago.... looks like it

[attachment deleted by admin]

Rik · Jul 31, 2009, 15:40:43

Quote from: mynnydd on Jul 31, 2009, 15:37:22
so I guess (as previously advised) a manual start up ping is the only reliable test.

It is.

Rik · Jul 31, 2009, 15:41:13

Quote from: karser on Jul 31, 2009, 15:39:24
Thankfully got my mac code today, they told me it was almost rebalanced just 2 days ago.... looks like it

Have you decided where to go? Let us know how things are, will you?

zappaDPJ · Jul 31, 2009, 15:50:54

Quote from: Rik on Jul 31, 2009, 15:23:16
Is it holding at that level?

No, it hit 8ms once, yesterday evening. I was gutted

@Dopamine. Pings are important because if a player positions his cursor over an object and hits the fire button with high latency the object may well have moved on before his packet of information hits the destination server. In short he'll miss the target.

In my experience 300ms would have a noticeable impact on surfing, particularly as you've found when you first hit the site.

Rik · Jul 31, 2009, 15:53:44

To which we might need to add the issue of DNS response time, of course.

I'd be interested to know just what BT did to your line, have you checked to see if there's a part-used drum of fibre just up the road?

pup · Jul 31, 2009, 15:58:29

Quote from: Glenn on Jul 30, 2009, 17:23:34
I'm a happy chappie sort of. On Brian's request he asked for a ping graph with the laptop in safe mode, it gave the same results So I swapped the laptop for another I have here with a broken screen, I ran the ping graph on there and it works.

All I need to do now is rebuild this W7rc laptop.

Thanks again Brian.

Makes me wonder if the os or software is causing a problem

Rik · Jul 31, 2009, 15:59:23

Don't forget the user in this particular instance, Pup.

Ray · Jul 31, 2009, 16:00:11

MarkE · Jul 31, 2009, 16:00:36

Quote from: zappaDPJ on Jul 31, 2009, 15:50:54
No, it hit 8ms once, yesterday evening. I was gutted

@Dopamine. Pings are important because if a player positions his cursor over an object and hits the fire button with high latency the object may well have moved on before his packet of information hits the destination server. In short he'll miss the target.

In my experience 300ms would have a noticeable impact on surfing, particularly as you've found when you first hit the site.

Indeed and then try that at an international based level playing for your country in nation cups and clanbase cups and esl invitationals and see what fun it isn't ...

I have just pinged multiplay.co.uk and im getting 300ms and i have tried router reboots.Some of the days I have had to do no less than 15 to 20 reboots to just get 100ms...

I have just phoned support and spoke to Miriam,she is going to phone me back in 30 minutes.

zappaDPJ · Jul 31, 2009, 16:05:33

[EDIT] In reply to Rik... (I seem to have broken the quote button

)

There's some Kelloggs Fruit 'n'Fibre in the cupboard if that counts

It was the timing of it that baffles me. My line was getting progressively worse all evening and then at midnight my coach arrived, pings dropped and throughput went up at least five fold. I was half expecting the Prince of Packet Loss to turn up on my doorstep in the morning with a big spanner but all is still fine

Rik · Jul 31, 2009, 16:07:38

Quote from: MarkE on Jul 31, 2009, 16:00:36
I have just pinged multiplay.co.uk and im getting 300ms and i have tried router reboots.Some of the days I have had to do no less than 15 to 20 reboots to just get 100ms...

I have just phoned support and spoke to Miriam,she is going to phone me back in 30 minutes.

This won't be of much consolation, but from my interleaved WBC line (the Max is pretty much identical):

ping www.mulitplay.co.uk

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

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

Rik · Jul 31, 2009, 16:08:51

Quote from: zappaDPJ on Jul 31, 2009, 16:05:33
[EDIT] In reply to Rik... (I seem to have broken the quote button )

There's some Kelloggs Fruit 'n'Fibre in the cupboard if that counts

Oh no you haven't.

QuoteIt was the timing of it that baffles me. My line was getting progressively worse all evening and then at midnight my coach arrived, pings dropped and throughput went up at least five fold. I was half expecting the Prince of Packet Loss to turn up on my doorstep in the morning with a big spanner but all is still fine

A lot of BT changes seem to happen in the 00:00 - 02:00 span, I don't know why.

MarkE · Jul 31, 2009, 16:09:00

That is odd,as at what i consider lower congestion times,ping times were still hugely unacceptable to servers that are based down the road from me in Maidenhead.

Rik · Jul 31, 2009, 16:10:21

Do a tracert and see how you're getting to them.

MarkE · Jul 31, 2009, 16:11:32

over a maximum of 30 hops: multiplay.co.uk

1 <1 ms <1 ms <1 ms 192.168.0.1
2 113 ms 104 ms 122 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 111 ms 103 ms 103 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243

4 72 ms 71 ms 68 ms lonap2.enta.net [193.203.5.135]
5 89 ms 88 ms 109 ms te5-3.gs1.core.enta.net [78.33.35.218]
6 111 ms 93 ms 102 ms te1-1.interxion.core.enta.net [87.127.236.86]
7 101 ms 103 ms 131 ms gi4-3.enta-transit.as35028.net [84.45.252.122]
8 134 ms 139 ms 157 ms www1.multiplay.co.uk [85.236.96.22]

juiceuk · Jul 31, 2009, 16:13:29

Quote from: mynnydd on Jul 31, 2009, 15:06:10
Rik could you recommend a general book on the ins and outs of broadband?

http://www.kitz.co.uk/index.htm -Kitz has got a nice amount of information on it.

What I'm getting at the moment.

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

Reply from 212.69.36.10: bytes=32 time=76ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=97ms TTL=59
Reply from 212.69.36.10: bytes=32 time=64ms TTL=59
Reply from 212.69.36.10: bytes=32 time=107ms TTL=59
Reply from 212.69.36.10: bytes=32 time=82ms TTL=59
Reply from 212.69.36.10: bytes=32 time=156ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=62ms TTL=59
Reply from 212.69.36.10: bytes=32 time=75ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=113ms TTL=59
Reply from 212.69.36.10: bytes=32 time=69ms TTL=59
Reply from 212.69.36.10: bytes=32 time=108ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms TTL=59

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

Never bothered turning the router off last night in the end because it started to settle down and I actually had one of my best rounds of battlefield 2142 (71 kills 8 deaths). FPS are very latency dependent, you have to change your style of play if your ping changes. I actually play with a few people that have pings of between 4ms and 10ms, they look at you and your dead. Ping graph at the bottom is last night.

[attachment deleted by admin]

Rik · Jul 31, 2009, 16:14:03

tracert www.multiplay.co.uk

Tracing route to core1.multiplay.co.uk [85.236.96.22]
over a maximum of 30 hops:

1 3 ms <1 ms 1 ms home [192.168.1.254]
2 26 ms 23 ms 25 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 26 ms 27 ms 25 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 26 ms 27 ms 25 ms lonap2.enta.net [193.203.5.135]
5 26 ms 25 ms 27 ms te5-3.gs1.core.enta.net [78.33.35.218]
6 27 ms 29 ms 29 ms te1-1.interxion.core.enta.net [87.127.236.86]
7 27 ms 25 ms 27 ms gi4-3.enta-transit.as35028.net [84.45.252.122]
8 27 ms 25 ms 25 ms www1.multiplay.co.uk [85.236.96.22]

Trace complete.

MarkE · Jul 31, 2009, 16:15:02

indeed the style of play ends up turtle/defensive however in some fast paced games 170 to 300ms just wont get you nowhere regardless of how much experience you have when the opponents are
all on a solid 30ms

Rik · Jul 31, 2009, 16:15:23

Quote from: juiceuk on Jul 31, 2009, 16:13:29
What I'm getting at the moment.

I can only suggest you follow the procedure here.