High Pings earlier .

ou7shined · Jan 07, 2007, 23:55:16

Thanks Mike, it's perversely reassuring that we might all be in the same boat.

AvengerUK · Jan 08, 2007, 12:43:31

- From 22:00 onwards it fully cleared up - although it wasnt all that bad in the first place!

Everything since that time has been flat as a lake!

AvengerUK · Jan 08, 2007, 19:39:02

Why o why do i open my mouth...

Are they back again or is it just me?

DorsetBoy · Jan 08, 2007, 20:04:18

Pings and speeds are back to VERY erratic again.

maxping · Jan 08, 2007, 20:07:15

Quote from: AvengerUK on Jan 08, 2007, 19:39:02
Why o why do i open my mouth...

Are they back again or is it just me?

Bad here also.

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

Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=45ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=35ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=35ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=52ms TTL=60
Reply from 212.69.36.10: bytes=32 time=37ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=35ms TTL=60
Reply from 212.69.36.10: bytes=32 time=41ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=50ms TTL=60
Reply from 212.69.36.10: bytes=32 time=57ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=61ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=53ms TTL=60
Reply from 212.69.36.10: bytes=32 time=72ms TTL=60
Reply from 212.69.36.10: bytes=32 time=64ms TTL=60
Reply from 212.69.36.10: bytes=32 time=67ms TTL=60
Reply from 212.69.36.10: bytes=32 time=94ms TTL=60
Reply from 212.69.36.10: bytes=32 time=64ms TTL=60
Reply from 212.69.36.10: bytes=32 time=84ms TTL=60
Reply from 212.69.36.10: bytes=32 time=73ms TTL=60
Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=55ms TTL=60
Reply from 212.69.36.10: bytes=32 time=53ms TTL=60
Reply from 212.69.36.10: bytes=32 time=69ms TTL=60
Reply from 212.69.36.10: bytes=32 time=42ms TTL=60
Reply from 212.69.36.10: bytes=32 time=45ms TTL=60
Reply from 212.69.36.10: bytes=32 time=47ms TTL=60
Reply from 212.69.36.10: bytes=32 time=60ms TTL=60
Reply from 212.69.36.10: bytes=32 time=57ms 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=34ms TTL=60
Reply from 212.69.36.10: bytes=32 time=36ms TTL=60
Reply from 212.69.36.10: bytes=32 time=46ms TTL=60
Reply from 212.69.36.10: bytes=32 time=72ms TTL=60
Reply from 212.69.36.10: bytes=32 time=65ms TTL=60
Reply from 212.69.36.10: bytes=32 time=31ms TTL=60
Reply from 212.69.36.10: bytes=32 time=68ms TTL=60
Reply from 212.69.36.10: bytes=32 time=66ms TTL=60
Reply from 212.69.36.10: bytes=32 time=42ms TTL=60
Reply from 212.69.36.10: bytes=32 time=52ms TTL=60
Reply from 212.69.36.10: bytes=32 time=65ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=34ms TTL=60
Reply from 212.69.36.10: bytes=32 time=76ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=64ms TTL=60

AvengerUK · Jan 08, 2007, 20:14:20

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

Reply from 85.236.96.22: bytes=32 time=74ms TTL=120
Reply from 85.236.96.22: bytes=32 time=65ms TTL=120
Reply from 85.236.96.22: bytes=32 time=70ms TTL=120
Request timed out.
Reply from 85.236.96.22: bytes=32 time=135ms TTL=120
Reply from 85.236.96.22: bytes=32 time=99ms TTL=120
Reply from 85.236.96.22: bytes=32 time=90ms TTL=120
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 85.236.96.22:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 135ms, Average = 88ms

Interesting note: it only times out as much as this to MP when the pings are having issues! - only times out through routes which go through enta...i think.

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

Reply from 212.69.36.10: bytes=32 time=100ms TTL=60
Reply from 212.69.36.10: bytes=32 time=79ms TTL=60
Reply from 212.69.36.10: bytes=32 time=70ms TTL=60
Reply from 212.69.36.10: bytes=32 time=69ms TTL=60

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 100ms, Average = 79ms

