Bitco Consumer Speed Test Results

[disiza]

 

[roughiain]

Nice

 

[JV_011_]

Nice !!!

Are you running any of the XBMC streams. If yes, hows the experience?

 

[BitCo]

Hi Guys,

Some interesting info on the net Index for Johannesburg

http://www.netindex.com/download/4,4355/Johannesburg/?tab=1

Mike

 

[disiza]

Nice !!!

Are you running any of the XBMC streams. If yes, hows the experience?

No XBMC Streams as yet, i've currently got my region set for SA, but as soon as i have feedback i will forward.

I have tried VIDI works like a charm...flawless.

Games : - Destiny Flawless
Farcry 4 Flawless
Battlefield 4 Flawless

Downloads:- Updates - Fast and Stable
Torrents/p2p - Fast and Stable

So far the experience has been impeccable...............................TBC

 

[disiza]

Hi Guys,

Some interesting info on the net Index for Johannesburg

http://www.netindex.com/download/4,4355/Johannesburg/?tab=1

Mike

 

[disiza]

Feed Back - Performance

http://www.speedtest.net/results.php?sh=e0b322c3e84c44be805600bea36b2741&ria=0

The heart attack before the flat line is Telkom and MTN/Afrihost.......... the flat line is BITCO, stable and consistent, the one drop spike is a speedtest to Seattle, Washington, Redmond.

Pretty impressive.....still early days!

 

[disiza]

Comparison -- ADSL 10 mb/s vs Bitco 10 mb/s

Telkom 10 MB/s ADSL Line


ping -n 250 www.msn.com

