Latency - Sunday 16:52 18/2/07

neocr0n · Feb 18, 2007, 16:54:42

Hi just checking in to see if everyone is experiencing some minor latency jumping today, in the region of 60/70ms.

I just got a new router but with IDnets current state its kind of hard to tell if its my router/settings/network or IDnet thats the problem.

Edit: Date added for clarity

Nova · Feb 18, 2007, 17:16:26

Seeing the same here.

Nerval · Feb 18, 2007, 17:29:07

From the thread title, I thought that today had been designated "Latency Sunday".

And from the performance of my PC, I wouldn't have been surprised.
Yes everything is bad here at the moment.

neocr0n · Feb 18, 2007, 17:46:19

Quote from: Nerval on Feb 18, 2007, 17:29:07
From the thread title, I thought that today had been designated "Latency Sunday".
And from the performance of my PC, I wouldn't have been surprised.
Yes everything is bad here at the moment.

Haha!, alright guys thanks, just needed to make sure it wasn't all me.

Rik · Feb 18, 2007, 17:53:32

Even I'm seeing pings at 2-3x normal, and I don't normally notice. Mind you, as long as I've been on the 'net, Sunday evenings have always shown the worst performance.

maxping · Feb 18, 2007, 18:02:32

Higher than normal here but not into the hundreds yet so my fingers are crossed.

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

Reply from 212.69.36.10: bytes=32 time=53ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=37ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms 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 = 25ms, Maximum = 53ms, Average = 36ms

Rik · Feb 18, 2007, 18:38:53

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

Reply from 212.69.36.10: bytes=32 time=48ms TTL=60
Reply from 212.69.36.10: bytes=32 time=45ms TTL=60
Reply from 212.69.36.10: bytes=32 time=43ms TTL=60
Reply from 212.69.36.10: bytes=32 time=52ms 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 = 43ms, Maximum = 52ms, Average = 47ms

Though I do have interleaving on.

siege2 · Feb 18, 2007, 18:42:06

Pinging www.idnet.co.uk [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=33ms TTL=60
Reply from 212.69.36.10: bytes=32 time=41ms TTL=60
Reply from 212.69.36.10: bytes=32 time=41ms 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 = 32ms, Maximum = 41ms, Average = 36ms

with a MTU on router off 1400 and PC 1310 "so I can play TA Springs" :-)

siege2 · Feb 18, 2007, 18:46:12

also if you are interested

Tracing route to www.idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 30 ms 30 ms telehouse-gw-msdp.idnet.net [*.*.*.*]
3 31 ms 30 ms 30 ms 212.69.63.10
4 42 ms 32 ms 32 ms redbus-gw.idnet.net [212.69.63.1]
5 35 ms 33 ms 31 ms www.idnet.net [212.69.36.10]

Trace complete.

maxping · Feb 18, 2007, 18:57:22

Looking good

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

Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=25ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms 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 = 25ms, Maximum = 28ms, Average = 26ms

siege2 · Feb 18, 2007, 18:59:22

cavillas · Feb 18, 2007, 19:01:09

Is "latency Sunday" a precursor to Lent, or am I in the wrong forum again.

MoHux · Feb 18, 2007, 19:04:21

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

Reply from 212.69.36.10: bytes=32 time=19ms TTL=60
Reply from 212.69.36.10: bytes=32 time=18ms TTL=60
Reply from 212.69.36.10: bytes=32 time=20ms TTL=60
Reply from 212.69.36.10: bytes=32 time=19ms 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 = 18ms, Maximum = 20ms, Average = 19ms

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

Reply from 212.69.36.10: bytes=32 time=19ms TTL=60
Reply from 212.69.36.10: bytes=32 time=18ms TTL=60
Reply from 212.69.36.10: bytes=32 time=17ms TTL=60
Reply from 212.69.36.10: bytes=32 time=18ms 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 = 17ms, Maximum = 19ms, Average = 18ms

maxping · Feb 18, 2007, 19:07:43

Mo i aint even going to try to beat that

MoHux · Feb 18, 2007, 19:15:15

Nova · Feb 19, 2007, 05:44:36

Reply from 212.69.36.10: bytes=32 time=17ms TTL=60
Reply from 212.69.36.10: bytes=32 time=17ms TTL=60
Reply from 212.69.36.10: bytes=32 time=17ms TTL=60
Reply from 212.69.36.10: bytes=32 time=16ms 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 = 16ms, Maximum = 17ms, Average = 16ms

-----

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

Reply from 212.69.36.10: bytes=32 time=18ms TTL=60
Reply from 212.69.36.10: bytes=32 time=17ms TTL=60
Reply from 212.69.36.10: bytes=32 time=16ms TTL=60
Reply from 212.69.36.10: bytes=32 time=16ms 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 = 16ms, Maximum = 18ms, Average = 16ms

Ping faster yo ;-)

Nova

maxping · Feb 19, 2007, 18:10:56

Best yet

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

Reply from 212.69.36.10: bytes=32 time=8ms TTL=60
Reply from 212.69.36.10: bytes=32 time=6ms TTL=60
Reply from 212.69.36.10: bytes=32 time=8ms TTL=60
Reply from 212.69.36.10: bytes=32 time=6ms 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 = 6ms, Maximum = 8ms, Average = 7ms

Lance · Feb 19, 2007, 18:12:39

right now i want to swear at you max! I'm sooooo jealous!

MoHux · Feb 20, 2007, 00:13:52

'ow did 'e do that!!

siege2 · Feb 20, 2007, 00:33:24

Either got put onto new Pipe FIRST :-) or moved next door or in to IDNET :-)

maxping · Feb 20, 2007, 01:04:18

Or i cheated a little

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

Reply from 212.69.36.10: bytes=32 time=1ms TTL=60
Reply from 212.69.36.10: bytes=32 time=1ms TTL=60
Reply from 212.69.36.10: bytes=32 time=1ms TTL=60
Reply from 212.69.36.10: bytes=32 time=1ms 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 = 1ms, Maximum = 1ms, Average = 1ms

neocr0n · Feb 20, 2007, 01:08:17

Cheat! haha

maxping · Feb 20, 2007, 01:09:27

MoHux · Feb 20, 2007, 01:31:36

Rik · Feb 20, 2007, 09:00:17

Now if only we could really adjust our pings so easily... 8)