maxping · Jan 08, 2007, 20:17:38

Its not just you mate.

I'm going to try the 30 min switch off and see if it helps.

Pinging 85.236.96.22 with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=98ms TTL=120
Reply from 85.236.96.22: bytes=32 time=104ms TTL=120
Reply from 85.236.96.22: bytes=32 time=111ms TTL=120
Reply from 85.236.96.22: bytes=32 time=97ms TTL=120

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 111ms, Average = 102ms

Pinging 85.236.96.22 with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=124ms TTL=120
Reply from 85.236.96.22: bytes=32 time=87ms TTL=120
Reply from 85.236.96.22: bytes=32 time=110ms TTL=120
Reply from 85.236.96.22: bytes=32 time=152ms TTL=120

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 152ms, Average = 118ms

Pinging 85.236.96.22 with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=136ms TTL=120
Request timed out.
Reply from 85.236.96.22: bytes=32 time=126ms TTL=120
Reply from 85.236.96.22: bytes=32 time=55ms TTL=120

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 136ms, Average = 105ms

jackmalanak · Jan 08, 2007, 20:21:15

Never had a problem until now BUT today I'm seeing the same sort of things. Just pinged idnet and results were returned in the high 100's

AvengerUK · Jan 08, 2007, 20:24:44

Quote from: maxping on Jan 08, 2007, 20:17:38
Its not just you mate.

I'm going to try the 30 min switch off and see if it helps.

- let us know the results, i may follow suit!

ou7shined · Jan 08, 2007, 20:51:31

How'd ya like them apples?

I didn't think that was possible.

Lance · Jan 08, 2007, 22:00:34

Nothing wrong this end...

C:\Documents and Settings\Administrator.LANCES>ping www.idnet.net -n 10

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

Reply from 212.69.36.10: bytes=32 time=14ms TTL=60
Reply from 212.69.36.10: bytes=32 time=22ms TTL=60
Reply from 212.69.36.10: bytes=32 time=20ms TTL=60
Reply from 212.69.36.10: bytes=32 time=15ms TTL=60
Reply from 212.69.36.10: bytes=32 time=15ms TTL=60
Reply from 212.69.36.10: bytes=32 time=22ms TTL=60
Reply from 212.69.36.10: bytes=32 time=17ms TTL=60
Reply from 212.69.36.10: bytes=32 time=14ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60

Ping statistics for 212.69.36.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 22ms, Average = 16ms

This is easily the best i have ever got. I occasionally maybe get one ping under 20 but 13 is by the the lowest i have ever had! i have previously normally been around 26.

philco · Jan 08, 2007, 22:03:16

bad for me too.

[attachment deleted by admin]

TimJ · Jan 08, 2007, 22:47:29

3 Lines - 3 exchanges - 3 similar l8nc graphs

1st 2 are my lines - the 3rd is from AvengerUK's sig

maxping · Jan 09, 2007, 00:42:24

QuoteI'm going to try the 30 min switch off and see if it helps.

I don't know if it was a coincidence but my pings returned to normal after i switched off the router for 30 mins.

Pinging 85.236.96.22 with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=25ms TTL=120
Reply from 85.236.96.22: bytes=32 time=25ms TTL=120
Reply from 85.236.96.22: bytes=32 time=24ms TTL=120
Reply from 85.236.96.22: bytes=32 time=24ms TTL=120

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 25ms, Average = 24ms

Pinging 85.236.96.22 with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=29ms TTL=120
Reply from 85.236.96.22: bytes=32 time=24ms TTL=120
Reply from 85.236.96.22: bytes=32 time=37ms TTL=120
Reply from 85.236.96.22: bytes=32 time=26ms TTL=120

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 37ms, Average = 29ms

Pinging 85.236.96.22 with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=29ms TTL=120
Reply from 85.236.96.22: bytes=32 time=27ms TTL=120
Reply from 85.236.96.22: bytes=32 time=25ms TTL=120
Reply from 85.236.96.22: bytes=32 time=36ms TTL=120

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 36ms, Average = 29ms

philco · Jan 09, 2007, 08:05:01

Maybe just coincidence, Mine seemed to be ok again at about midnight.

