New IP range - crazy latency

[dotcat]

i have been assigned a 41.x.x.x ip

im seeing very high latency to international site 2000ms

saix internet kzn

anybody else experiencing this?

 

[rpm]

Crazy ADSL latency indeed...got the same...between 1500 and 2000 ms internationally. On DSL 4 Mbps...

 

[Megasurf]

how about 10000ms.

 

[bwana]

i have been assigned a 41.x.x.x ip

im seeing very high latency to international site 2000ms

saix internet kzn

anybody else experiencing this?

Mine seems normal'ish to google.com - not brilliant but not the train smash youre getting

Ping has started ...

PING www.l.google.com (72.14.205.99): 56 data bytes
64 bytes from 72.14.205.99: icmp_seq=0 ttl=238 time=441.925 ms
64 bytes from 72.14.205.99: icmp_seq=1 ttl=238 time=443.197 ms
64 bytes from 72.14.205.99: icmp_seq=2 ttl=238 time=442.416 ms
64 bytes from 72.14.205.99: icmp_seq=3 ttl=238 time=443.389 ms
64 bytes from 72.14.205.99: icmp_seq=4 ttl=238 time=445.910 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 441.925/443.367/445.910/1.377 ms

 

[dotcat]

ping www.google.de

Pinging www.l.google.com [72.14.205.99] with 32 bytes of data:

Reply from 72.14.205.99: bytes=32 time=4031ms TTL=237
Reply from 72.14.205.99: bytes=32 time=3894ms TTL=237
Reply from 72.14.205.99: bytes=32 time=4058ms TTL=237
Reply from 72.14.205.99: bytes=32 time=4332ms TTL=237

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

