OpenWeb Survey - 10GB - R349

That sounds great ... I will most likely be taking an account with you if they are available ... I really like the separation of local and international :)
I was a bit concerned with the ping response time from google.co.za of all places ... that should have been the quickest ... i usually use that as my benchmark :)
I am not a hard and fast gamer .. so not sure if the saix.net is good or even the right one to test ...
Please guys, provide me with things you would like me to test so that I can conduct a thorough test and everyone can make sure it will work for them.
Thanx again MrBeep.
 
Howzit.

Thanks for the trial run. I do not have all these fancy ping stats and what not but i can tell u that i was generally very happy with the service. The international was a bit difficult to judge due to IS int being intermittently down for most of yesterday...

The idea of being able to split local and international is great though and has been a long time coming....

As long as the international speeds are up to scratch, i could be very interested in getting an account with u guys :-)

l8rs
 
hj2k_x said:
Howzit.

The international was a bit difficult to judge due to IS int being intermittently down for most of yesterday...
Click to expand...
So that is why my international speeds were so low and intermittant.

Thanks for the test account MrBEEB. Local was fine running at 20-22 kB/s, Int was running at 7-9 kB/s and later a little faster. On my normal saix account the graph on DUmeter is smooth. With the international test account it jumps up and down like crazy. Don't know if this is normal but it irritated the bejezuz out of me.

MrBEEB, would this be normal download speed for int.?

Cheerz
Voodoo
 
Hey Voodoo,

Not, not at all. We are currently changing our International portion.

I will re-activate all accounts as soon as this is done. I would appreciate it if you could test again.

Kind regards
MrBEEP
 
Thanks MrBEEP

Just send a email or pm when you re-activate. Will gladly retest again.

Cheerz
Voodoo

EDIT: Just one more question: (Have not tested myself) Would the vpn work for 2 pc's connected to a router? i.o.w could both dial into the vpn?
 
Last edited:
mrbeep could i get a test account

because if int and gaming works i would sign and i chat alot on the bf 2 forums
and there are plenty ppl on 10 gig saol that arent happy about 499

so if i could see it was good you could get a bit of business :)

well let me know :)
 
I need normally working internet connection without protocol restrictions whatsoever. I am running a lot of services on my machine, so having external IP is required. I am also not prepared to have to do special setup for any of the programs I use (like proxies and other garbage). I am using linux, so I won't consider anything that requires special software to dial in.

I think in year 2006 one should not need to do tricks and hacks in order to get connected. Rather burn down telkom!
 
Who gives you the right to call proxies garbage?

"(like proxies and other garbage)."
 
Another question - are there any resets every 24 hours ? or is this VPN account on once you "Dial in" ? and can i run my FTP service on this with a fixed IP addy ?
 
Yesh, let us know about resets etc. The package sounds great at the moment though. It caters for what I'm looking for (fast, highish volume local access) and international
 
I was finally able to test the VPN account as well ... here are the results, please let me know if you would like anything specifically tested :

Gamco
Local only
20.19 KB/sec

VPN
17.24 KB/sec

Telkom

Local only
Download Speed Test

Your line speed is approximately 155.7 Kbps or 19.1 kBytes/sec
( Where kb = kilobits and kB = kiloBytes )
Results:
Below is the data used to calculate your download speed:
• Download time: 26.203 seconds
• Size of file: 500 KiloBytes
• Estimated line speed: 155.7 (kilobits/second)
• Estimated line speed: 19.1 (kiloBytes/second)

VPN
Download Speed Test
Telkom ADSL Speed Test Meter
Your line speed is approximately 146 Kbps or 17.9 kBytes/sec
( Where kb = kilobits and kB = kiloBytes )
Results:
Below is the data used to calculate your download speed:
• Download time: 27.953 seconds
• Size of file: 500 KiloBytes
• Estimated line speed: 146 (kilobits/second)
• Estimated line speed: 17.9 (kiloBytes/second)

Broadband Reports.com
Seattle server
dslreports.com speed test result on 2006-02-18 13:58:52 EST:
144 / 145
Your download speed : 144 kbps or 18.1 KB/sec.

Your upload speed : 145 kbps or 18.1 KB/sec.


Standford University
running 10s outbound test (client to server) . . . . . 114.21Kb/s
running 10s inbound test (server to client) . . . . . . 128.43kb/s

Pings
Local only
Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=70ms TTL=240
Reply from 196.25.1.200: bytes=32 time=66ms TTL=240
Reply from 196.25.1.200: bytes=32 time=69ms TTL=240
Reply from 196.25.1.200: bytes=32 time=65ms TTL=240
Reply from 196.25.1.200: bytes=32 time=62ms TTL=240
Reply from 196.25.1.200: bytes=32 time=63ms TTL=240
Reply from 196.25.1.200: bytes=32 time=63ms TTL=240
Reply from 196.25.1.200: bytes=32 time=62ms TTL=240
Reply from 196.25.1.200: bytes=32 time=63ms TTL=240
Reply from 196.25.1.200: bytes=32 time=64ms TTL=240

