Brilliant iBurst connection!

19/04/2007 09:12PM Cape Town, Gardens Centre Tower, IP 41.208.224.XXX, 1.07 Mbps

My connections are stable again - after nearly three weeks of poor browsing speeds, high latencies and regular timeouts. (A Telkom dial-up was faster and more reliable – no joking.)

Currently, I have browsing speeds (international & local) that rival Telkom’s 4 Mbps lines, downloads are the fastest I’ve ever seen them, timeouts have disappeared, VoIP sounds like a landline, etc. (All services are working flawlessly at high speed – what a pleasure.)

If you are reading this and you are employed by iBurst (directly or indirectly) or know someone that works in the networking department, please inform them and ask them not to F*** with it EVER again, just leave it alone.

Do you know what it is like using a dial-up connection trying to upload a website, using remote desktop applications and or using a VPN and having to pay for iBurst's broadband access?

Good for you.. for the rest of us it sucks right now...

packet loss is something awful tonight

I agree it's the best it's been for ages, and I'm sure someone from iburst will be reading this thread.

I don't know how they got it to work and quite frankly I don't care as long as they now leave it alone and not try to "improve" it while it's performing the way it is right now.

Hey JT, Sorry to hear about your sh** - but I have 5 usable iBurst modems again after three weeks of dial-up speeds which made using the internet nearly impossible and having non-technical clients bitching at me for not having access to the internet or their emails.

maybe, but still no p2p

For most of JHB connections are super poo tonight, and yes...p2p is still crap as well.

The hub still mostly works tho....*cough* not that we ever see you there s1ght or should I say Mr. "I'll be right back" *cough*

S1ght said:

maybe, but still no p2p

Click to expand...

Nope, theres even P2P in Cape Town.

I'm also on a .224 IP, it is good, very nice low international latency. Local is stable too, and speeds have actually been better than I have seen in ages.

Since it started performing correctly there have been no bad, dead or dying IPs, lets just hope they don't fiddle with it while it's working so well.

I'm on business in PE and the speeds suck big time!! Keep loosing connection as well

Fyi....

From the incident report page on iBurst:

20/04/07 Informative 20/04/07 All iBurst subscribers. INFORMATIVE INFORMATIVE
Details iBurst Core maintenance will take place at midnight (20/04/2007 00:00) for 2 hours.

Please just a request from me to those of you getting extra good connections...what sort of latency are you experiencing locally and internationally?? I would like to know what i-burst is like at its best for interest sake and seeing as they seem to be better in some places lately.

Maybe ping a few int and local sites and post results. Many thanks

Ping Results..

Hi JTS, as requested...

Tracing route to www.l.google.com [216.239.37.99] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 169 ms 44 ms 145 ms wbs-41-208-224-1.wbs.co.za [41.208.224.1]
3 64 ms 49 ms 49 ms 192.168.2.1
4 62 ms 44 ms 144 ms 192.168.4.34
5 113 ms 89 ms 99 ms fe2-1-0sub513.gw1.cpt1.alter.net[196.7.3.101]
6 292 ms 254 ms 359 ms so1-0-3.cr1.lnd19.alter.net [196.30.229.173]
7 313 ms 279 ms 280 ms so0-0-0.ir1.lnd19.alter.net [196.30.229.182]
8 279 ms 259 ms 249 ms so-0-0-1.IH2.LND9.ALTER.NET [146.188.2.241]
9 282 ms 284 ms 259 ms so-2-0-2.TR1.LND9.ALTER.NET [146.188.2.45]
10 268 ms 334 ms 249 ms POS1-0.BR1.LND9.ALTER.NET [146.188.7.242]
11 356 ms 329 ms 359 ms 146.188.35.138
12 358 ms 344 ms 335 ms sl-bb23-lon-3-0.sprintlink.net [213.206.129.151]
13 329 ms 329 ms 324 ms sl-gw23-lon-15-0.sprintlink.net [213.206.128.63]
14 257 ms 244 ms 284 ms sle-eurogoogle-1-0.sprintlink.net [82.195.189.186]
15 347 ms 264 ms 260 ms 66.249.95.130
16 355 ms 339 ms 333 ms 72.14.236.216
17 377 ms 355 ms 358 ms 216.239.46.227
18 447 ms 359 ms 354 ms 216.239.46.225
19 388 ms 355 ms 379 ms 72.14.238.233
20 381 ms 349 ms 334 ms 66.249.95.127
21 372 ms 374 ms 369 ms 72.14.232.108
22 368 ms 364 ms 364 ms 216.239.48.110
23 387 ms 360 ms 384 ms va-in-f99.google.com [216.239.37.99]

