next »

[Splinter]

After the heavy rain last night, I've noticed a slow down in my connection and a ping test showed 66Ms, whereas normally it's about 30.
Could rain ingress be causing this I wonder? Possibly the cables in the junction box outside.

[Wooster]

Could be, but it also depends on what you are pinging.
If it's somewhere distant, then there could be some problems on the network forcing the packets to take a longer route.

Have a play around with pathping, it might show you where the problem is.

i.e.

Code:

pathping [url=http://www.google.com]www.google.com[/url] -q 10

[Splinter]

Wooster, this is what I got putting in my web addresss:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Marc>pathping -n www.compufixshop.com

Tracing route to compufixshop.com [97.74.144.97]
over a maximum of 30 hops:
  0  192.168.1.102
  1  192.168.1.1
  2  10.0.0.2
  3  200.3.60.4
  4  200.3.92.73
  5  190.224.165.114
  6  195.22.220.213
  7  195.22.221.197
  8  64.208.110.209
  9  67.17.104.213
 10  64.209.110.218
 11  208.109.112.153
 12  208.109.112.142
 13  216.69.188.77
 14  216.69.188.102
 15  97.74.144.97

Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           192.168.1.102
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2    1ms     0/ 100 =  0%     0/ 100 =  0%  10.0.0.2
                                0/ 100 =  0%   |
  3   16ms     0/ 100 =  0%     0/ 100 =  0%  200.3.60.4
                                0/ 100 =  0%   |
  4   16ms     0/ 100 =  0%     0/ 100 =  0%  200.3.92.73
                                0/ 100 =  0%   |
  5   17ms     0/ 100 =  0%     0/ 100 =  0%  190.224.165.114
                                0/ 100 =  0%   |
  6   15ms     0/ 100 =  0%     0/ 100 =  0%  195.22.220.213
                                0/ 100 =  0%   |
  7   35ms     0/ 100 =  0%     0/ 100 =  0%  195.22.221.197
                                0/ 100 =  0%   |
  8   40ms     0/ 100 =  0%     0/ 100 =  0%  64.208.110.209
                                0/ 100 =  0%   |
  9  216ms     3/ 100 =  3%     3/ 100 =  3%  67.17.104.213
                                0/ 100 =  0%   |
 10  215ms     0/ 100 =  0%     0/ 100 =  0%  64.209.110.218
                                0/ 100 =  0%   |
 11  200ms     0/ 100 =  0%     0/ 100 =  0%  208.109.112.153
                                0/ 100 =  0%   |
 12  203ms     0/ 100 =  0%     0/ 100 =  0%  208.109.112.142
                                0/ 100 =  0%   |
 13  209ms     0/ 100 =  0%     0/ 100 =  0%  216.69.188.77
                                0/ 100 =  0%   |
 14  ---     100/ 100 =100%   100/ 100 =100%  216.69.188.102
                                0/ 100 =  0%   |
 15  201ms     0/ 100 =  0%     0/ 100 =  0%  97.74.144.97

Trace complete.

C:\Documents and Settings\Marc>

Doesn't mean a lot to me, except that n# 9 and 14 look dodgy.
Ping has come back down to 33 (using speedtest.net) from 69 overnight.
Are there any physical improvements one can ake to redice lag/ping/latency?
Cheers mate

[Thermalsig]

Are you on cable or DSL Splint? 9 looks like a poor jump(dodgy connection) and 14 looks like it was either off line or unresponsive. In total, the packet loss you had was on the very low side. Distance is a huge factor in ping rate. When you say your ping was in the 20's, what are you pinging? I usually only get that low of a ping for servers in southern Texas. 66 is average for some of the servers up north, but still isn't a bad thing.

[Wooster]

Looks like the problem is on hop 9 right enough.
It's in New York apparently, so a fair distance away and one of the major junctions on teh web.
Dig out a US phone book, call some random from New York and give them a bollocking about the state of the network.
It might make you feel a bit better and their reply could be well funny.

[Splinter]

It's DSL (Telecom Argentina), apparently via fibre optic cable at least to the point of entry ie the junction box not far away.
Our package is 3MB that we are paying for, but to be honest I'm not convinced we're getting what we're paying for.
On one occasion I noticed that the speed had dropped dramatically and when i finally spoke to a human, I was informed that they had put us on 1MB, but admitted the error.
3Mb is the most we can get here.
At work I have 3Mb cable which is much more stable:

Tracing route to www.smn.gov.ar [200.16.116.68]
over a maximum of 30 hops:
  0  192.168.1.105
  1  192.168.1.1
  2  186.136.3.1
  3     *        *        *
Computing statistics for 75 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           192.168.1.105
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2   17ms     0/ 100 =  0%     0/ 100 =  0%  186.136.3.1
                              100/ 100 =100%   |
  3  ---     100/ 100 =100%     0/ 100 =  0%  0.0.0.0

Trace complete.

Maybe I'm being paranoid.
I've been using Speedtest.net if that helps.

[Wooster]

Speedtest can get a bit congested at times.

Have you tried Numion?
Results look like this..
http://www.numion.com/YourSpeed3/ShowMeasurement.php?ID=73,076,742

[Stevie]

When you're doing these kids of test it's best to use the same destination ip every time.

4.2.2.2 is always up

Btw, it's a bigass DNS server if you ever need to use external, as is 4.2.2.3, 4.2.2.4,

[Wooster]

Google's DNS server is pretty easy to remember as well: 8.8.8.8 or 8.8.4.4