Ping times Jan 28 onwards

[DarkStar]

My PingGraph has had a nice even line between 35/45 since early yesterday and speeds had been consistent at just below 2000. Now I have just come back from tea and speed has gone to the dogs and pings through the roof. Don't have a current ping graph, some fool turned it off  (not me)
I had a reading of 380 just a little while ago.

Ian

Pinging 212.69.40.3 with 32 bytes of data:

Reply from 212.69.40.3: bytes=32 time=147ms TTL=61
Reply from 212.69.40.3: bytes=32 time=165ms TTL=61
Reply from 212.69.40.3: bytes=32 time=124ms TTL=61
Reply from 212.69.40.3: bytes=32 time=163ms TTL=61

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



Tracing route to resolver1.idnet.net [212.69.40.3]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2   177 ms   139 ms   145 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   190 ms   183 ms   161 ms  telehouse-gw1-fa0-0.400.idnet.net [212.69.63.241
]
  4   187 ms   188 ms   190 ms  resolver1.idnet.net [212.69.40.3]

Trace complete.

[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=139ms TTL=59
Reply from 212.69.36.10: bytes=32 time=150ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms 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 = 139ms, Maximum = 154ms, Average = 147ms

C:\Users\David>

[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


Sorry to post just want to compare the two this one taken earlier today hope no-one minds

[Lance]

Reply #701 is bad, but #702 very good, David.

[David]

Vast difference Lance 

[Lance]

Unfortunately so. When were they both run?

[David]

One .the lowest one was this morning..the higher one after tonights drop

[ducky22]

2:19am - awesome pings, very fast.

M:\>ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59

841k/second on a download.

[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=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=12ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=17ms 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 = 17ms, Average = 14ms

C:\Users\David>

Looks like it has recovered for me .I am only posting in a bid to help pinpoint the problem and no other reason

[Rik]

Mine are fine too, David.

[David]

  8)

[Steve]

No issues for me this am. I am assuming the evening problems are due to congestion on one of the pipes. If you can be manually switched to another central am I correct in presuming this is a temporary fix? If you then drop PPP for any reason outside "office hours" you are presumably potentially back to square one until the issue is resolved. Hopefully a weeks walking in the Peak District will solve the problem for me.

[Rik]

It doesn't appear to be congestion at this point, Steve, but IDNet have identified a router problem which could have been the cause.

[Steve]

  Expect they need a break as well

[Rik]

I think they've got one.

[Mohux_Jnr]

My pings have been stable for 48 hours  , just losing browsing capability on the odd occasion several times a day but I can live with that.

[Rik]

That may be explained by Simon's announcement about the router...

[David]

I think they have worked so hard and under,I would imagine unbearable pressure,they deserve any praise they get in my book 

[Ray]

I think they have worked so hard and under,I would imagine unbearable pressure,they deserve any praise they get in my book 

I'll second that, David. 

[Steve]

Dare I say it. Things looking much better this early evening, ping times for me are back to normal and browsing is very snappy No doubt that's put the kaibosh on it.

[Rik]

I'm seeing much better pings today, Steve, with more consistency.

[Dopamine]

I'm seeing much better pings today, Steve, with more consistency.

So was I until about 30 minutes ago. UK sites are slow, many US sites are timing out.
I'm not sure if I'm pinging correctly - should I type "ping xxx.com" or "ping www xxx.com"? - but here are my results:



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

C:\>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=168ms TTL=121
Reply from 212.58.224.138: bytes=32 time=166ms TTL=121
Reply from 212.58.224.138: bytes=32 time=140ms TTL=121
Reply from 212.58.224.138: bytes=32 time=151ms TTL=121

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

C:\>ping idnet.com
Pinging idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=160ms TTL=59
Reply from 212.69.36.10: bytes=32 time=178ms TTL=59
Reply from 212.69.36.10: bytes=32 time=111ms TTL=59
Reply from 212.69.36.10: bytes=32 time=130ms 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 = 111ms, Maximum = 178ms, Average = 144ms

C:\>ping nbc.com
Pinging nbc.com [64.210.192.67] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.210.192.67:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>ping cnn.com
Pinging cnn.com [157.166.226.25] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 157.166.226.25:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>ping google.com
Pinging google.com [209.85.171.100] with 32 bytes of data:

Reply from 209.85.171.100: bytes=32 time=269ms TTL=242
Reply from 209.85.171.100: bytes=32 time=299ms TTL=242
Reply from 209.85.171.100: bytes=32 time=293ms TTL=242
Reply from 209.85.171.100: bytes=32 time=327ms TTL=242

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

C:\>ping google.co.uk
Pinging google.co.uk [66.249.93.104] with 32 bytes of data:

Reply from 66.249.93.104: bytes=32 time=179ms TTL=246
Reply from 66.249.93.104: bytes=32 time=153ms TTL=246
Reply from 66.249.93.104: bytes=32 time=146ms TTL=246
Reply from 66.249.93.104: bytes=32 time=170ms TTL=246

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

[Rik]

Very different to my results, Dopamine:

ping bbc.co.uk

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

Reply from 212.58.224.138: bytes=32 time=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=22ms TTL=122
Reply from 212.58.224.138: bytes=32 time=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=20ms TTL=122

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

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

ping nbc.com

Pinging nbc.com [64.210.192.67] with 32 bytes of data:

Request timed out.


ping www.nbc.com

Pinging a1669.g.akamai.net [88.221.26.49] with 32 bytes of data:

Reply from 88.221.26.49: bytes=32 time=22ms TTL=60
Reply from 88.221.26.49: bytes=32 time=22ms TTL=60
Reply from 88.221.26.49: bytes=32 time=21ms TTL=60
Reply from 88.221.26.49: bytes=32 time=19ms TTL=60

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

ping www.cnn.com

Pinging www.cnn.com [64.236.90.21] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.236.90.21:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping google.com

Pinging google.com [74.125.45.100] with 32 bytes of data:

Reply from 74.125.45.100: bytes=32 time=115ms TTL=244
Reply from 74.125.45.100: bytes=32 time=114ms TTL=244
Reply from 74.125.45.100: bytes=32 time=110ms TTL=244
Reply from 74.125.45.100: bytes=32 time=113ms TTL=244

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

ping google.co.uk

Pinging google.co.uk [72.14.221.104] with 32 bytes of data:

Reply from 72.14.221.104: bytes=32 time=41ms TTL=246
Reply from 72.14.221.104: bytes=32 time=42ms TTL=246
Reply from 72.14.221.104: bytes=32 time=39ms TTL=246
Reply from 72.14.221.104: bytes=32 time=42ms TTL=246

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

[Rik]

NBC seems to have sprung to life now:

tracert www.nbc.com

Tracing route to a1669.g.akamai.net [88.221.26.49]
over a maximum of 30 hops:

  1    <1 ms     1 ms     1 ms  home [192.168.1.254]
  2    25 ms    22 ms    25 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    23 ms    23 ms    21 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    23 ms    21 ms    23 ms  lonap.netarch.akamai.com [193.203.5.72]
  5    23 ms    23 ms    25 ms  a88-221-26-49.deploy.akamaitechnologies.com [88.221.26.49]
Trace complete.

ping www.nbc.com

Pinging a1669.g.akamai.net [88.221.26.49] with 32 bytes of data:

Reply from 88.221.26.49: bytes=32 time=22ms TTL=60
Reply from 88.221.26.49: bytes=32 time=22ms TTL=60
Reply from 88.221.26.49: bytes=32 time=21ms TTL=60
Reply from 88.221.26.49: bytes=32 time=22ms TTL=60

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

[Steve]

This time of the evening has been poor for me for the last 11 days but ok at present

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 - 6620 kbps

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

C:\Users\Steve>ping idnet.net

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

C:\Users\Steve>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=47ms TTL=122
Reply from 212.58.224.138: bytes=32 time=17ms TTL=122
Reply from 212.58.224.138: bytes=32 time=16ms TTL=122
Reply from 212.58.224.138: bytes=32 time=15ms TTL=122

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

C:\Users\Steve>ping google.co.uk

Pinging google.co.uk [216.239.59.104] with 32 bytes of data:
Reply from 216.239.59.104: bytes=32 time=30ms TTL=247
Reply from 216.239.59.104: bytes=32 time=30ms TTL=247
Reply from 216.239.59.104: bytes=32 time=28ms TTL=247
Reply from 216.239.59.104: bytes=32 time=28ms TTL=247

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