Latency (North East England)

Started by neocr0n, Jul 16, 2007, 17:37:17

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

neocr0n

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

Reply from 212.69.36.10: bytes=32 time=103ms TTL=61
Reply from 212.69.36.10: bytes=32 time=88ms TTL=61
Reply from 212.69.36.10: bytes=32 time=54ms TTL=61
Reply from 212.69.36.10: bytes=32 time=59ms TTL=61

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

C:\Documents and Settings\jonny>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.224.86] with 32 bytes of data:

Reply from 212.58.224.86: bytes=32 time=98ms TTL=250
Reply from 212.58.224.86: bytes=32 time=101ms TTL=250
Reply from 212.58.224.86: bytes=32 time=73ms TTL=250
Reply from 212.58.224.86: bytes=32 time=49ms TTL=250

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

C:\Documents and Settings\jonny>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=78ms TTL=61
Reply from 212.69.36.10: bytes=32 time=99ms TTL=61
Reply from 212.69.36.10: bytes=32 time=72ms TTL=61
Reply from 212.69.36.10: bytes=32 time=63ms TTL=61

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


Anyone else been experiencing high latency over the past few days during peak hours?

I must say since IDnet had the new pipeline installed a few month ago my connection has been pretty much flawless.  For the past few days though I have been experiencing high latency during peak hours.

Is this the same for most on IDnet? 

Thanks,

Jonny/neocr0n
Play Counter-Strike 1.6 online 6 years and counting. :(

Rik

I'm seeing consistent pings in the 21-24ms range for both IDNet and the BBC. This is with interleaving on.

I'd suggest using the -n switch and run 10-20 pings to each, then cut'n'paste the results in an email to support. They can then have a look for you.
Rik
--------------------

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

neocr0n

Play Counter-Strike 1.6 online 6 years and counting. :(

DorsetBoy

ping -n 10 www.bbc.co.uk       

Rik

If you use ping <URL> -n X, where X is an integer, it will ping the site that number of times before reporting, eg

ping www.bbc.net.uk -n 10

Pinging www.bbc.net.uk [212.58.224.116] with 32 bytes of data:

Reply from 212.58.224.116: bytes=32 time=21ms TTL=251
Reply from 212.58.224.116: bytes=32 time=22ms TTL=251
Reply from 212.58.224.116: bytes=32 time=21ms TTL=251
Reply from 212.58.224.116: bytes=32 time=20ms TTL=251
Reply from 212.58.224.116: bytes=32 time=22ms TTL=251
Reply from 212.58.224.116: bytes=32 time=20ms TTL=251
Reply from 212.58.224.116: bytes=32 time=21ms TTL=251
Reply from 212.58.224.116: bytes=32 time=22ms TTL=251
Reply from 212.58.224.116: bytes=32 time=22ms TTL=251
Reply from 212.58.224.116: bytes=32 time=21ms TTL=251

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



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

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

MoHux

Just taken;  South-West England.

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

Reply from 212.69.36.10: bytes=32 time=26ms TTL=61
Reply from 212.69.36.10: bytes=32 time=26ms TTL=61
Reply from 212.69.36.10: bytes=32 time=28ms TTL=61
Reply from 212.69.36.10: bytes=32 time=31ms TTL=61

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


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

Reply from 212.58.224.131: bytes=32 time=27ms TTL=123
Reply from 212.58.224.131: bytes=32 time=26ms TTL=123
Reply from 212.58.224.131: bytes=32 time=25ms TTL=123
Reply from 212.58.224.131: bytes=32 time=25ms TTL=123

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

Interleaving 'On'
"It's better to say nothing and be thought an idiot - than to open your mouth and remove all doubt."