Cybersmart - packet loss on international

D

Digilus

Senior Member
Joined
Mar 19, 2007
Messages
653
Reaction score
67
Location
Gordons Bay
Greetings all,

Figured I'd ask and see if I am a special case (as in this just happening to me) or if others are getting it....

Since the whole Seacom oopsie on Thursday (which Seacom says is fixed as per their twitter feed) I've had some really bad international browsing experiences (not bad sites .. just bad connection). MSN kept disconnecting (annoying cause it is used for work) and international sites seemed slow all the way down to unresponsive.

So I've run a few tracerts to a few sites overseas (ranging from cnn to some of my hosted sites on amazon etc) and it seems that the first jump after 217.78.88.* brings up a huge amount of packet loss .. ranging from 20 odd percent .. to 80 percent on my latest attempt.

I'd almost say this looks like heavy international shaping (or they've run out of capacity) ... cause surely if there was THIS much packet loss .. they might look into it?

No specific request here .. just if other Cybersmart users can tell me I am not nuts .. then I'll bring it up with them in the morning
 
See below:

Reuben@TRLTech said:
Cybersmart is currently awaiting international bandwidth upgrades which should be completed by the end of the month if all goes well.

So clients might experience higher than normal pings / timeouts (random times during the day), depending on how busy the network is at that time.
Click to expand...
 
International browsing is really slow with lots of timeouts - I am on Cybersmart as well
 
Digilus said:
Ta Michael - not a word of that on their support page. Guess I'll just twiddle thumbs and hope for the best come end of the month.
Click to expand...

No probs...

Alternative would be FNB Connect / MTN / Eassy @ R 12.38 per GB (50GB bundle - unshaped) until TRL Tech / Cybersmart / Seacom @ R 9.50 per GB (50GB bundle - unshaped) bandwidth capacity has been upgraded and Seacom cable issues have been resolved.

I do suggest you stay clear of ISP's that employ shaping like MWEB / WA - shaping = oversold capacity or utilise IS network like Afrihost.
 
Last edited:
i wonder if this is the cause of my battlefield woes then... i struggle to connect to EA and can't seem to keep a connection to their servers resulting in me getting kicked. i dont' get any packet loss doing a pingtest but the ping itself is through the roof. browsing seems fine though... gmail is a bit slow but it's often like that.
 
I'm with PCFLive, with is on the Cybersmart network afaik. Downloads and torrents are running at full speed, but latencies is sky high (300-1500ms).
 
I've also noticed that with Cybersmart I cannot get onto the EA servers but when I change over to FNBconnect then I connect and can play games perfectly. This on a 384 line is quite decent. Cybersmart sucks!
 
saloojee said:
I've also noticed that with Cybersmart I cannot get onto the EA servers but when I change over to FNBconnect then I connect and can play games perfectly. This on a 384 line is quite decent. Cybersmart sucks!
Click to expand...
that's good to know actually, i was starting to worry it might have something to do with something my side the longer it went on :P local pings are normal again, international still grade F :P
 
No real problems here on my 384k post outage... just frequent disconnects today... about 4 since this morning... have to try a few times to reconnect, then all OK again.. until another disconnect. Other than that... no real problems locally or international.
 
kilobitsperyear said:
No real problems here on my 384k post outage... just frequent disconnects today... about 4 since this morning... have to try a few times to reconnect, then all OK again.. until another disconnect. Other than that... no real problems locally or international.
Click to expand...

kilobitsperyear what happens if you try a pingtest to say maidenhead in uk?
 
Fresh From The Grave said:
kilobitsperyear what happens if you try a pingtest to say maidenhead in uk?
Click to expand...

Here you go....

ping maidenhead.co.uk

Pinging maidenhead.co.uk [174.120.138.59] with 32 bytes of data:
Reply from 174.120.138.59: bytes=32 time=333ms TTL=47
Reply from 174.120.138.59: bytes=32 time=337ms TTL=47
Reply from 174.120.138.59: bytes=32 time=338ms TTL=47
Reply from 174.120.138.59: bytes=32 time=337ms TTL=47

Ping statistics for 174.120.138.59:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 338ms, Average = 336ms

* grins *

37402145.png
 
Last edited:
kilobitsperyear said:
Here you go....

ping maidenhead.co.uk

Pinging maidenhead.co.uk [174.120.138.59] with 32 bytes of data:
Reply from 174.120.138.59: bytes=32 time=333ms TTL=47
Reply from 174.120.138.59: bytes=32 time=337ms TTL=47
Reply from 174.120.138.59: bytes=32 time=338ms TTL=47
Reply from 174.120.138.59: bytes=32 time=337ms TTL=47

Ping statistics for 174.120.138.59:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 338ms, Average = 336ms

* grins *

37402145.png
Click to expand...