Ping statistics for 196.25.1.200:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 70ms, Average = 64ms

VPN

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=123ms TTL=248
Reply from 196.25.1.200: bytes=32 time=118ms TTL=248
Reply from 196.25.1.200: bytes=32 time=200ms TTL=248
Reply from 196.25.1.200: bytes=32 time=202ms TTL=248
Reply from 196.25.1.200: bytes=32 time=110ms TTL=248
Reply from 196.25.1.200: bytes=32 time=201ms TTL=248
Reply from 196.25.1.200: bytes=32 time=111ms TTL=248
Reply from 196.25.1.200: bytes=32 time=207ms TTL=248
Reply from 196.25.1.200: bytes=32 time=199ms TTL=248
Reply from 196.25.1.200: bytes=32 time=219ms TTL=248

Ping statistics for 196.25.1.200:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 219ms, Average = 169ms

Local only
Pinging www.is.co.za [196.34.149.154] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

Local only
Pinging kalahari.mweb.co.za [196.2.33.21] with 32 bytes of data:

Reply from 196.2.33.21: bytes=32 time=47ms TTL=117
Reply from 196.2.33.21: bytes=32 time=45ms TTL=117
Reply from 196.2.33.21: bytes=32 time=47ms TTL=117
Reply from 196.2.33.21: bytes=32 time=41ms TTL=117
Reply from 196.2.33.21: bytes=32 time=40ms TTL=117
Reply from 196.2.33.21: bytes=32 time=44ms TTL=117
Reply from 196.2.33.21: bytes=32 time=43ms TTL=117
Reply from 196.2.33.21: bytes=32 time=45ms TTL=117
Reply from 196.2.33.21: bytes=32 time=45ms TTL=117
Reply from 196.2.33.21: bytes=32 time=39ms TTL=117

Ping statistics for 196.2.33.21:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 47ms, Average = 43ms

Tracing route to kalahari.mweb.co.za [196.2.33.21]
over a maximum of 30 hops:

1 2248 ms <1 ms <1 ms 192.168.0.1
2 26 ms 26 ms 25 ms c1-1-1.ndn.isadsl.co.za [196.209.0.1]
3 * 254 ms 270 ms cdsl1-rba-at6-0-11-is.isdsl.net [196.38.72.249]

4 * 281 ms 279 ms curp1-rba-gi6.isdsl.net [196.38.72.238]
5 37 ms 36 ms 35 ms cdsl1-rba-gi0-1-43.isdsl.net [196.38.72.229]
6 421 ms 357 ms 373 ms 196.26.96.203
7 406 ms 361 ms 426 ms core1a-rba-gi2-0-0.rtr.isnet.net [196.26.0.7]
8 39 ms 39 ms 38 ms 168.209.0.134
9 40 ms 42 ms 43 ms 196.36.218.142
10 42 ms 41 ms 42 ms kalahari.mweb.co.za [196.2.33.21]

Trace complete.

VPN

Pinging kalahari.mweb.co.za [196.2.33.21] with 32 bytes of data:

Reply from 196.2.33.21: bytes=32 time=201ms TTL=117
Reply from 196.2.33.21: bytes=32 time=114ms TTL=117
Reply from 196.2.33.21: bytes=32 time=197ms TTL=117
Reply from 196.2.33.21: bytes=32 time=105ms TTL=117
Reply from 196.2.33.21: bytes=32 time=104ms TTL=117
Reply from 196.2.33.21: bytes=32 time=104ms TTL=117
Reply from 196.2.33.21: bytes=32 time=105ms TTL=117
Reply from 196.2.33.21: bytes=32 time=104ms TTL=117
Reply from 196.2.33.21: bytes=32 time=154ms TTL=117
Reply from 196.2.33.21: bytes=32 time=106ms TTL=117

Ping statistics for 196.2.33.21:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 201ms, Average = 129ms

Local only
Pinging google.co.za [216.239.39.99] with 32 bytes of data:

Reply from 216.239.39.99: bytes=32 time=1462ms TTL=237
Reply from 216.239.39.99: bytes=32 time=1099ms TTL=237
Request timed out.
Reply from 216.239.39.99: bytes=32 time=942ms TTL=237
Request timed out.
Reply from 216.239.39.99: bytes=32 time=1178ms TTL=237
Request timed out.
Request timed out.
Reply from 216.239.39.99: bytes=32 time=1148ms TTL=237
Reply from 216.239.39.99: bytes=32 time=1100ms TTL=237