Pinging www.myadsl.co.za [196.40.97.12] with 32 bytes of data:
Reply from 196.40.97.12: bytes=32 time=66ms TTL=241
Reply from 196.40.97.12: bytes=32 time=90ms TTL=241
Reply from 196.40.97.12: bytes=32 time=107ms TTL=241
Reply from 196.40.97.12: bytes=32 time=216ms TTL=241
Reply from 196.40.97.12: bytes=32 time=89ms TTL=241
Reply from 196.40.97.12: bytes=32 time=112ms TTL=241
Reply from 196.40.97.12: bytes=32 time=120ms TTL=241
Reply from 196.40.97.12: bytes=32 time=109ms TTL=241
Reply from 196.40.97.12: bytes=32 time=112ms TTL=241
Reply from 196.40.97.12: bytes=32 time=115ms TTL=241
Reply from 196.40.97.12: bytes=32 time=109ms TTL=241
Reply from 196.40.97.12: bytes=32 time=107ms TTL=241
Reply from 196.40.97.12: bytes=32 time=110ms TTL=241
Reply from 196.40.97.12: bytes=32 time=108ms TTL=241
Reply from 196.40.97.12: bytes=32 time=106ms TTL=241
Reply from 196.40.97.12: bytes=32 time=120ms TTL=241
Reply from 196.40.97.12: bytes=32 time=113ms TTL=241
Reply from 196.40.97.12: bytes=32 time=116ms TTL=241
Reply from 196.40.97.12: bytes=32 time=109ms TTL=241
Reply from 196.40.97.12: bytes=32 time=102ms TTL=241
Reply from 196.40.97.12: bytes=32 time=115ms TTL=241
Reply from 196.40.97.12: bytes=32 time=110ms TTL=241
Reply from 196.40.97.12: bytes=32 time=117ms TTL=241
Reply from 196.40.97.12: bytes=32 time=115ms TTL=241
Ping statistics for 196.40.97.12:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 216ms, Average = 112ms


Pinging web1.skype.com [198.173.5.35] with 32 bytes of data:
Reply from 198.173.5.35: bytes=32 time=377ms TTL=47
Reply from 198.173.5.35: bytes=32 time=395ms TTL=47
Reply from 198.173.5.35: bytes=32 time=382ms TTL=47
Reply from 198.173.5.35: bytes=32 time=385ms TTL=47
Reply from 198.173.5.35: bytes=32 time=439ms TTL=47
Reply from 198.173.5.35: bytes=32 time=357ms TTL=47
Reply from 198.173.5.35: bytes=32 time=380ms TTL=47
Reply from 198.173.5.35: bytes=32 time=378ms TTL=47
Reply from 198.173.5.35: bytes=32 time=381ms TTL=47
Reply from 198.173.5.35: bytes=32 time=379ms TTL=47
Reply from 198.173.5.35: bytes=32 time=366ms TTL=47
Reply from 198.173.5.35: bytes=32 time=370ms TTL=47
Reply from 198.173.5.35: bytes=32 time=389ms TTL=47
Reply from 198.173.5.35: bytes=32 time=387ms TTL=47
Reply from 198.173.5.35: bytes=32 time=375ms TTL=47
Reply from 198.173.5.35: bytes=32 time=378ms TTL=47
Reply from 198.173.5.35: bytes=32 time=375ms TTL=47
Reply from 198.173.5.35: bytes=32 time=373ms TTL=47
Reply from 198.173.5.35: bytes=32 time=377ms TTL=47
Reply from 198.173.5.35: bytes=32 time=389ms TTL=47
Reply from 198.173.5.35: bytes=32 time=377ms TTL=47
Reply from 198.173.5.35: bytes=32 time=375ms TTL=47
Reply from 198.173.5.35: bytes=32 time=398ms TTL=47
Reply from 198.173.5.35: bytes=32 time=377ms TTL=47
Ping statistics for 198.173.5.35:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 357ms, Maximum = 439ms, Average = 381ms

