Ping times Jan 28 onwards

[David]

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

C:\Users\David>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms 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 = 12ms, Maximum = 14ms, Average = 12ms

[Rik]

Can't complain at them. 

[David]

  Thanks Rik.....

Jusut popping out speak soon 

[Rik]

[Simon]

I suppose he had to go out at some point! 

[Rik]

 

I'm keeping quiet.

[David]

I didnt 

[drummer]

Thanks for your reply Simon.  I guess I expected to see updates in Service Announcements but as it's not really a gripe, I'll say no more.

No specific problems, it's just that I didn't want to unnecessarily bombard y'all with my ping stats as I'm sure you've better things to do with your time.  Just thought I'd missed a request to do so is all.

Anyway, switched the router off for about ten minutes and seems to have done the trick. 

[attachment deleted by admin]

[Rik]

That looks much healthier. 

[brizo]

Hi,

Wonder if you could help me as I'm new to all this!

Traceroute has started ...

traceroute to www.idnet.net (212.69.36.10), 64 hops max, 40 byte packets
1  192.168.0.1 (192.168.0.1)  2.613 ms  25.384 ms  26.131 ms
2  telehouse-gw2-lo2.idnet.net (212.69.63.55)  103.130 ms  235.164 ms  111.856 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  112.085 ms  191.261 ms  118.504 ms
4  redbus-gw2-g0-1-331.idnet.net (212.69.63.5)  117.809 ms  138.242 ms  85.237 ms
5  redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)  54.408 ms  53.422 ms  67.491 ms
6  * * *
7  * * *
8  * * *
9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * *

and so on.

Have I got a problem here?

Cheers.

[Rik]

Not necessarily. Try pinging instead, better, ping the IDNet name server, ie hit Start > Run > then type CMD. When the window appears, type ping 212.69.40.3 -n 10. See what that yields.

[brizo]

Thanks for your time Rik, by the way I'm using an iMac!
Ping has started ...

PING 212.69.40.3 (212.69.40.3): 56 data bytes
64 bytes from 212.69.40.3: icmp_seq=0 ttl=61 time=101.175 ms
64 bytes from 212.69.40.3: icmp_seq=1 ttl=61 time=107.481 ms
64 bytes from 212.69.40.3: icmp_seq=2 ttl=61 time=125.928 ms
64 bytes from 212.69.40.3: icmp_seq=3 ttl=61 time=201.057 ms
64 bytes from 212.69.40.3: icmp_seq=4 ttl=61 time=162.766 ms
64 bytes from 212.69.40.3: icmp_seq=5 ttl=61 time=159.334 ms
64 bytes from 212.69.40.3: icmp_seq=6 ttl=61 time=150.200 ms
64 bytes from 212.69.40.3: icmp_seq=7 ttl=61 time=139.882 ms
64 bytes from 212.69.40.3: icmp_seq=8 ttl=61 time=163.594 ms
64 bytes from 212.69.40.3: icmp_seq=9 ttl=61 time=155.354 ms

--- 212.69.40.3 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 101.175/146.677/201.057/27.989 ms

Doesn't look very good! 

[Rik]

Sorry, I kind of assume Windows until firmly corrected.

That doesn't look good. Try re-booting your router. There's been a problem with the new central becoming congested on half its capacity, while the other half remains almost empty. Hopefully, a re-boot will move you, if not, let support know and they can do it manually for you.

[Steve]

Similar to mine I used to be between 15-20ms,rebooting the router x3 has made no difference today, I will check with support during office hours.

>ping 212.69.40.3 -n 10

Pinging 212.69.40.3 with 32 bytes of data:
Reply from 212.69.40.3: bytes=32 time=130ms TTL=61
Reply from 212.69.40.3: bytes=32 time=121ms TTL=61
Reply from 212.69.40.3: bytes=32 time=119ms TTL=61
Reply from 212.69.40.3: bytes=32 time=103ms TTL=61
Reply from 212.69.40.3: bytes=32 time=115ms TTL=61
Reply from 212.69.40.3: bytes=32 time=134ms TTL=61
Reply from 212.69.40.3: bytes=32 time=91ms TTL=61
Reply from 212.69.40.3: bytes=32 time=106ms TTL=61
Reply from 212.69.40.3: bytes=32 time=136ms TTL=61
Reply from 212.69.40.3: bytes=32 time=190ms TTL=61

Ping statistics for 212.69.40.3:
   Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 91ms, Maximum = 190ms, Average = 124ms

[Rik]