well yours is normal... mine's not lol xD
http://www.pingtest.net/result/37402508.png

you should see it when it starts doing the pingtest it's like 1000ms jitter, had 13000 ping lol xD
 
Last edited:
Mine pretty much normal again:

Pinging www.cybersmart.co.za [196.41.124.12] with 32 bytes of data:
Reply from 196.41.124.12: bytes=32 time=64ms TTL=58
Reply from 196.41.124.12: bytes=32 time=68ms TTL=58
Reply from 196.41.124.12: bytes=32 time=67ms TTL=58
Reply from 196.41.124.12: bytes=32 time=68ms TTL=58

Ping statistics for 196.41.124.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 68ms, Average = 66ms

Pinging www.bbc.net.uk [212.58.244.70] with 32 bytes of data:
Reply from 212.58.244.70: bytes=32 time=306ms TTL=48
Reply from 212.58.244.70: bytes=32 time=303ms TTL=48
Reply from 212.58.244.70: bytes=32 time=303ms TTL=48
Reply from 212.58.244.70: bytes=32 time=303ms TTL=48

Ping statistics for 212.58.244.70:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 303ms, Maximum = 306ms, Average = 303ms
 
if i try the same pings as you guys i start getting packet loss now...

first time:
Pinging www.bbc.net.uk [212.58.244.66] with 32 bytes of data:
Reply from 212.58.244.66: bytes=32 time=216ms TTL=48
Reply from 212.58.244.66: bytes=32 time=219ms TTL=48
Reply from 212.58.244.66: bytes=32 time=217ms TTL=48
Reply from 212.58.244.66: bytes=32 time=221ms TTL=48

Ping statistics for 212.58.244.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 216ms, Maximum = 221ms, Average = 218ms

2nd time:
Pinging www.bbc.net.uk [212.58.244.66] with 32 bytes of data:
Request timed out.
Reply from 212.58.244.66: bytes=32 time=221ms TTL=48
Request timed out.
Reply from 212.58.244.66: bytes=32 time=224ms TTL=48

Ping statistics for 212.58.244.66:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 221ms, Maximum = 224ms, Average = 222ms

1st time:
Pinging maidenhead.co.uk [174.120.138.59] with 32 bytes of data:
Request timed out.
Reply from 174.120.138.59: bytes=32 time=385ms TTL=46
Request timed out.
Reply from 174.120.138.59: bytes=32 time=440ms TTL=46

Ping statistics for 174.120.138.59:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 385ms, Maximum = 440ms, Average = 412ms

2nd time:
Pinging maidenhead.co.uk [174.120.138.59] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

oh noes D:

local is fine though:
Pinging www.cybersmart.co.za [196.41.124.12] with 32 bytes of data:
Reply from 196.41.124.12: bytes=32 time=24ms TTL=60
Reply from 196.41.124.12: bytes=32 time=23ms TTL=60
Reply from 196.41.124.12: bytes=32 time=22ms TTL=60
Reply from 196.41.124.12: bytes=32 time=23ms TTL=60

Ping statistics for 196.41.124.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 24ms, Average = 23ms
 
Last edited:
Since Thursday my internet has been crawling allowing, last night tried to download a 32kb file and it took 14min! im on the night rider bundle with cyberdumb, and im so glad to see its not just me! ive reset my router, updated firmware, done virus scans. Defrag. hell i even vacuumed out my pc. Cause according to the FAQ up on their website seacom is up since Sunday. Least they can do is send me a freaking mail or post something on their website...
 
saloojee said:
I've also noticed that with Cybersmart I cannot get onto the EA servers but when I change over to FNBconnect then I connect and can play games perfectly. This on a 384 line is quite decent. Cybersmart sucks!
Click to expand...

same problem here but with cod bo, stays at "Fetching Stats" screen but I can use Steam, very strange.

I phoned in today complaining about it and was told that everything should be sorted out by next week.
 
FreddyB said:
Since Thursday my internet has been crawling allowing, last night tried to download a 32kb file and it took 14min! im on the night rider bundle with cyberdumb, and im so glad to see its not just me! ive reset my router, updated firmware, done virus scans. Defrag. hell i even vacuumed out my pc. Cause according to the FAQ up on their website seacom is up since Sunday. Least they can do is send me a freaking mail or post something on their website...
Click to expand...

i'm also on the nightrider bundle but not really having speed issues to be honest. i wouldn't have guessed there was a problem just from my browsing or downloading. pingtests and traceroutes however reveal that something is mighty wrong o.O

NomNom said:
same problem here but with cod bo, stays at "Fetching Stats" screen but I can use Steam, very strange.

I phoned in today complaining about it and was told that everything should be sorted out by next week.
Click to expand...

let's hope so! i had to order another game just so i have something to play while battlefield is inaccessible D: it would be nice if they like, you know, warned people -.-
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X