Terrible latency to international?

[BeLgaRiOn]

Good day all,

Is anyone else experiencing erratic connectivity to international and getting horrendous lag? (2000ms plus?).

I'm with TelkomInternet ISP and ever since last week my connection has been dodgey at best. I'm also on 512 ADSL. I did a tracert to a WoW server and this is what I got:

Tracing route to 80.239.181.20. [80.239.181.20]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 10.0.0.2

2 23 ms 12 ms 11 ms dsl-145-128-01.telkomadsl.co.za [165.145.128.1]

3 11 ms 11 ms 12 ms tbnb-ip-esr-2-gig-6-1-0-615.telkom-ipnet.co.za [196.43.10.122]

4 11 ms 11 ms 11 ms tbnb-ip-esr-2-gig-6-1-0-615.telkom-ipnet.co.za [196.43.10.122]

5 * * 439 ms lon-ip-dir-telecity-pos-5-0.telkom-ipnet.co.za [196.43.9.50]

6 * * * Request timed out.

7 441 ms 432 ms 432 ms ldn-b1-geth4-0.telia.net [213.248.100.217]

8 461 ms 463 ms 466 ms ldn-bb1-link.telia.net [80.91.250.91]

9 440 ms * * prs-bb1-pos6-0-0.telia.net [213.248.64.9]

10 * * * Request timed out.

11 471 ms 464 ms 459 ms prs-nant-ks51-geth0-2.telia.net [213.248.98.78]

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * *

 

[magneto]

5 390 ms 389 ms 392 ms lon-ip-dir-telecity-pos-5-0.telkom-ipnet.co.za [196.43.9.50]
6 379 ms 372 ms 376 ms ldn-tch-i1-link.telia.net [213.155.141.153]
7 380 ms 393 ms 391 ms ldn-b1-geth4-0.telia.net [213.248.100.217]
8 400 ms 402 ms 401 ms ldn-bb2-pos1-2-0.telia.net [213.248.74.13]
9 416 ms 417 ms 574 ms prs-bb2-pos6-0-0.telia.net [213.248.65.114]
10 400 ms 535 ms 388 ms prs-b2-pos11-0.telia.net [213.248.65.226]
11 393 ms 390 ms 395 ms prs-nant-ks51-link.telia.net [80.91.249.62]

looks about rite for int traffic 300ms-400ms..

 

[Xarog]

Telkom's pings have been funny for me in the last few days. Seems they've started implementing timed packet-shaping. I.e. heavy shaping during the day with less shaping at night.

Maybe that's the cause of the difference. Either way, the time of the pings should also be added to really get a clear picture.

 

[squ3al]

Trying to play wow atm. pings range from 1500 - 3000 wtf.

 

[proff]

Here's why...

Call Reference ID : STT000000005049
Failure Type : Network Failure

Problem Description : Line down from Cape Town to New Doornfontein

Time Down : 5 Sep 2006, 15:30:00

Impact : All customers might experience slow intermittent browsing.

Site : Cape Town

Services Affected : All customers

Cause of Failure : Unknown

Status : New

Cheers
Proff

 

[arf9999]

motherf####! Always when I need to get some info...

40% packet loss atm on international!

 

[clynton]

I tried using Ventrilo for in game chat and it kept reporting a ping of 22000.
Usually get a ping off the servers for Calll of Duty 2 of 400 and for BF2 it's usually around 500 to 700

 

[krycor]

Shaped, saix:

Pinging dsl-mud.org [63.166.155.222] with 32 bytes of data:
Ping statistics for 63.166.155.222:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 902ms, Maximum = 1193ms, Average = 1048ms

Here we go again..

 

[MrG]

yeah, today its the same problem TEL****

 

[arf9999]

Same problem tonight?

>ping google.com -t

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

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

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

>ping www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:

Reply from 196.2.63.110: bytes=32 time=59ms TTL=113
Reply from 196.2.63.110: bytes=32 time=45ms TTL=113
Reply from 196.2.63.110: bytes=32 time=48ms TTL=113
Reply from 196.2.63.110: bytes=32 time=81ms TTL=113

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

>ping google.com -t

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

Reply from 64.233.187.99: bytes=32 time=403ms TTL=237
Reply from 64.233.187.99: bytes=32 time=388ms TTL=235
Reply from 64.233.187.99: bytes=32 time=389ms TTL=237
Reply from 64.233.187.99: bytes=32 time=390ms TTL=235
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.187.99: bytes=32 time=392ms TTL=237
Reply from 64.233.187.99: bytes=32 time=388ms TTL=235
Request timed out.
Request timed out.
Reply from 64.233.187.99: bytes=32 time=393ms TTL=237
Reply from 64.233.187.99: bytes=32 time=386ms TTL=235
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.187.99: bytes=32 time=391ms TTL=235
Request timed out.

Ping statistics for 64.233.187.99:
    Packets: Sent = 23, Received = 9, Lost = 14 (60% loss),
Approximate round trip times in milli-seconds:
    Minimum = 386ms, Maximum = 403ms, Average = 391ms

 

[Xarog]

50% packet loss here. How can Telkom call itself an ISP?

 

[SuperAntMD]

Am I right this isnt just TelkomInternet customers but everyone on SAIX, Im even struggling to get google to load and im not with Telscum

 

[arf9999]

I'm with WA... it's a SAIX problem... again.

 

[Xarog]

Telkom = SAIX.

I'm with Mweb, btw.

 

[Dmitrimm]

Same problem here.