IDNet are monitoring, Steve, but obviously the more information the better.

[brizo]

Cheers Rik!

Looks better!!!

Ping has started ...

PING 212.69.40.3 (212.69.40.3): 56 data bytes
64 bytes from 212.69.40.3: icmp_seq=0 ttl=61 time=43.192 ms
64 bytes from 212.69.40.3: icmp_seq=1 ttl=61 time=43.496 ms
64 bytes from 212.69.40.3: icmp_seq=2 ttl=61 time=42.706 ms
64 bytes from 212.69.40.3: icmp_seq=3 ttl=61 time=42.134 ms
64 bytes from 212.69.40.3: icmp_seq=4 ttl=61 time=44.778 ms
64 bytes from 212.69.40.3: icmp_seq=5 ttl=61 time=46.913 ms
64 bytes from 212.69.40.3: icmp_seq=6 ttl=61 time=43.469 ms
64 bytes from 212.69.40.3: icmp_seq=7 ttl=61 time=41.832 ms
64 bytes from 212.69.40.3: icmp_seq=8 ttl=61 time=43.332 ms
64 bytes from 212.69.40.3: icmp_seq=9 ttl=61 time=44.667 ms

--- 212.69.40.3 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 41.832/43.652/46.913/1.408 ms

Still don't get to the end of the traceroute, though. Do you know the reason for this? I also tried www.bbc.co.uk and the same thing happens!

Traceroute has started ...

traceroute to 212.69.36.10 (212.69.36.10), 64 hops max, 40 byte packets
1  192.168.0.1 (192.168.0.1)  2.814 ms  20.693 ms  1.683 ms
2  telehouse-gw2-lo2.idnet.net (212.69.63.55)  61.498 ms  42.861 ms  128.073 ms
3  telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  82.714 ms  404.530 ms  86.996 ms
4  redbus-gw2-g0-1-331.idnet.net (212.69.63.5)  44.590 ms  42.960 ms  74.636 ms
5  redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)  50.920 ms  54.718 ms  54.561 ms
6  * * *
7  * * *

Thanks 

[Rik]

Could just be routers giving low priority to ping traffic, or being heavily loaded. I've noticed, of late, that pinging www.bbc.co.uk times out, while pinging bbc.co.uk works. 

It works for me to IDNet, but the BBC is timing out right now:

tracert www.idnet.net

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

  1     1 ms    <1 ms     1 ms  home [192.168.1.254]
  2    23 ms    25 ms    61 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    27 ms    25 ms    23 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    25 ms    27 ms    27 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    23 ms    25 ms    25 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    25 ms    23 ms    25 ms  www.idnet.net [212.69.36.10]

Trace complete.

tracert www.bbc.co.uk

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

  1    <1 ms     1 ms     1 ms  home [192.168.1.254]
  2    25 ms    25 ms    25 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    25 ms    23 ms    23 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    26 ms    21 ms    23 ms  rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
  5    26 ms    25 ms    23 ms  212.58.238.129
  6    21 ms    23 ms    27 ms  212.58.239.58
  7     *        *        *     Request timed out.

[brizo]

Thanks Rik.

Out of interest, I tried a speed test.

Date   11/02/09 18:16:04
Speed Down   3062.98 Kbps ( 3 Mbps )
Speed Up   373.18 Kbps ( 0.4 Mbps )
Port   8095
Server   speedtest1.thinkbroadband.com

How bad is that  In the good old days, I'd get 6.5 Mbps!

Mmmmm, I think I'll have a beer.

[Rik]

Can't really say whether it's good or bad, because it's missing the vital profile information. Can you try a BT test?

[brizo]

Had to look up the FAQ's to find out how to do it!

Test1 comprises of Best Effort Test:  -provides background information.
    Your DSL connection rate: 8128 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
    IP profile for your line is - 7150 kbps
    Actual IP throughput achieved during the test was - 6160 kbps

If you wish to discuss these results please contact your ISP.

If you are experiencing problems with specific applications, servers or websites please contact your ISP for assistance.

It certainly looks better.

Your test has completed please close this window to exit the performance tester.

[Rik]

Sorry, I should have said. 

That looks OK, not quite as good as it might, but at this time of night, I'd expect to see any exchange congestion taking its toll. If you get a chance to run one in the morning, that would be a useful comparison.

[brizo]

Will do. I'll keep an eye on things.

And thanks for all your help 

[Rik]

My pleasure.

[psp83]

still getting high pings and dns problems! another week of no xbox playing

[David]

Hi Paul see the help section