Ping statistics for 216.239.39.99:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 942ms, Maximum = 1462ms, Average = 1154ms


VPN

Pinging google.co.za [216.239.39.99] with 32 bytes of data:

Reply from 216.239.39.99: bytes=32 time=546ms TTL=239
Reply from 216.239.39.99: bytes=32 time=598ms TTL=239
Reply from 216.239.39.99: bytes=32 time=445ms TTL=239
Reply from 216.239.39.99: bytes=32 time=547ms TTL=239
Reply from 216.239.39.99: bytes=32 time=446ms TTL=239
Reply from 216.239.39.99: bytes=32 time=452ms TTL=239
Reply from 216.239.39.99: bytes=32 time=537ms TTL=239
Reply from 216.239.39.99: bytes=32 time=553ms TTL=239
Reply from 216.239.39.99: bytes=32 time=455ms TTL=239
Reply from 216.239.39.99: bytes=32 time=450ms TTL=239

Ping statistics for 216.239.39.99:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 445ms, Maximum = 598ms, Average = 502ms



Tucows Saix Game server

Local Only
Pinging games.tucows.saix.net [196.25.240.137] with 32 bytes of data:

Reply from 196.25.240.137: bytes=32 time=74ms TTL=240
Reply from 196.25.240.137: bytes=32 time=64ms TTL=240
Reply from 196.25.240.137: bytes=32 time=155ms TTL=240
Reply from 196.25.240.137: bytes=32 time=65ms TTL=240
Reply from 196.25.240.137: bytes=32 time=155ms TTL=240
Reply from 196.25.240.137: bytes=32 time=152ms TTL=240
Reply from 196.25.240.137: bytes=32 time=155ms TTL=240
Reply from 196.25.240.137: bytes=32 time=155ms TTL=240
Reply from 196.25.240.137: bytes=32 time=154ms TTL=240
Reply from 196.25.240.137: bytes=32 time=68ms TTL=240

Ping statistics for 196.25.240.137:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 155ms, Average = 119ms

VPN
Pinging games.tucows.saix.net [196.25.240.137] with 32 bytes of data:

Reply from 196.25.240.137: bytes=32 time=123ms TTL=248
Reply from 196.25.240.137: bytes=32 time=202ms TTL=248
Reply from 196.25.240.137: bytes=32 time=204ms TTL=248
Reply from 196.25.240.137: bytes=32 time=201ms TTL=248
Reply from 196.25.240.137: bytes=32 time=200ms TTL=248
Reply from 196.25.240.137: bytes=32 time=222ms TTL=248
Reply from 196.25.240.137: bytes=32 time=201ms TTL=248
Reply from 196.25.240.137: bytes=32 time=111ms TTL=248
Reply from 196.25.240.137: bytes=32 time=201ms TTL=248
Reply from 196.25.240.137: bytes=32 time=114ms TTL=248

Ping statistics for 196.25.240.137:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 222ms, Average = 177ms

Saix Game Server
Local only

Pinging games.saix.net [196.4.79.14] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 196.4.79.14:
Packets: Sent = 10, Received = 0, Lost = 10 (100% loss),
VPN
Pinging games.saix.net [196.4.79.14] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 196.4.79.14:
Packets: Sent = 10, Received = 0, Lost = 10 (100% loss),
 
It seems really good for local browsing/downloading(even with the VPN account) ... however international was not consistent for P2P and sometimes browsing as well(could just be me or the particular stuff I was getting).
I am also not sure about whether the latencies are good enough for gaming(one of the gamers will have to help me out here), as I think you need a latency of below 100 for decent gaming, but you will notice that games.saix does not seem to work, but the tucows.saix game server provides much higher latencies than "I think" which is minimal for gaming(please correct me if I am wrong).
Overall it is great for browsing,downloading,P2P,etc. ... with the added bonus(my fav) that you can separate your international from local ... so basically you have 20GB local and 10GB international.
 
Last edited:
well - it definately sounds worth it to sign up for the price - Win some, Loose some. We do live in the Country called Telkom!
 
I definitely think it is the best option available at the moment, so I will be taking one starting 1 March :D
 
Hey Guys,

Thank you SO much for your extensive testing.

We were planning to launch on 1 March, however, our international link is not strong enough yet to hold a commercial service.

However, we will be officially launching this service in 1 April 2006. We will be taking a limited amount of orders from middle March, as this account will be very limited. We will NOT oversell.

I once again would like to thank everyone for the marvelous contribution.

Beta testing conitnues.

Kind regards
MrBEEP
 
MrBeep, please let me/us know if we can be of any further assistance :)

Now, what to do till 1 April ... any ideas anyone?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X