**VERY High Latency - Pretoria**

Z

Zarathustra

Expert Member
Joined
Aug 7, 2003
Messages
1,164
Reaction score
223
Location
South Africa.
Is anyone aware of or is experiencing high latency on web browsing in the Pretoria area?!?

Since late this morning, e-mail (POP3 & SMTP) is working, but web browsing is VERY slow. Takes up to 5 minutes to deliver a single page.

Running 4Mb ADSL line with MWeb as the ISP. Tried switching to the Neotel 'backup' with exactly the same results.
 
Zarathustra said:
Is anyone aware of or is experiencing high latency on web browsing in the Pretoria area?!?

Since late this morning, e-mail (POP3 & SMTP) is working, but web browsing is VERY slow. Takes up to 5 minutes to deliver a single page.

Running 4Mb ADSL line with MWeb as the ISP. Tried switching to the Neotel 'backup' with exactly the same results.
Click to expand...

I have had the same problem this morning on my 384 line with a telkom account before I left for work, pages taking ages to load.
 
In Centurion Celtisdal Area.

Yea, logged a call with telkom and "they are working on it".

Been having this issue for 3 months intermittent now, and calls always gets closed as the DSL line "appears" to be fine.

here is my pings to telkom.co.za from webafrica ISP.

Reply from 196.43.22.222: bytes=32 time=807ms TTL=246
Reply from 196.43.22.222: bytes=32 time=927ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1074ms TTL=246
Request timed out.
Reply from 196.43.22.222: bytes=32 time=706ms TTL=246
Request timed out.
Request timed out.
Reply from 196.43.22.222: bytes=32 time=703ms TTL=246
Reply from 196.43.22.222: bytes=32 time=876ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1058ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1034ms TTL=246
Reply from 196.43.22.222: bytes=32 time=785ms TTL=246
Reply from 196.43.22.222: bytes=32 time=611ms TTL=246
Reply from 196.43.22.222: bytes=32 time=682ms TTL=246
Reply from 196.43.22.222: bytes=32 time=847ms TTL=246
Reply from 196.43.22.222: bytes=32 time=839ms TTL=246
Request timed out.
Reply from 196.43.22.222: bytes=32 time=721ms TTL=246
Reply from 196.43.22.222: bytes=32 time=844ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1036ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1077ms TTL=246
Reply from 196.43.22.222: bytes=32 time=745ms TTL=246
Reply from 196.43.22.222: bytes=32 time=92ms TTL=246
Reply from 196.43.22.222: bytes=32 time=269ms TTL=246


and tracerts

C:\>tracert -d telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 787 ms 949 ms 1061 ms 196.220.59.250
4 942 ms 620 ms 617 ms 41.185.0.38
5 623 ms 741 ms 887 ms 196.220.59.230
6 1075 ms 1045 ms 744 ms 196.43.11.166
7 344 ms 319 ms 282 ms 196.43.23.6
8 430 ms 479 ms 603 ms 196.43.23.30
9 799 ms 793 ms 906 ms 196.43.22.222
 
Had same problem in Faerie Glen this morning. Will try again tonight when I get home.
 
any updates on this? my line just started acting funny, 4mb watermayer park, tried SAIX unshaped, verizon unshaped, saix normal, is normal all high int pings??
 
Ludjer said:
any updates on this? my line just started acting funny, 4mb watermayer park, tried SAIX unshaped, verizon unshaped, saix normal, is normal all high int pings??
Click to expand...

I am having the same problem but in CT. Local is 100% fine but international is at 450ms pings and 50% packet loss. Think its now an national problem

EDIT: My problem only started 02h30 this morning
 
All back to normal now...Even the Neotel 'backup' is 'fast' this morning...Clearly someone has pressed the correct buttons...
 
CT 512 ADSL line here. Been having the issue with international connections since Monday morning... driving me nuts! Time-outs, low speeds... grrr...
 
Getting the same problems at work this morning.

Local is fine, international is breaking bad.

ping -t google.com

Pinging google.com [209.85.229.105] with 32 bytes of data:
Reply from 209.85.229.105: bytes=32 time=489ms TTL=52
Reply from 209.85.229.105: bytes=32 time=482ms TTL=52
Request timed out.
...
...
Reply from 209.85.229.105: bytes=32 time=493ms TTL=52
Request timed out.

Ping statistics for 209.85.229.105:
Packets: Sent = 54, Received = 32, Lost = 22 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 475ms, Maximum = 495ms, Average = 485ms
 
Pinging google.com [209.85.129.103] with 32 bytes of data:
Reply from 209.85.129.103: bytes=32 time=525ms TTL=51
Reply from 209.85.129.103: bytes=32 time=528ms TTL=51
Request timed out.
Request timed out.
Reply from 209.85.129.103: bytes=32 time=528ms TTL=51
Request timed out.
Request timed out.
Reply from 209.85.129.103: bytes=32 time=528ms TTL=51
Request timed out.
Reply from 209.85.129.103: bytes=32 time=523ms TTL=51
Reply from 209.85.129.103: bytes=32 time=522ms TTL=51


lol.

Tracing route to google.com [74.125.43.147]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 9 ms 9 ms 9 ms 41.185.76.1
3 33 ms 32 ms 31 ms 196.220.59.238
4 32 ms 33 ms 32 ms 41.185.0.30
5 32 ms 32 ms 32 ms 196.220.59.230
6 500 ms * * 196.43.18.94
7 507 ms 510 ms 506 ms 83.245.76.221
8 511 ms * 511 ms 209.85.252.76
9 * * 516 ms 216.239.43.123
10 524 ms * 524 ms 66.249.95.133
11 528 ms * 528 ms 216.239.48.5

lol x 2

Webafrica.
 
Last edited:
my interntional is flying now, but thats because i've started burning my software to dvd's and DHLing them.
 
I’ve been having some problems regarding pings in the Potch area, on Tuesday it was like usual with about 200ms constant ping on www.bbc.net.uk, since yesterday it’s been in the 400 region. At least it’s not fluctuating, but still... Calling Telkom later on.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X