Please can anyone ping............

[houseparty]

hi
can a few people here please help.
Using idnet please post there results using Visual ping and pinging too the BBC.
i tried the test 5 times 3 times i saw pocket loss.

i get these results and a few timed out anyone else.
thanks

Pinging www.bbc.co.uk with 32 bytes of data:
Reply from 212.58.226.232 bytes:46 Time:54ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:56ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:47ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:52ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:51ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:48ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:41ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:54ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:45ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:51ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:50ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:53ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:38ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:52ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:44ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:55ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:40ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:40ms TTL:123
Time out.
Reply from 212.58.226.232 bytes:46 Time:55ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:49ms TTL:123
Time out.
Reply from 212.58.226.232 bytes:46 Time:52ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:52ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:41ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:57ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:55ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:47ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:54ms TTL:123
Reply from 212.58.226.232 bytes:46 Time:52ms TTL:123
Ping statistics for www.bbc.co.uk :
Packets: Sent = 30, Received = 28, Lost = 2 (7%) loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 57ms, Average = 49ms

[Rik]

No losses, but a high average, 43ms, compared to low 20s normally.

Tracing route to www.bbc.net.uk [212.58.224.87]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.xxx.xxx.xxx]
  2    50 ms    49 ms    47 ms  telehouse-gw3-msdp.idnet.net [212.69.63.51]
  3    45 ms    48 ms    47 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  4    44 ms    37 ms    40 ms  212.58.238.129
  5    43 ms    50 ms    50 ms  www50.thdo.bbc.co.uk [212.58.224.87]

Trace complete.

Support ask that people email their tracert results to them (support@idnet.net), they are not aware of any general problems at the moment.

[AvengerUK]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

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

Reply from 212.58.224.131: bytes=32 time=23ms TTL=123
Reply from 212.58.224.131: bytes=32 time=20ms TTL=123
Reply from 212.58.224.131: bytes=32 time=21ms TTL=123
Reply from 212.58.224.131: bytes=32 time=23ms 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 = 20ms, Maximum = 23ms, Average = 21ms

C:\Documents and Settings\Simon>ping bbc.co.uk -n 10

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

Reply from 212.58.224.131: bytes=32 time=22ms TTL=123
Reply from 212.58.224.131: bytes=32 time=47ms TTL=123
Reply from 212.58.224.131: bytes=32 time=20ms TTL=123
Reply from 212.58.224.131: bytes=32 time=20ms TTL=123
Reply from 212.58.224.131: bytes=32 time=27ms TTL=123
Reply from 212.58.224.131: bytes=32 time=28ms TTL=123
Reply from 212.58.224.131: bytes=32 time=17ms TTL=123
Reply from 212.58.224.131: bytes=32 time=19ms TTL=123
Reply from 212.58.224.131: bytes=32 time=19ms TTL=123
Reply from 212.58.224.131: bytes=32 time=19ms TTL=123

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

Not a bad day

[Rik]

Have your forwarded that to Support, Avenger? Clearly, something is happening to some of us, so the more data they have the easier it will be to trace.

[AvengerUK]

erm, no i didnt at the time.

I will do so, if you still think its "worth while" doing....

...id hate to clutter up idnet's support inbox if its no longer needed !

[Rik]

They were still monitoring it when I spoke to them yesterday evening, so it would be worth letting them see your results, as it might help establish a geographical connection (or whatever). Thanks.

[AvengerUK]

Ok rik - will send something later, my line changes back to MAX sometime today...so i mayaswell "re-ping" it

[AvengerUK]

EDIT: Yes, it was changed at near enough 12:30 am
(l8nc graph shows interleaving as on)

So far it looks promising - only 1/2 disconnects shown - which, im assuming are due to another 10 day test period? (i moved from max, to fixed, to max again)

[Rik]

Sounds likely, Avenger. Migrating carries the profile, but a speed change wouldn't, I don't think.

Hope you get some benefit from the switch, keep us posted...

[AvengerUK]

Synced at 2666kb/s - best ever!

Download speed at 2meg

[Rik]

Looks like your profile is keeping up quite well. I take it you mean 2656? (or 2688)

[AvengerUK]

2624 atually, near enough

Just off out now...my keyboard has been causing the bios screens to "click" (speaker sound) - now seems that keys are "messed up" e.g i type M and it comes out MV or VM!!!!

o well...it did cost 50 pence a year ago!

[Rik]

That much? I'm amazed at you Avenger.