Pinging [204.79.197.203] with 32 bytes of data:
Reply from 204.79.197.203: bytes=32 time=185ms TTL=109
Reply from 204.79.197.203: bytes=32 time=257ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=205ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=413ms TTL=109
Reply from 204.79.197.203: bytes=32 time=189ms TTL=109
Reply from 204.79.197.203: bytes=32 time=193ms TTL=109
Reply from 204.79.197.203: bytes=32 time=203ms TTL=109
Reply from 204.79.197.203: bytes=32 time=189ms TTL=109
Reply from 204.79.197.203: bytes=32 time=333ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=376ms TTL=109
Reply from 204.79.197.203: bytes=32 time=412ms TTL=109
Reply from 204.79.197.203: bytes=32 time=287ms TTL=109
Reply from 204.79.197.203: bytes=32 time=403ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=587ms TTL=109
Reply from 204.79.197.203: bytes=32 time=469ms TTL=109
Reply from 204.79.197.203: bytes=32 time=502ms TTL=109
Reply from 204.79.197.203: bytes=32 time=242ms TTL=109
Reply from 204.79.197.203: bytes=32 time=282ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=311ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=397ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=433ms TTL=109
Reply from 204.79.197.203: bytes=32 time=342ms TTL=109
Reply from 204.79.197.203: bytes=32 time=283ms TTL=109
Reply from 204.79.197.203: bytes=32 time=587ms TTL=109
Reply from 204.79.197.203: bytes=32 time=418ms TTL=109
Reply from 204.79.197.203: bytes=32 time=456ms TTL=109
Reply from 204.79.197.203: bytes=32 time=256ms TTL=109
Reply from 204.79.197.203: bytes=32 time=342ms TTL=109
Reply from 204.79.197.203: bytes=32 time=206ms TTL=109
Reply from 204.79.197.203: bytes=32 time=237ms TTL=109
Reply from 204.79.197.203: bytes=32 time=328ms TTL=109
Reply from 204.79.197.203: bytes=32 time=185ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=187ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=290ms TTL=109
Reply from 204.79.197.203: bytes=32 time=269ms TTL=109
Reply from 204.79.197.203: bytes=32 time=422ms TTL=109
Reply from 204.79.197.203: bytes=32 time=444ms TTL=109
Reply from 204.79.197.203: bytes=32 time=388ms TTL=109
Reply from 204.79.197.203: bytes=32 time=569ms TTL=109
Reply from 204.79.197.203: bytes=32 time=319ms TTL=109
Reply from 204.79.197.203: bytes=32 time=453ms TTL=109
Reply from 204.79.197.203: bytes=32 time=326ms TTL=109
Reply from 204.79.197.203: bytes=32 time=363ms TTL=109
Reply from 204.79.197.203: bytes=32 time=348ms TTL=109
Reply from 204.79.197.203: bytes=32 time=223ms TTL=109
Reply from 204.79.197.203: bytes=32 time=222ms TTL=109
Reply from 204.79.197.203: bytes=32 time=379ms TTL=109
Reply from 204.79.197.203: bytes=32 time=240ms TTL=109
Reply from 204.79.197.203: bytes=32 time=189ms TTL=109
Reply from 204.79.197.203: bytes=32 time=222ms TTL=109
Reply from 204.79.197.203: bytes=32 time=218ms TTL=109
Reply from 204.79.197.203: bytes=32 time=276ms TTL=109
Reply from 204.79.197.203: bytes=32 time=287ms TTL=109
Reply from 204.79.197.203: bytes=32 time=193ms TTL=109
Reply from 204.79.197.203: bytes=32 time=306ms TTL=109
Reply from 204.79.197.203: bytes=32 time=284ms TTL=109
Reply from 204.79.197.203: bytes=32 time=406ms TTL=109
Reply from 204.79.197.203: bytes=32 time=188ms TTL=109
Reply from 204.79.197.203: bytes=32 time=187ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=317ms TTL=109
Reply from 204.79.197.203: bytes=32 time=194ms TTL=109
Reply from 204.79.197.203: bytes=32 time=234ms TTL=109
Reply from 204.79.197.203: bytes=32 time=299ms TTL=109
Reply from 204.79.197.203: bytes=32 time=317ms TTL=109
Reply from 204.79.197.203: bytes=32 time=443ms TTL=109
Reply from 204.79.197.203: bytes=32 time=407ms TTL=109
Reply from 204.79.197.203: bytes=32 time=312ms TTL=109
Reply from 204.79.197.203: bytes=32 time=544ms TTL=109
Reply from 204.79.197.203: bytes=32 time=374ms TTL=109
Reply from 204.79.197.203: bytes=32 time=319ms TTL=109
Reply from 204.79.197.203: bytes=32 time=189ms TTL=109
Reply from 204.79.197.203: bytes=32 time=187ms TTL=109
Reply from 204.79.197.203: bytes=32 time=186ms TTL=109
Reply from 204.79.197.203: bytes=32 time=281ms TTL=109
Reply from 204.79.197.203: bytes=32 time=218ms TTL=109
Reply from 204.79.197.203: bytes=32 time=515ms TTL=109






Ping statistics for 204.79.197.203:
Packets: Sent = 250, Received = 250, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 642ms, Average = 301ms



BITCO 10MB/s



ping -n 250 www.msn.com

Pinging [204.79.197.203] with 32 bytes of data:
Reply from 204.79.197.203: bytes=32 time=6ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=8ms TTL=122
Reply from 204.79.197.203: bytes=32 time=6ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=7ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=6ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=6ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=6ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=6ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=4ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=6ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122
Reply from 204.79.197.203: bytes=32 time=5ms TTL=122




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


Am i missing something here such a huge difference

 

[disiza]

Update-


http://www.speedtest.net/results.php?sh=e0b322c3e84c44be805600bea36b2741&ria=0

 

[disiza]

Update:-

http://www.speedtest.net/results.php?sh=e0b322c3e84c44be805600bea36b2741&ria=0

Take note of the cool, calm and collected heartbeat!!!!

Disregard the best up and down results got that when i was using Telkom LTE a few months back.

 

[BitCo]

Update:-

http://www.speedtest.net/results.php?sh=e0b322c3e84c44be805600bea36b2741&ria=0

Take note of the cool, calm and collected heartbeat!!!!

Disregard the best up and down results got that when i was using Telkom LTE a few months back.

Hi Disiza,

