Gaming with IS

I

Icaris

New Member
Joined
Dec 1, 2005
Messages
6
Reaction score
0
I am looking into getting an IS account through openweb to use for local gaming (after the cap). Can anyone give me an idea on what pings and how well it works for local gaming? Is it playable?

Thanks :D
 
Hey,
I play on mweb Kalahari usualy. On my SAIX account I ping 60ms. On my IS account I ping 40ms. I live in CT. Your area tends to affect your ping by 20ms or so.
 
Now [14H51 Monday from an IS provided 1024 line using their 5 ip fixed address routing solution]:

C:\>ping saix.co.za

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

Reply from 196.25.1.200: bytes=32 time=164ms TTL=245
Reply from 196.25.1.200: bytes=32 time=154ms TTL=245
Reply from 196.25.1.200: bytes=32 time=155ms TTL=245
Reply from 196.25.1.200: bytes=32 time=163ms TTL=245

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 154ms, Maximum = 164ms, Average = 159ms

Unfortunately, none of the game servers respong to pings ...
Is there something you want me to ping ?

Obviously - this is not IS's gaming server but an indication of what SAIX's SGS servers will be responding like.
 
I'm not at home atm but this evening i'll run some stats on my IS and my SAIX accounts and post them. All I can say is that on mweb's gaming servers IS is better for me by about 20ms
 
ok I get about 30 ping in Johannesburg with my current SAIX account. I wouldn't mind an increase of 20 ping but I just want to know if it doesn't lag, no only ping but response wise (some connections "jerk").
 
Has anyone had experience with openweb in particular? Do you know how many concurrent sessions are available?

What alternative company has seemed good for you? (IS 2gb with 30gb local at between R160 and R180)

Thanks :D
 
I am using a OpenWeb 2GB IS account. It goes for R163. I havent tried concurent loggins unfortunately. The only other providers of IS accounts I know of is nukecap and imagine.
 
I play CSS and Quake 4. What is the servic elike on openweb? I only play on SGS servers.
 
I am not sure I'll havto do some pings this evening; I play on mweb's servers only so I cannot comment on saix connectivity.
 
Here is my results on bother accounts:
========================================================
IS
========================================================
C:\>ping saix.co.za

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

Reply from 196.25.1.200: bytes=32 time=61ms TTL=242
Reply from 196.25.1.200: bytes=32 time=63ms TTL=242
Reply from 196.25.1.200: bytes=32 time=61ms TTL=242
Reply from 196.25.1.200: bytes=32 time=66ms TTL=242

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

C:\>ping kalahari.mweb.co.za

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

Reply from 196.2.33.21: bytes=32 time=39ms TTL=118
Reply from 196.2.33.21: bytes=32 time=42ms TTL=118
Reply from 196.2.33.21: bytes=32 time=44ms TTL=118
Reply from 196.2.33.21: bytes=32 time=47ms TTL=118

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

C:\>ping karoo.mweb.co.za

Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=65ms TTL=116
Reply from 196.2.128.100: bytes=32 time=67ms TTL=116
Reply from 196.2.128.100: bytes=32 time=65ms TTL=116
Reply from 196.2.128.100: bytes=32 time=69ms TTL=116

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

========================================================
SAIX
========================================================
C:\>ping saix.co.za

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

Reply from 196.25.1.200: bytes=32 time=15ms TTL=250
Reply from 196.25.1.200: bytes=32 time=14ms TTL=250
Reply from 196.25.1.200: bytes=32 time=15ms TTL=250
Reply from 196.25.1.200: bytes=32 time=14ms TTL=250

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

C:\>ping kalahari.mweb.co.za

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

Reply from 196.2.33.21: bytes=32 time=39ms TTL=119
Reply from 196.2.33.21: bytes=32 time=40ms TTL=119
Reply from 196.2.33.21: bytes=32 time=40ms TTL=119
Reply from 196.2.33.21: bytes=32 time=38ms TTL=119

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

C:\>ping karoo.mweb.co.za

Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=67ms TTL=117
Reply from 196.2.128.100: bytes=32 time=68ms TTL=117
Reply from 196.2.128.100: bytes=32 time=66ms TTL=117
Reply from 196.2.128.100: bytes=32 time=65ms TTL=117

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

As you can see IS seems just as good too mweb; but it seems its slower too saix.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X