Slow SAT3 intl bandwidth. Everyone in denial.

brendon9x

Active Member
Joined
Oct 25, 2005
Messages
32
Reaction score
0
International ping times have to gone to hell since last Friday. For your enjoyment, ping 66.249.89.99 (a Google server). If you're lucky enough to have an uncrippled 'unshaped' account (or on a leased line) you should get about 250ms - always. But since last Friday ping times have been consistently around 600ms.

Worse is the packet-loss. It is currently at 2% which is tolerable, but has peaked up to 20% since the Internet lost its legs last week.

As I work on UK-based PC on VNC over VPN, I'm particularly susceptible to latency and hugely affected by any packet loss.

At 5% packet loss you're better off using satellite-based services owing to the delays caused TCP retransmission. When it comes to TCP, your connection speed is roughly correlated to the speed of the slowest packet. At 10% packet loss, it's time to buy yourself a modem. At 20% you may as well start tying little notes to pigeons.

So, basically my job sucks at the moment. Most concerning is the complete denial that there is a problem. The SAiX noticeboard is worryingly devoid of any "Internation latency intolerable" messages. Bunch of muppets.

Usually, the ping times are very consistent. About 250ms, with variation of +-15ms. By the way the pings are swinging so wildly (600 +- 150ms), I reckon that we're close to the limit of international bandwidth. These problems also disappear at night further backing up this theory. I'd be less worried if I knew it was ADSL users that are affected, but no-one I know can get consistent sub 300 anymore.

Knowing Telkom though, we'll have to wait until it gets a lot worse before it gets any better.
 
Last edited:
I noted this last night here.

Web Africa's reply:

I see that the site is hosted internationally.... There was SAIX connectivity issues yesterday, Which could be the reason for the problem.

Not very specific or informative with regards to if/when it will be resolved.
 
I too have noticed this in the last couple of weeks

I bought myself an unshaped account specifically so I can play online games

With my shaped account I used to average about 650ms latency and with my unshaped account about 200ms latency

However over the past couple of weeks my with my unshaped account I am now averaging 600ms, too scared to see what my shaped account will look like

This suxor
 
Strangely, my shaped SAIX account was averaging about 440ms to the server that I usually play on.
 
--- www.l.google.com ping statistics ---
51 packets transmitted, 51 received, 0% packet loss, time 50021ms
rtt min/avg/max/mdev = 183.407/186.765/213.632/4.611 ms, pipe 2

this on the tenet network, which uses sat3 through saix, so the problem is probably elsewhere...
 
