Hi MrBEEP I emailed support about an hour ago requesting a new account haven't gotten back to me yet, DSLheaven is very good overall just recently more towards the gaming has been impossible due to latency not sure why.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I've been moved over from DSLHeaven to IS Gold now. So far it's working great, but still not as good as DSLHeaven used to be for me. Just loved having 170ms ping to UK/EU, since I do a lot of overseas gaming, etc. Hopefully in a few weeks DSLHeaven will be back to normal though.
Was also moved to IS. On the first day it was brilliant. Now, daytime local and int. browsing is dog slow for me. Same issues I had with IS before. Gold is losing its shine.
Yesterday IS was fine.
Today.... http://www.speedtest.net/result/1791003810.png
Okay, so my speeds hit normal 4 minutes ago (from 30KBps on FTP to 105KBps)
I took that screenshot at 17h02.
Netlimiter drew a lovely graph for me: http://dl.dropbox.com/u/21762292/shaping.png
Good old IS at it's best. Couldn't stand the shaping they applied during office hours![]()
Yeah, will probably switch backbones again in the morning. Any feedback on DSL heaven, BCS, Altech?
DSL-H is running very good on my side, currently busy with a HTTP download, maxing my line as I type this![]()
Any packet loss? That was my main issue with DSL-h. Massive packet loss after midnight. Made skyping to the GF and gaming near impossible.
Any packet loss? That was my main issue with DSL-h. Massive packet loss after midnight. Made skyping to the GF and gaming near impossible.
Got none of those issues. Gaming is awesome my international ping is great and local actually.
IS ADSL Local Speed Test to Internet Solutions New York Data Centre
Download Speed: 33 KBytes/s
Line Speed: 264 kbits/s
Anyone else experiencing problems on the VB network?
International gaming is a no go with latency at 5 times what it usually was. Downloading for Downstorm and even program updates run at half speed.
Pinging yahoo.com [98.139.183.24] with 32 bytes of data:
Reply from 98.139.183.24: bytes=32 time=1001ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1045ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1027ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1110ms TTL=47
Reply from 98.139.183.24: bytes=32 time=623ms TTL=47
Reply from 98.139.183.24: bytes=32 time=294ms TTL=47
Reply from 98.139.183.24: bytes=32 time=383ms TTL=47
Reply from 98.139.183.24: bytes=32 time=342ms TTL=47
Reply from 98.139.183.24: bytes=32 time=498ms TTL=47
Reply from 98.139.183.24: bytes=32 time=602ms TTL=47
Reply from 98.139.183.24: bytes=32 time=631ms TTL=47
Reply from 98.139.183.24: bytes=32 time=731ms TTL=47
Reply from 98.139.183.24: bytes=32 time=748ms TTL=47
Reply from 98.139.183.24: bytes=32 time=783ms TTL=47
Reply from 98.139.183.24: bytes=32 time=908ms TTL=47
Reply from 98.139.183.24: bytes=32 time=975ms TTL=47
Reply from 98.139.183.24: bytes=32 time=920ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1012ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1108ms TTL=47
Reply from 98.139.183.24: bytes=32 time=1144ms TTL=47
Ping statistics for 98.139.183.24:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 294ms, Maximum = 1144ms, Average = 794ms