plenty
Well-Known Member
We have the 5up : 5down down option at work, and during the day we about 6.8 down, and about 4.8 up
It's managed during the day from a speed point of view, it seems it does not get managed after hours... as the following will show you.
National does seem to have a limitation, but within your metro... these speeds are obtainable all day...
I get 2-3ms traces to CINX -- And quite frankly have been totally blown away by the service thus far.
We are going to be moving up to 10up : 10down soon for the extra headroom it will give us during business hours.
Ubuntu Torrents
>>>> Utorrent Test - 7pm Friday <<<<
Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:
Reply from 84.234.17.86: bytes=32 time=153ms TTL=110
Reply from 84.234.17.86: bytes=32 time=153ms TTL=110
Reply from 84.234.17.86: bytes=32 time=153ms TTL=110
Reply from 84.234.17.86: bytes=32 time=156ms TTL=110
Ping statistics for 84.234.17.86:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 156ms, Average = 153ms
Pinging is.cinx.net.za [198.32.214.10] with 32 bytes of data:
Reply from 198.32.214.10: bytes=32 time=3ms TTL=249
Reply from 198.32.214.10: bytes=32 time=3ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Ping statistics for 198.32.214.10:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
Pinging ntp2.is.co.za [196.26.5.10] with 32 bytes of data:
Reply from 196.26.5.10: bytes=32 time=2ms TTL=56
Reply from 196.26.5.10: bytes=32 time=3ms TTL=56
Reply from 196.26.5.10: bytes=32 time=3ms TTL=56
Reply from 196.26.5.10: bytes=32 time=2ms TTL=56
Ping statistics for 196.26.5.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
Pinging ntp.is.co.za [196.4.160.4] with 32 bytes of data:
Reply from 196.4.160.4: bytes=32 time=29ms TTL=55
Reply from 196.4.160.4: bytes=32 time=29ms TTL=55
Reply from 196.4.160.4: bytes=32 time=29ms TTL=55
Reply from 196.4.160.4: bytes=32 time=28ms TTL=55
Ping statistics for 196.4.160.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 29ms, Average = 28ms
Pinging ns1.theplanet.com [207.218.247.135] with 32 bytes of data:
Reply from 207.218.247.135: bytes=32 time=259ms TTL=235
Reply from 207.218.247.135: bytes=32 time=259ms TTL=235
Reply from 207.218.247.135: bytes=32 time=258ms TTL=235
Reply from 207.218.247.135: bytes=32 time=259ms TTL=235
Ping statistics for 207.218.247.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 258ms, Maximum = 259ms, Average = 258ms
Pinging ns1.level3.net [209.244.0.1] with 32 bytes of data:
Reply from 209.244.0.1: bytes=32 time=223ms TTL=47
Reply from 209.244.0.1: bytes=32 time=223ms TTL=47
Reply from 209.244.0.1: bytes=32 time=223ms TTL=47
Reply from 209.244.0.1: bytes=32 time=223ms TTL=47
Ping statistics for 209.244.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 223ms, Average = 223ms
But if there are any doubters as to what is possible over a 5up : 5down line, this posting will hopefully be the final say on that matter!
I'd be happy to answer further questions regarding the service, service installation or any other info
Cape Town tests



JHB tests



DBN tests

It's managed during the day from a speed point of view, it seems it does not get managed after hours... as the following will show you.
National does seem to have a limitation, but within your metro... these speeds are obtainable all day...
I get 2-3ms traces to CINX -- And quite frankly have been totally blown away by the service thus far.
We are going to be moving up to 10up : 10down soon for the extra headroom it will give us during business hours.
Ubuntu Torrents
>>>> Utorrent Test - 7pm Friday <<<<
Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:
Reply from 84.234.17.86: bytes=32 time=153ms TTL=110
Reply from 84.234.17.86: bytes=32 time=153ms TTL=110
Reply from 84.234.17.86: bytes=32 time=153ms TTL=110
Reply from 84.234.17.86: bytes=32 time=156ms TTL=110
Ping statistics for 84.234.17.86:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 156ms, Average = 153ms
Pinging is.cinx.net.za [198.32.214.10] with 32 bytes of data:
Reply from 198.32.214.10: bytes=32 time=3ms TTL=249
Reply from 198.32.214.10: bytes=32 time=3ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Reply from 198.32.214.10: bytes=32 time=2ms TTL=249
Ping statistics for 198.32.214.10:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
Pinging ntp2.is.co.za [196.26.5.10] with 32 bytes of data:
Reply from 196.26.5.10: bytes=32 time=2ms TTL=56
Reply from 196.26.5.10: bytes=32 time=3ms TTL=56
Reply from 196.26.5.10: bytes=32 time=3ms TTL=56
Reply from 196.26.5.10: bytes=32 time=2ms TTL=56
Ping statistics for 196.26.5.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
Pinging ntp.is.co.za [196.4.160.4] with 32 bytes of data:
Reply from 196.4.160.4: bytes=32 time=29ms TTL=55
Reply from 196.4.160.4: bytes=32 time=29ms TTL=55
Reply from 196.4.160.4: bytes=32 time=29ms TTL=55
Reply from 196.4.160.4: bytes=32 time=28ms TTL=55
Ping statistics for 196.4.160.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 29ms, Average = 28ms
Pinging ns1.theplanet.com [207.218.247.135] with 32 bytes of data:
Reply from 207.218.247.135: bytes=32 time=259ms TTL=235
Reply from 207.218.247.135: bytes=32 time=259ms TTL=235
Reply from 207.218.247.135: bytes=32 time=258ms TTL=235
Reply from 207.218.247.135: bytes=32 time=259ms TTL=235
Ping statistics for 207.218.247.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 258ms, Maximum = 259ms, Average = 258ms
Pinging ns1.level3.net [209.244.0.1] with 32 bytes of data:
Reply from 209.244.0.1: bytes=32 time=223ms TTL=47
Reply from 209.244.0.1: bytes=32 time=223ms TTL=47
Reply from 209.244.0.1: bytes=32 time=223ms TTL=47
Reply from 209.244.0.1: bytes=32 time=223ms TTL=47
Ping statistics for 209.244.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 223ms, Average = 223ms
But if there are any doubters as to what is possible over a 5up : 5down line, this posting will hopefully be the final say on that matter!
I'd be happy to answer further questions regarding the service, service installation or any other info
Cape Town tests



JHB tests



DBN tests