Pinging www.l.google.com [216.239.37.104] with 32 bytes of data:
Reply from 216.239.37.104: bytes=32 time=363ms TTL=234
Reply from 216.239.37.104: bytes=32 time=317ms TTL=235
Reply from 216.239.37.104: bytes=32 time=356ms TTL=235
Reply from 216.239.37.104: bytes=32 time=315ms TTL=235
Reply from 216.239.37.104: bytes=32 time=373ms TTL=234
Reply from 216.239.37.104: bytes=32 time=340ms TTL=235
Reply from 216.239.37.104: bytes=32 time=354ms TTL=235
Reply from 216.239.37.104: bytes=32 time=348ms TTL=235
Reply from 216.239.37.104: bytes=32 time=348ms TTL=235
Reply from 216.239.37.104: bytes=32 time=341ms TTL=234
Reply from 216.239.37.104: bytes=32 time=350ms TTL=234
Reply from 216.239.37.104: bytes=32 time=369ms TTL=234
Reply from 216.239.37.104: bytes=32 time=353ms TTL=234
Reply from 216.239.37.104: bytes=32 time=367ms TTL=234
Reply from 216.239.37.104: bytes=32 time=352ms TTL=234
Reply from 216.239.37.104: bytes=32 time=355ms TTL=235
Reply from 216.239.37.104: bytes=32 time=369ms TTL=235
Reply from 216.239.37.104: bytes=32 time=368ms TTL=235
Reply from 216.239.37.104: bytes=32 time=352ms TTL=235
Reply from 216.239.37.104: bytes=32 time=351ms TTL=235
Reply from 216.239.37.104: bytes=32 time=390ms TTL=235
Reply from 216.239.37.104: bytes=32 time=373ms TTL=235
Reply from 216.239.37.104: bytes=32 time=382ms TTL=235
Ping statistics for 216.239.37.104:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 315ms, Maximum = 390ms, Average = 355ms

Mine still sucks. :/

Well JHB and Cape Town arent really related unless its international.

Michael, I see your pings are about the same as mine, it makes a nice improvement for international, down from 500+. But local is a bit higher than usual but at least it stays stable without (m)any timeouts

Hi EHV,

You are right local is not in the 60's anymore, think they are rerouting local, however international is going via Mauritius, so therefore we don't have the international Saix issues and the good pings...

Edit: "In terms of Mauritius' international connectivity, Telecom Plus has a 2 Mbps outgoing satellite link to France and an outgoing link of the same capacity to the USA. The inbound link has a capacity of 10 Mbps. Telecom Plus also has dedicated Internet links with Madagascar and Rodrigues (island district of Mauritius). Massive bandwidth is available with the SAFE cable (linking South Africa to Malaysia via Mauritius)"

I think its a fair trade-off, the international was quite neccesary.

Its Cape Town local that is affected the most though, our pings to say iburst.co.za or saix.net will still be in roughly the same range as myadsl.co.za now. Actually my pings are better to those JHB IP's. I guess we are going through JHB then.

@ who.is.michael

Thanks for the results, much appreciated

So it seems international even beats SAIX unshaped. At least comes close!

Disappointed about local though but why would they be doing that I wonder?? You say it used to be in the 60's, dam that would have been ok

See we have an i-burst station right close to us so maybe its worth a look :/

Jonny Two Shoes said:

Disappointed about local though but why would they be doing that I wonder?? You say it used to be in the 60's, dam that would have been ok

See we have an i-burst station right close to us so maybe its worth a look :/

Click to expand...

That local was only for Cape Town servers for us in Cape Town where we got 60ms pings. In JHB you get around 60ms to the local servers around there. The local pings to JHB didn't change, so basically it was just MyADSL, no big loss.

Pinging 196.40.97.12 with 32 bytes of data:

Reply from 196.40.97.12: bytes=32 time=65ms TTL=247
Reply from 196.40.97.12: bytes=32 time=59ms TTL=247
Reply from 196.40.97.12: bytes=32 time=57ms TTL=247
Reply from 196.40.97.12: bytes=32 time=66ms TTL=247
Reply from 196.40.97.12: bytes=32 time=70ms TTL=247
Reply from 196.40.97.12: bytes=32 time=59ms TTL=247
Reply from 196.40.97.12: bytes=32 time=63ms TTL=247
Reply from 196.40.97.12: bytes=32 time=57ms TTL=247
Reply from 196.40.97.12: bytes=32 time=61ms TTL=247
Reply from 196.40.97.12: bytes=32 time=60ms TTL=247
Reply from 196.40.97.12: bytes=32 time=58ms TTL=247
Reply from 196.40.97.12: bytes=32 time=57ms TTL=247
Reply from 196.40.97.12: bytes=32 time=66ms TTL=247
Reply from 196.40.97.12: bytes=32 time=65ms TTL=247

Ping statistics for 196.40.97.12:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 70ms, Average = 61ms

Ja, its gone back now, so our international is back to 500ms

I prefer it the other way...