[jongi:~#] ping 66.249.89.99
PING 66.249.89.99 (66.249.89.99) 56(84) bytes of data.
64 bytes from 66.249.89.99: icmp_seq=1 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=2 ttl=243 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=3 ttl=244 time=320 ms
64 bytes from 66.249.89.99: icmp_seq=4 ttl=243 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=5 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=6 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=7 ttl=244 time=322 ms
64 bytes from 66.249.89.99: icmp_seq=8 ttl=244 time=320 ms
64 bytes from 66.249.89.99: icmp_seq=9 ttl=243 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=10 ttl=243 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=11 ttl=243 time=322 ms
64 bytes from 66.249.89.99: icmp_seq=12 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=13 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=14 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=15 ttl=244 time=320 ms
64 bytes from 66.249.89.99: icmp_seq=16 ttl=244 time=322 ms

--- 66.249.89.99 ping statistics ---
17 packets transmitted, 16 received, 5% packet loss, time 16011ms
rtt min/avg/max/mdev = 320.527/321.437/322.277/0.712 ms


WebAfrica Prepaid
 
I've received a few replies from Web Africa on this issue and they say it's due to the problems SAIX have been having since the 20th of the month. So there's nothing they can do.

Again, we're the ones who have to pay.
 
Yeah, I also get that at 1am. Unfortunately, I need the bandwidth for work in the day. The problem manifests itself between 8am and 6pm.

[jongi:~#] ping 66.249.89.99
PING 66.249.89.99 (66.249.89.99) 56(84) bytes of data.
64 bytes from 66.249.89.99: icmp_seq=1 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=2 ttl=243 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=3 ttl=244 time=320 ms
64 bytes from 66.249.89.99: icmp_seq=4 ttl=243 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=5 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=6 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=7 ttl=244 time=322 ms
64 bytes from 66.249.89.99: icmp_seq=8 ttl=244 time=320 ms
64 bytes from 66.249.89.99: icmp_seq=9 ttl=243 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=10 ttl=243 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=11 ttl=243 time=322 ms
64 bytes from 66.249.89.99: icmp_seq=12 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=13 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=14 ttl=244 time=321 ms
64 bytes from 66.249.89.99: icmp_seq=15 ttl=244 time=320 ms
64 bytes from 66.249.89.99: icmp_seq=16 ttl=244 time=322 ms

--- 66.249.89.99 ping statistics ---
17 packets transmitted, 16 received, 5% packet loss, time 16011ms
rtt min/avg/max/mdev = 320.527/321.437/322.277/0.712 ms


WebAfrica Prepaid
 
Reply from 66.249.89.99: bytes=32 time=476ms TTL=234
Reply from 66.249.89.99: bytes=32 time=473ms TTL=234
Reply from 66.249.89.99: bytes=32 time=474ms TTL=235
Reply from 66.249.89.99: bytes=32 time=474ms TTL=234
Reply from 66.249.89.99: bytes=32 time=474ms TTL=235
Reply from 66.249.89.99: bytes=32 time=477ms TTL=235

That's using my unshaped SAIX account.

Pinging 66.249.89.99 with 32 bytes of data:

Reply from 66.249.89.99: bytes=32 time=368ms TTL=241
Reply from 66.249.89.99: bytes=32 time=367ms TTL=241
Reply from 66.249.89.99: bytes=32 time=367ms TTL=241
Reply from 66.249.89.99: bytes=32 time=367ms TTL=241
Reply from 66.249.89.99: bytes=32 time=367ms TTL=241
Reply from 66.249.89.99: bytes=32 time=369ms TTL=241

That's using my shaped SAIX account.

Both from Web Africa.
 
Web Africa's reply to this unshaped problem:

There is a link down between the SA and hong kong. This happened last week Thursday, since then we have experienced very bad pings to international servers. What you can do is log a speed problem with Telkom and they will log it with SAIX.
 
Lol.. got a standard IS account with a 384kbps line and its a public holiday.
I shouldnt be laughing!


Reply from 66.249.89.99: bytes=32 time=1422ms TTL=228
Reply from 66.249.89.99: bytes=32 time=1397ms TTL=228
Reply from 66.249.89.99: bytes=32 time=1396ms TTL=228
Reply from 66.249.89.99: bytes=32 time=1409ms TTL=228

Ping statistics for 66.249.89.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1396ms, Maximum = 1422ms, Average = 1406ms
 
There is a link down between the SA and hong kong. This happened last week Thursday, since then we have experienced very bad pings to international servers. What you can do is log a speed problem with Telkom and they will log it with SAIX.

lol @ what you can do... erm YOU ARE THE FREAKIN ISP - right ?

having also issues with unshapped...

webafrica - if you are the isp and we are your clients isn't it your duty to keep us happy and do that type of work and not having your clients phone around ?
 
Just a word of advice... I made the mistake of criticizing WebAfrica, and I got burned very badly.
 
its an honest question:
webafrica - if you are the isp and we are your clients isn't it your duty to keep us happy and do that type of work and not having your clients phone around ?

to:
There is a link down between the SA and hong kong. This happened last week Thursday, since then we have experienced very bad pings to international servers. What you can do is log a speed problem with Telkom and they will log it with SAIX.
..........


for example if you are an software developer then you don't expect you clients to compile your code and then use it - no you give it to them pre-compiled and ready...
 
Most ISP's use Telkom SAIX for their international links (not the only international provider)
as they provide the backbone (because they are Telkom)

I normally contact SAIX direct on their tollfree, normally
should be reserved for SAIX Customers
http://www.saix.net/cgi-bin/saix_contacts.pl
TollFree 0800222772

See outdated ISP Map from Gregory Massel
and SAIX Network Map

Terrible DSL Access (only) from Maginet Hotel access in Nairobi, Kenya
Speedtest
from www.speedtest.net
Costing R250 for 24 hrs
 
Last edited:
I agree with Necuno. We're the ones paying the ISP's - they should do their best to make sure we get what we pay for.
 
Top
Sign up to the MyBroadband newsletter
X