Anyone else having major issues with international traffic?

CPTBoy

Expert Member
Joined
Dec 1, 2011
Messages
1,419
Reaction score
442
Local is fine, but international is pretty much dead.

Pings are fine and traceroutes to international sites are also fine, but downloading / browsing / streaming is horrible on anything outside South Africa.

Tested on 3 account

Plugg 4mb uncapped
WebAfrica capped
Afrihost capped

I get the same results with all 3 of them. Can a faulty exchange or line do this? I highly doubt it, because my local traffic is ok.
 
I get 565ms and 25% packet loss to local.. MWEB/Telkom tell me its exhcange congestion. I think thats become the new excuse for any fault.

>ping mweb.co.za

Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=11ms TTL=122
Reply from 196.2.63.110: bytes=32 time=565ms TTL=122
Request timed out.
Reply from 196.2.63.110: bytes=32 time=26ms TTL=122

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 565ms, Average = 200ms
 
Buuuut... under my circumstances... international is "ok".

>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=167ms TTL=239
Reply from 212.58.241.131: bytes=32 time=226ms TTL=239
Request timed out.
Reply from 212.58.241.131: bytes=32 time=156ms TTL=239

Ping statistics for 212.58.241.131:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 156ms, Maximum = 226ms, Average = 183ms
 
afrihost uncapped jhb

PING bbc.co.uk (212.58.241.131) 56(84) bytes of data.
64 bytes from 212.58.241.131: icmp_seq=1 ttl=237 time=190 ms
64 bytes from 212.58.241.131: icmp_seq=2 ttl=237 time=190 ms
64 bytes from 212.58.241.131: icmp_seq=3 ttl=237 time=190 ms
64 bytes from 212.58.241.131: icmp_seq=4 ttl=237 time=189 ms
 
Top
Sign up to the MyBroadband newsletter
X