tracert www.saix.net

Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms 192.168.1.1
2 28 ms 29 ms 29 ms dsl-145-64-01.telkomadsl.co.za [165.145.64.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 181 ms 55 ms 55 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
6 56 ms 54 ms 57 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.
>tracert www.google.com

Tracing route to www.l.google.com [72.14.205.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 28 ms 29 ms 29 ms dsl-145-64-01.telkomadsl.co.za [165.145.64.1]
3 * * * Request timed out.
4 * * * Request timed out.
5 3720 ms 3909 ms 3917 ms lon-ip-dir-telecity-pos-5-0.telkom-ipnet.co.za [
196.43.9.50]
6 3997 ms 3900 ms 3866 ms 83.245.76.221
7 3818 ms 3866 ms 3760 ms 72.14.238.244
8 3837 ms 3843 ms 3826 ms 72.14.236.216
9 3901 ms 3828 ms 3714 ms 72.14.236.213
10 3711 ms 3747 ms 3775 ms 72.14.233.113
11 3662 ms 3718 ms 3686 ms 66.249.94.96
12 3671 ms 3710 ms 3763 ms 72.14.236.142
13 3856 ms 3769 ms 3832 ms qb-in-f99.google.com [72.14.205.99]

Trace complete.

so here we have the offending box

 

[bwana]

@dotcat - according to that traceroute it would appear you're not connected to an ip in the new 41 range.

 

[krycor]

Ping statistics for 63.166.155.222:
Packets: Sent = 25, Received = 19, Lost = 6 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 3817ms, Maximum = 4314ms, Average = 4046ms

Also on the new ip, *cry* and only cause i had to change my firewall settings else i'd still have my 165.x.x.x IP. Is this problem only for those new ip's?

 

[dotcat]

@dotcat - according to that traceroute it would appear you're not connected to an ip in the new 41 range.

i have the 41 ip not the radius server that im connected to

the new ip ranges addressed the problem of new adsl users and therefore there are now new ip ranges that are dished out - i have a 41.x.x.x

 

[Yuu]

Everone please using the following on a SAiX account & post pings if any difference as for me I went from 100KB/s to 400KB/s, downloading so can't do any pings right now

Yes I have been put in the new iP range aswell.

Proxy
cache.saix.net Port 8080

Yuu

 

[krycor]

So where is the stuff up? looks like its either on their own network before or on sat-3 link.

and i see what you mean.. about this
1 <1 ms <1 ms <1 ms 192.168.1.1
2 19 ms 19 ms 19 ms dsl-146-128-01.telkomadsl.co.za [165.146.128.1]

3 * * * Request timed out.
4 * * * Request timed out.
5 21 ms 22 ms 22 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]

According to my router:
IP Address 41.abc.abc.abc
Subnet Mask 255.255.255.255
Default Gateway 165.146.128.1
DNS Server 196.43.46.190

But something i don't get is how the ip can be a 41.x.x.x and the subnet be like that while the gateway is 165.x.x.x ? btw this explains why yesterday my skype was having issues sat-3 thiny again

 

[Bjorn]

Same here pings to google are in the 3500ms to 4500ms, WTH is going on?

 

[Syndyre]

Getting almost 2000ms, also on 41 range.

 

[dotcat]

logged it with saix - if that will help

 

[savage]

According to my router:
IP Address 41.abc.abc.abc
Subnet Mask 255.255.255.255
Default Gateway 165.146.128.1
DNS Server 196.43.46.190

But something i don't get is how the ip can be a 41.x.x.x and the subnet be like that while the gateway is 165.x.x.x ? btw this explains why yesterday my skype was having issues sat-3 thiny again

Because you use PPP (Point to Point Protocol). Quite normal, nothing wrong with that.

You wont easily get any other subnet than 255.255.255.255 on PPP (as it will allow broadcasts over your modem) on PPP, and you will seldom get a Address and Gateway on the same network segment (as your subnet won't allow for a network & broadcast address).

PPP was designed to work this way...

 

[Wynsam]

Pinging www.l.google.com [72.14.221.147] with 32 bytes of data:

Reply from 72.14.221.147: bytes=32 time=3785ms TTL=242
Reply from 72.14.221.147: bytes=32 time=3698ms TTL=242
Reply from 72.14.221.147: bytes=32 time=3899ms TTL=242
Reply from 72.14.221.147: bytes=32 time=4146ms TTL=242

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


I am also on the new IP range (41) and it sucks.

 

[krycor]

ah, i've wondered about that since last yr when i was working with ADSL. The other thing I also wondered about is this: if you traceroute to a domain you will see that there is two hops on the same ip address.. why is that? Someone tried to tell me a while back but they struggled to explain it to me.

I think I will go read up on the PPP standard later this week when i have more time.

 

[killadoob]

guys maybe some sites are just slow today because google is slow and a few other sites but i just think there is general problem

 

[dotcat]

its definitely a general problem - I have pinged sites everywhere in the world
and the tracerts point at a local issue

 

[Kasyx]

1 19 ms 19 ms 21 ms dsl-145-64-01.telkomadsl.co.za [165.145.64.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 3892 ms 3776 ms 3831 ms lon-ip-dir-telecity-pos-6-0.telkom-ipnet.co.za [
196.43.18.94]
5 4054 ms 4120 ms * 83.245.76.221
6 3721 ms 3611 ms 3708 ms 72.14.238.244
7 4002 ms * 4021 ms 72.14.236.216
8 4080 ms 3993 ms 4283 ms 72.14.236.213
9 * 4298 ms 3967 ms 72.14.233.115
10 3928 ms * 3903 ms 66.249.94.96
11 4096 ms 4203 ms * 72.14.236.138
12 * 4257 ms 4211 ms qb-in-f99.google.com [72.14.205.99]

the 2nd and 3rd hops always timeout. wtf?

 

[bullfrog]

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

Reply from 72.14.207.99: bytes=32 time=440ms TTL=239
Reply from 72.14.207.99: bytes=32 time=585ms TTL=239
Reply from 72.14.207.99: bytes=32 time=431ms TTL=239
Reply from 72.14.207.99: bytes=32 time=420ms TTL=239

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

A little slow but still quite normal. I'm also on the 41 range