AvengerUK · Jan 09, 2007, 12:55:14

Proberbly coincidence - it got alot better for me also!

Simon_idnet · Jan 09, 2007, 14:18:15

We have seen that the traffic through our Centrals has become unbalanced
recently. This is particularly apparent during the highest peak hours of 8pm
to 10pm. We are working at re-balancing the traffic.

We have more capacity due to come online at the end of February which will
alleviate the problem. The sudden increase in traffic has been due to an
unforeseen influx of customers recently.

Apologies to those affected.
Regards
Simon

houseparty · Jan 09, 2007, 14:50:42

Quote from: simon on Jan 09, 2007, 14:18:15
We have seen that the traffic through our Centrals has become unbalanced
recently. This is particularly apparent during the highest peak hours of 8pm
to 10pm. We are working at re-balancing the traffic.

We have more capacity due to come online at the end of February which will
alleviate the problem. The sudden increase in traffic has been due to an
unforeseen influx of customers recently.

Apologies to those affected.
Regards
Simon

yes im sure thats the problem, i notice cr*p pings, slow webpages loading during busy hours, i went on the net at 7 this morning and it was great, really nice and enjoyable, but it goes sllllooooooowwwwwwwww during peak hours.

I then notice the pages loading better towards 10 at ight, and by 11 tey are nice and fast again.

I think members on this forum have brought this on too ourselfs, we have said how good idnet is and now they everyone wants too join idnet, that is causing us problems, like this one...........lol

AvengerUK · Jan 09, 2007, 15:11:18

Thanks for the update

I think *most* isp's have seen a large increase of customers recently due to the amount of ISP's that have collapsed!

"I think members on this forum have brought this on too ourselfs, we have said how good idnet is and now they everyone wants too join idnet, that is causing us problems, like this one...........lol"

The pings werent extremely bad, so hopefully it wont get much worse - but i have not noticed a single "slow down" - speeds remain at my max at any hour....so im happy!

mrapoc · Jan 09, 2007, 16:20:52

sometimes it helps to grin and bear it - unless you have a clan match on a game or a job that relies on your net

AvengerUK · Jan 09, 2007, 16:26:46

Quote from: mrapoc on Jan 09, 2007, 16:20:52
sometimes it helps to grin and bear it - unless you have a clan match on a game or a job that relies on your net

Wouldnt that just involve more "grinning"

maxping · Jan 09, 2007, 18:01:01

Quote from: houseparty on Jan 09, 2007, 14:50:42

yes I'm sure thats the problem, i notice cr*p pings, slow webpages loading during busy hours, i went on the net at 7 this morning and it was great, really nice and enjoyable, but it goes sllllooooooowwwwwwwww during peak hours.

I then notice the pages loading better towards 10 at ight, and by 11 tey are nice and fast again.

Simon has given the reason and remember exchange contention will also play a part at peak times.

QuoteI think members on this forum have brought this on too ourselfs, we have said how good idnet is and now they everyone wants too join idnet, that is causing us problems, like this one...........lol

I don't see it as a problem , in the 12 months there has only been one other instance of high pings and it was fixed quickly.
As more users join more money fills the bank account so more can be invested in keeping IDNet thew way we like it.

/takes fanboy hat off

maxping · Jan 09, 2007, 18:02:16

Quote
Apologies to those affected.
Regards
Simon

Thanks for the update Simon.

maxping · Jan 09, 2007, 18:30:31

Pings are spot on here @ 18:35

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

Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 27ms, Average = 25ms

Lance · Jan 09, 2007, 18:37:14

here too @ 18:41

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

Reply from 212.69.36.10: bytes=32 time=15ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=15ms TTL=60
Reply from 212.69.36.10: bytes=32 time=15ms TTL=60
Reply from 212.69.36.10: bytes=32 time=14ms TTL=60
Reply from 212.69.36.10: bytes=32 time=20ms TTL=60
Reply from 212.69.36.10: bytes=32 time=18ms TTL=60
Reply from 212.69.36.10: bytes=32 time=15ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60

Ping statistics for 212.69.36.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 27ms, Average = 17ms