High pings again

Started by glen, Jul 20, 2009, 10:34:43

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

MarkE

Quote from: Sebby on Jul 27, 2009, 19:31:31
Good luck with Enta.

to be fair given how often of late pings have been cr*p with idnet,then i will take that luck :)


cannot be any worse

Rik

Do let us know how it compares, Mark. It's always useful to see what the competition is like.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

Quote from: Glenn on Jul 27, 2009, 19:25:57
It's worse here  :(

It also appears to have a different pattern to it. The first graph has a distinctive pulse of lost packets. I have a PC here that produces the same ping graph pattern no matter what the quality of the connection and I can't for the life of me work out what's causing it. The frequency of the pulse, 35-40 seconds, is exactly as displayed in your first graph and it causes the accumulated latency figure to be a number of times higher than the base.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

#228
I have never seen it like that until yesterday, the only thing that happened yesterday was my router rebooted itself, then I had no internet access at around 6 am in the morning, when I got home from work I rebooted it again to get a connection back. After that I got the 35 - 40 second pattern, on 1 laptop, but not the PC. Both the laptop and PC go through the same wiring, Speedtouch 585 v6 > Linksys PSUS4 switch so I have no idea what could cause it.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

Very odd indeed, I wish I could pin it down.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

I've swapped routers and connected to the test socket, I still get the same 35 - 40 second time out cycle. Does yours do the same from the test socket?
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

MarkE

My migration doesnt come through till next tuesday.In the meantime putting up with these unplayable pings...............



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

Reply from 85.236.96.22: bytes=32 time=132ms TTL=124
Reply from 85.236.96.22: bytes=32 time=116ms TTL=124
Reply from 85.236.96.22: bytes=32 time=128ms TTL=124
Reply from 85.236.96.22: bytes=32 time=172ms TTL=124


What exactly are idnet doing regarding the balancing because that is not looking too good for me here,luckily my hairs pretty short else i would be bald by now  :laugh:

Rik

Quote from: MarkE on Jul 29, 2009, 17:18:59
luckily my hairs pretty short else i would be bald by now  :laugh:

Stop boasting. ;D

Have you spoken to support? The network should be re-balanced now (I checked at lunchtime).
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Gary

All day my pings have been pretty good they maxed at 40ms earlier but now they are fine.

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

Damned, if you do damned if you don't

Gary

Quote from: MarkE on Jul 29, 2009, 17:18:59
My migration doesnt come through till next tuesday.In the meantime putting up with these unplayable pings...............



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

Reply from 85.236.96.22: bytes=32 time=132ms TTL=124
Reply from 85.236.96.22: bytes=32 time=116ms TTL=124
Reply from 85.236.96.22: bytes=32 time=128ms TTL=124
Reply from 85.236.96.22: bytes=32 time=172ms TTL=124


What exactly are idnet doing regarding the balancing because that is not looking too good for me here,luckily my hairs pretty short else i would be bald by now  :laugh:
here are mine to that address

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

C:\Users\>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=36ms TTL=124
Reply from 85.236.96.22: bytes=32 time=30ms TTL=124
Reply from 85.236.96.22: bytes=32 time=30ms TTL=124
Reply from 85.236.96.22: bytes=32 time=33ms 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 = 36ms, Average = 32ms

Damned, if you do damned if you don't

Glenn

I'll cheer you all up  ;D

[attachment deleted by admin]
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Gary

Quote from: Glenn on Jul 29, 2009, 17:30:20
I'll cheer you all up  ;D
Stop using spaghetti to your router  ;D
Damned, if you do damned if you don't

MarkE

Quote from: Rik on Jul 29, 2009, 17:20:33
Stop boasting. ;D

Have you spoken to support? The network should be re-balanced now (I checked at lunchtime).



I gave up on support and settled on biding my time to migrate Rik lol

Gary

Quote from: MarkE on Jul 29, 2009, 17:33:19


I gave up on support and settled on biding my time to migrate Rik lol
I get 32ms to your multiplay addy ping wise as I said since they balanced the network, email them, you are only here for a few days, whats there to loose  ;D
Damned, if you do damned if you don't

Glenn

Quote from: Gary on Jul 29, 2009, 17:32:22
Stop using spaghetti to your router  ;D

Brian is currently looking into the problem
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

It grows n trees you know ;D
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

karser

Going to request my mac tomorrow I think

[attachment deleted by admin]

Glenn

Looking at my graph and karser's, the noise on both, increase around the same time  ??? To me that would appear to be congestion on the central, I'm most likely wrong though.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Congestion can't affect NM though, that's a purely local issue.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

I was referring to the ping time increase
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Ah, it's just you said noise. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

A poor choice of words  :blush:
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

You know they never get past me, Glenn. ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.