Speed Problem 20th August [2005]

sburrell

Well-Known Member
Joined
Apr 8, 2005
Messages
327
Reaction score
0
Location
Cape Town
Any Body elese having problems with international bandwidth today?

C:\Documents and Settings\60 degrees>ping www.google.com

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

Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.187.99: bytes=32 time=912ms TTL=238

Ping statistics for 64.233.187.99:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 912ms, Maximum = 912ms, Average = 912ms
 
Yes me too.

I'm also timing out on pings to Google. Google Earth, iTunes Radio, it seems all bandwidth internationally is almost dead.
 
My best effort to the uk nevemind my non existant gw play.

Pinging bbc.co.uk [212.58.224.131] with 32 bytes of data:

Request timed out.
Reply from 212.58.224.131: bytes=32 time=896ms TTL=113
Reply from 212.58.224.131: bytes=32 time=892ms TTL=113
Request timed out.

Ping statistics for 212.58.224.131:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 892ms, Maximum = 896ms, Average = 894ms
 
yup...I can't get mail from gmail via pop.

also getting 900ms ping to google with 50% lost packets.


Edit: does anyone know the SAIX network incident webpage URL?
 
Last edited:
two words! F#*& Telkom!

( and can you believe the audasity of it all, as I write this, A Telkom Ad came on TV. Dreams Come True my ASS!)
 
20/08/2005: 10:45

Experiencing bad performance on Sentech, ADSL seems fine ...

Google: 765ms RTT, 20% packet loss - Sentech MyWireless
Google: 259ms RTT, 0% packet loss - SAOL unshaped
 
SAIX Network Notice Update
----------------------------------------------------------------------

Reference ID : STT000000004231
Failure Type : Network Failure
Problem Description : New York to Rosebank-Link down
Impact : Customers will experience intermittent connectivity to international sites
Time Down : 20 Aug, 2005 at 07:00:00 (SAT)
Time Up : None
Sites : New York
Services Affected : International
Update Description : Our technicians are still busy investigating.
 
Same - WOW pings of between 4000-8000!!! WTF!!!??? G-mail also basically unusable
 
Pinging www.l.google.com [64.233.183.99] with 32 bytes of data:

Reply from 64.233.183.99: bytes=32 time=441ms TTL=238
Reply from 64.233.183.99: bytes=32 time=447ms TTL=238
Reply from 64.233.183.99: bytes=32 time=476ms TTL=238
Reply from 64.233.183.99: bytes=32 time=413ms TTL=238


oh wait im not using ADSL hiehiehie :)
 
Pinging google.com [216.239.37.99] with 32 bytes of data:

Reply from 216.239.37.99: bytes=32 time=923ms TTL=240
Request timed out.
Reply from 216.239.37.99: bytes=32 time=909ms TTL=240
Request timed out.

Ping statistics for 216.239.37.99:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 909ms, Maximum = 923ms, Average = 916ms
 
% ping google.com
PING google.com (216.239.39.99): 56 data bytes
64 bytes from 216.239.39.99: icmp_seq=0 ttl=239 time=235.672 ms
64 bytes from 216.239.39.99: icmp_seq=1 ttl=239 time=233.358 ms
64 bytes from 216.239.39.99: icmp_seq=2 ttl=239 time=234.123 ms
64 bytes from 216.239.39.99: icmp_seq=3 ttl=239 time=233.763 ms
64 bytes from 216.239.39.99: icmp_seq=3 ttl=239 time=233.763 ms
^C
--- google.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 233.358/234.072/235.672/0.844 ms


Woops ye, i dont use adsl either ;p
 
Wait 1 second. WTF, Rosebank to New York..... Checking SAIX website......

How the hell is it possible to connect via undersea cable from Rosebank (a landlocked city) to New York. Also check this out .....

http://www.saix.net/diagrams/ipnet_jul05.pdf

It makes no sense, the only 2 international connections should be SAFE and SAT3. I doubt weather it can be an international fault as only one city is reporting problems. Could be a local SAIX stuff up, or could it be that you are not using the cable as previously thought. Still it could be congestion, which is impossible on ADSL as each DSLAM has a unique connection to the ISP, but if the ISP is overloaded it could explain it.

If Telkom cannot cope with the demand, they would naturally increase pricing to create less of a demand for their crappy service. Hence November's price increase.
 
Last edited:
WHY! Need WoW! Need blackend defias leather set at AH. NEED BUYOUT!


GRR ..... i hate telkom #$$&*@^$ DOGS!
 
Top
Sign up to the MyBroadband newsletter
X