Glad to see you enjoying your connection

Mike

 

[CriticalConsumer]

Hi Mike, my connection seems to be throttled to around 1.2 - 1.4Mbps...This is rather strange that is so restrained after business hours
http://www.speedtest.net/my-result/4295069954

Something seriously wrong here. I have no downloads running, no streaming - my attempts at watching YouTube is painful.

Please assist - I will call the help desk tomorrow but they are not going to be able to test after hours.

 

[koeksGHT]

 

[disiza]

View attachment 208364

This is what i like to see from a ISP .....consistency

http://www.speedtest.net/my-result/4293574319

http://www.speedtest.net/my-result/4177543106

http://www.speedtest.net/my-result/4230009045

 

[BitCo]

Hi Mike, my connection seems to be throttled to around 1.2 - 1.4Mbps...This is rather strange that is so restrained after business hours
http://www.speedtest.net/my-result/4295069954

Something seriously wrong here. I have no downloads running, no streaming - my attempts at watching YouTube is painful.

Please assist - I will call the help desk tomorrow but they are not going to be able to test after hours.

Hi Critical Consumer,

hope you have been well?

i see a fault on your line from around 7pm last night. seems to be stable this morning so either support team made some changes or not currently happening.

Can you log with [email protected] and see what they say

Send us a PM later when you are online if it happens again

Mike

 

[CriticalConsumer]

Hi Critical Consumer,

hope you have been well?

i see a fault on your line from around 7pm last night. seems to be stable this morning so either support team made some changes or not currently happening.

Can you log with [email protected] and see what they say

Send us a PM later when you are online if it happens again

Mike

Hi Mike,

Thanks for the response. I have been well but busy. I have just logged the ticket due to power outages in our area for around 12 hours...
I have copied and pasted the posts and emailed it to the support team. Am awaiting their response. Things seem to be ok for now...not sure how it will be later.

Thanks!
Ash

 

[CriticalConsumer]

Ok so ticket is logged: #SP00121293
Link seems better but will check later tonight.

 

[CriticalConsumer]

And here are my results from a later test from tonight (apart from the one I already sent in my PM to you Mike). Something definitely wrong!



I suspect the fault to be one of the following:
1. Temperature related and connector impacting on the RF side (expansion / contraction with the change in weather).
2. Moisture forming in a weathered joint due to rubber tape not insulating properly.
3. Interference due to a newish Wirulink 2 doors down from me.

I would recommend putting a trace on this to monitor over a 48 hour period...I would appreciate a visit by a techie during the day to check it out - as you know I am not far off from your offices.

Thanks!

 

[BitCo]

And here are my results from a later test from tonight (apart from the one I already sent in my PM to you Mike). Something definitely wrong!



I suspect the fault to be one of the following:
1. Temperature related and connector impacting on the RF side (expansion / contraction with the change in weather).
2. Moisture forming in a weathered joint due to rubber tape not insulating properly.
3. Interference due to a newish Wirulink 2 doors down from me.

I would recommend putting a trace on this to monitor over a 48 hour period...I would appreciate a visit by a techie during the day to check it out - as you know I am not far off from your offices.

Thanks!

Hi CriticalConsumer,

Thanks for the post, i suspect this could be interference related as something close to you starts to broadcast in the evenings

If you can please log with [email protected] so someone senior can investigate then keep me posted via PM if you haven't got it resolved.

Very weird fault indeed, i am confident our team will resolve it for you

Mike

 

[CriticalConsumer]

Hi CriticalConsumer,

Thanks for the post, i suspect this could be interference related as something close to you starts to broadcast in the evenings

If you can please log with [email protected] so someone senior can investigate then keep me posted via PM if you haven't got it resolved.

Very weird fault indeed, i am confident our team will resolve it for you

Mike

A ticket was logged...no feedback yet.

Another speed test...
http://www.speedtest.net/result/4304367773.png

and it seems as if there is interference in the form of someone using the same frequency.. Might be time to -re-optimise / replan this link.