BitCo Consumer Review

Quick one, do you need to pay a downgrade fee when on month to month? I'm going to be away for the next three months, don't want to cancel but if I can downgrade and save a bit of cash for those three months why not.
 
Anyone else having issues today?

Code: 
C:\Users\stryd_000>ping bitco.co.za -t

Pinging bitco.co.za [196.22.142.12] with 32 bytes of data:
Reply from 196.22.142.12: bytes=32 time=202ms TTL=56
Reply from 196.22.142.12: bytes=32 time=179ms TTL=56
Reply from 196.22.142.12: bytes=32 time=118ms TTL=56
Reply from 196.22.142.12: bytes=32 time=212ms TTL=56
Reply from 196.22.142.12: bytes=32 time=259ms TTL=56
Reply from 196.22.142.12: bytes=32 time=327ms TTL=56
Reply from 196.22.142.12: bytes=32 time=175ms TTL=56
Reply from 196.22.142.12: bytes=32 time=151ms TTL=56
Reply from 196.22.142.12: bytes=32 time=138ms TTL=56
Reply from 196.22.142.12: bytes=32 time=85ms TTL=56
Reply from 196.22.142.12: bytes=32 time=102ms TTL=56
Reply from 196.22.142.12: bytes=32 time=191ms TTL=56
Reply from 196.22.142.12: bytes=32 time=127ms TTL=56
Reply from 196.22.142.12: bytes=32 time=195ms TTL=56
Reply from 196.22.142.12: bytes=32 time=302ms TTL=56
Reply from 196.22.142.12: bytes=32 time=169ms TTL=56
Reply from 196.22.142.12: bytes=32 time=196ms TTL=56
Reply from 196.22.142.12: bytes=32 time=194ms TTL=56
Reply from 196.22.142.12: bytes=32 time=191ms TTL=56
Reply from 196.22.142.12: bytes=32 time=199ms TTL=56
Reply from 196.22.142.12: bytes=32 time=176ms TTL=56
Reply from 196.22.142.12: bytes=32 time=163ms TTL=56
Reply from 196.22.142.12: bytes=32 time=281ms TTL=56
Reply from 196.22.142.12: bytes=32 time=337ms TTL=56
Reply from 196.22.142.12: bytes=32 time=226ms TTL=56
Reply from 196.22.142.12: bytes=32 time=215ms TTL=56
Reply from 196.22.142.12: bytes=32 time=231ms TTL=56
Reply from 196.22.142.12: bytes=32 time=2248ms TTL=56
Reply from 196.22.142.12: bytes=32 time=138ms TTL=56
Reply from 196.22.142.12: bytes=32 time=155ms TTL=56
Reply from 196.22.142.12: bytes=32 time=272ms TTL=56
Reply from 196.22.142.12: bytes=32 time=170ms TTL=56
Request timed out.
Reply from 196.22.142.12: bytes=32 time=2506ms TTL=56
Reply from 196.22.142.12: bytes=32 time=656ms TTL=56
Reply from 196.22.142.12: bytes=32 time=113ms TTL=56
Reply from 196.22.142.12: bytes=32 time=89ms TTL=56
Reply from 196.22.142.12: bytes=32 time=127ms TTL=56
Reply from 196.22.142.12: bytes=32 time=255ms TTL=56
Reply from 196.22.142.12: bytes=32 time=173ms TTL=56
Reply from 196.22.142.12: bytes=32 time=120ms TTL=56
Reply from 196.22.142.12: bytes=32 time=97ms TTL=56
Reply from 196.22.142.12: bytes=32 time=124ms TTL=56
Reply from 196.22.142.12: bytes=32 time=141ms TTL=56
Reply from 196.22.142.12: bytes=32 time=159ms TTL=56
Reply from 196.22.142.12: bytes=32 time=66ms TTL=56
Reply from 196.22.142.12: bytes=32 time=143ms TTL=56
Reply from 196.22.142.12: bytes=32 time=172ms TTL=56
Reply from 196.22.142.12: bytes=32 time=920ms TTL=56
Reply from 196.22.142.12: bytes=32 time=257ms TTL=56
Reply from 196.22.142.12: bytes=32 time=163ms TTL=56
Reply from 196.22.142.12: bytes=32 time=160ms TTL=56
Reply from 196.22.142.12: bytes=32 time=100ms TTL=56
Reply from 196.22.142.12: bytes=32 time=135ms TTL=56
Reply from 196.22.142.12: bytes=32 time=162ms TTL=56
Reply from 196.22.142.12: bytes=32 time=89ms TTL=56
Reply from 196.22.142.12: bytes=32 time=257ms TTL=56
Reply from 196.22.142.12: bytes=32 time=105ms TTL=56
Reply from 196.22.142.12: bytes=32 time=50ms TTL=56
Request timed out.
Reply from 196.22.142.12: bytes=32 time=239ms TTL=56
Reply from 196.22.142.12: bytes=32 time=147ms TTL=56
Reply from 196.22.142.12: bytes=32 time=126ms TTL=56
Reply from 196.22.142.12: bytes=32 time=62ms TTL=56
Reply from 196.22.142.12: bytes=32 time=120ms TTL=56
Reply from 196.22.142.12: bytes=32 time=97ms TTL=56
Reply from 196.22.142.12: bytes=32 time=60ms TTL=56
Reply from 196.22.142.12: bytes=32 time=97ms TTL=56
Reply from 196.22.142.12: bytes=32 time=79ms TTL=56
Reply from 196.22.142.12: bytes=32 time=82ms TTL=56
Reply from 196.22.142.12: bytes=32 time=69ms TTL=56
Reply from 196.22.142.12: bytes=32 time=176ms TTL=56
Reply from 196.22.142.12: bytes=32 time=294ms TTL=56
Reply from 196.22.142.12: bytes=32 time=893ms TTL=56
Reply from 196.22.142.12: bytes=32 time=749ms TTL=56
Reply from 196.22.142.12: bytes=32 time=257ms TTL=56
Reply from 196.22.142.12: bytes=32 time=144ms TTL=56
Reply from 196.22.142.12: bytes=32 time=142ms TTL=56
Reply from 196.22.142.12: bytes=32 time=60ms TTL=56

Ping statistics for 196.22.142.12:
    Packets: Sent = 79, Received = 77, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 2506ms, Average = 253ms

This is ridiculous, I can't even load the mybroadband speedtest.
 
Last edited:
Murmaider said:
Anyone else having issues today?

Code: 
C:\Users\stryd_000>ping bitco.co.za -t

Pinging bitco.co.za [196.22.142.12] with 32 bytes of data:
Reply from 196.22.142.12: bytes=32 time=202ms TTL=56
Reply from 196.22.142.12: bytes=32 time=179ms TTL=56
Reply from 196.22.142.12: bytes=32 time=118ms TTL=56
Reply from 196.22.142.12: bytes=32 time=212ms TTL=56
Reply from 196.22.142.12: bytes=32 time=259ms TTL=56
Reply from 196.22.142.12: bytes=32 time=327ms TTL=56
Reply from 196.22.142.12: bytes=32 time=175ms TTL=56
Reply from 196.22.142.12: bytes=32 time=151ms TTL=56
Reply from 196.22.142.12: bytes=32 time=138ms TTL=56
Reply from 196.22.142.12: bytes=32 time=85ms TTL=56
Reply from 196.22.142.12: bytes=32 time=102ms TTL=56
Reply from 196.22.142.12: bytes=32 time=191ms TTL=56
Reply from 196.22.142.12: bytes=32 time=127ms TTL=56
Reply from 196.22.142.12: bytes=32 time=195ms TTL=56
Reply from 196.22.142.12: bytes=32 time=302ms TTL=56
Reply from 196.22.142.12: bytes=32 time=169ms TTL=56
Reply from 196.22.142.12: bytes=32 time=196ms TTL=56
Reply from 196.22.142.12: bytes=32 time=194ms TTL=56
Reply from 196.22.142.12: bytes=32 time=191ms TTL=56
Reply from 196.22.142.12: bytes=32 time=199ms TTL=56
Reply from 196.22.142.12: bytes=32 time=176ms TTL=56
Reply from 196.22.142.12: bytes=32 time=163ms TTL=56
Reply from 196.22.142.12: bytes=32 time=281ms TTL=56
Reply from 196.22.142.12: bytes=32 time=337ms TTL=56
Reply from 196.22.142.12: bytes=32 time=226ms TTL=56
Reply from 196.22.142.12: bytes=32 time=215ms TTL=56
Reply from 196.22.142.12: bytes=32 time=231ms TTL=56
Reply from 196.22.142.12: bytes=32 time=2248ms TTL=56
Reply from 196.22.142.12: bytes=32 time=138ms TTL=56
Reply from 196.22.142.12: bytes=32 time=155ms TTL=56
Reply from 196.22.142.12: bytes=32 time=272ms TTL=56
Reply from 196.22.142.12: bytes=32 time=170ms TTL=56
Request timed out.
Reply from 196.22.142.12: bytes=32 time=2506ms TTL=56
Reply from 196.22.142.12: bytes=32 time=656ms TTL=56
Reply from 196.22.142.12: bytes=32 time=113ms TTL=56
Reply from 196.22.142.12: bytes=32 time=89ms TTL=56
Reply from 196.22.142.12: bytes=32 time=127ms TTL=56
Reply from 196.22.142.12: bytes=32 time=255ms TTL=56
Reply from 196.22.142.12: bytes=32 time=173ms TTL=56
Reply from 196.22.142.12: bytes=32 time=120ms TTL=56
Reply from 196.22.142.12: bytes=32 time=97ms TTL=56
Reply from 196.22.142.12: bytes=32 time=124ms TTL=56
Reply from 196.22.142.12: bytes=32 time=141ms TTL=56
Reply from 196.22.142.12: bytes=32 time=159ms TTL=56
Reply from 196.22.142.12: bytes=32 time=66ms TTL=56
Reply from 196.22.142.12: bytes=32 time=143ms TTL=56
Reply from 196.22.142.12: bytes=32 time=172ms TTL=56
Reply from 196.22.142.12: bytes=32 time=920ms TTL=56
Reply from 196.22.142.12: bytes=32 time=257ms TTL=56
Reply from 196.22.142.12: bytes=32 time=163ms TTL=56
Reply from 196.22.142.12: bytes=32 time=160ms TTL=56
Reply from 196.22.142.12: bytes=32 time=100ms TTL=56
Reply from 196.22.142.12: bytes=32 time=135ms TTL=56
Reply from 196.22.142.12: bytes=32 time=162ms TTL=56
Reply from 196.22.142.12: bytes=32 time=89ms TTL=56
Reply from 196.22.142.12: bytes=32 time=257ms TTL=56
Reply from 196.22.142.12: bytes=32 time=105ms TTL=56
Reply from 196.22.142.12: bytes=32 time=50ms TTL=56
Request timed out.
Reply from 196.22.142.12: bytes=32 time=239ms TTL=56
Reply from 196.22.142.12: bytes=32 time=147ms TTL=56
Reply from 196.22.142.12: bytes=32 time=126ms TTL=56
Reply from 196.22.142.12: bytes=32 time=62ms TTL=56
Reply from 196.22.142.12: bytes=32 time=120ms TTL=56
Reply from 196.22.142.12: bytes=32 time=97ms TTL=56
Reply from 196.22.142.12: bytes=32 time=60ms TTL=56
Reply from 196.22.142.12: bytes=32 time=97ms TTL=56
Reply from 196.22.142.12: bytes=32 time=79ms TTL=56
Reply from 196.22.142.12: bytes=32 time=82ms TTL=56
Reply from 196.22.142.12: bytes=32 time=69ms TTL=56
Reply from 196.22.142.12: bytes=32 time=176ms TTL=56
Reply from 196.22.142.12: bytes=32 time=294ms TTL=56
Reply from 196.22.142.12: bytes=32 time=893ms TTL=56
Reply from 196.22.142.12: bytes=32 time=749ms TTL=56
Reply from 196.22.142.12: bytes=32 time=257ms TTL=56
Reply from 196.22.142.12: bytes=32 time=144ms TTL=56
Reply from 196.22.142.12: bytes=32 time=142ms TTL=56
Reply from 196.22.142.12: bytes=32 time=60ms TTL=56

Ping statistics for 196.22.142.12:
    Packets: Sent = 79, Received = 77, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 2506ms, Average = 253ms

This is ridiculous, I can't even load the mybroadband speedtest.
Click to expand...

It appears they have messed up my connection since upgrading me to the 10MB.

I am only getting 0.12mb upload speeds.
 
Murmaider said:
It appears they have messed up my connection since upgrading me to the 10MB.

I am only getting 0.12mb upload speeds.
Click to expand...

For the first time yesterday I had a few strange lag spikes in CS:GO. No train smash but it did annoy me at times. It got better again around 23:00. Might have been something on the network, but mine seems to be all ok again.
 
Nephew_ said:
Received this email today. :cry:
Wonder if they just want to focus on business users, or are their "airspace" full and they do not want to oversell (actually that is what the email says).
Click to expand...

The consumer space is fraught with low margins and troublesome users who are usually squeakier wheels than corporate clients. The CPA adds to these woes, providing corporate grade legal protection to the man on the street (aka the home broadband user).
We saw it in 1999-2001, when the "Corporate" ISPs consolidated and sold off their dial-up subscriber user bases to the highest bidder. There is money to be made in the consumer business, but the business model needs to be lean, and geared towards selling (and supporting) cheap services very quickly and cheaply to the masses. So automation, self-service and cheap service delivery (coupled with emotion driven marketing as seen by Afrihost and some other ISPs in 2008-2012) is key. Which begs the question: Why do corporate-focussed ISPs even bother with IHUs (interactive home users)?
Bandwidth patterns for one - after 17H00, most businesses wind down, and the cost of the ISP's IPLC (and local peering) has already been paid for, but is underutilised (akin to an empty plane seat after takeoff).
To the ISP who wants to make money (and better margins) for their investors very quickly, an IHU is a third-grade afterthought, merely feeding off the scraps of bandwidth that they cannot sell to corporates (after business hours). Sometimes the ISP forgets that the IHUs have enabled them to recoup losses at off-peak hours and therefore allowed them buy more bandwidth to support corporate clients during the business day, in addition to allowing them to extend their (corporate) support desk hours from 8/5 to 16/7 or even 24/7.
After 23H45, the IHUs are (mostly) in slumberland, and the DHTs (die-hard techies) too -- only difference is that the DHTs have automated their downloads (news servers, FTP, torrents and darkweb activity) to utilise the full spectrum of the service, so many ISPs offer generous or even "unlimited" services during these hours.

An ISP who decides to no longer take on home users is either:
1) oversubscribed in the "after-hours" timeslots; and/or
2) gatvol of taking consumer complaints after pumpkin time; and/or
3) has recently hired a financial director who does not understand the complementary business model; and/or
4) hasn't got the automation, systems and people to cope with the "cheap" sales and the support cycle associated with consumer service.
Or, various combinations of the above. Go figure.
 
Last edited:
infscrtyrisk said:
The consumer space is fraught with low margins and troublesome users who are usually squeakier wheels than corporate clients. The CPA adds to these woes, providing corporate grade legal protection to the man on the street (aka the home broadband user).
We saw it in 1999-2001, when the "Corporate" ISPs consolidated and sold off their dial-up subscriber user bases to the highest bidder. There is money to be made in the consumer business, but the business model needs to be lean, and geared towards selling (and supporting) cheap services very quickly and cheaply to the masses. So automation, self-service and cheap service delivery (coupled with emotion driven marketing as seen by Afrihost and some other ISPs in 2008-2012) is key. Which begs the question: Why do corporate-focussed ISPs even bother with IHUs (interactive home users)?
Bandwidth patterns for one - after 17H00, most businesses wind down, and the cost of the ISP's IPLC (and local peering) has already been paid for, but is underutilised (akin to an empty plane seat after takeoff).
To the ISP who wants to make money (and better margins) for their investors very quickly, an IHU is a third-grade afterthought, merely feeding off the scraps of bandwidth that they cannot sell to corporates (after business hours). Sometimes the ISP forgets that the IHUs have enabled them to recoup losses at off-peak hours and therefore allowed them buy more bandwidth to support corporate clients during the business day, in addition to allowing them to extend their (corporate) support desk hours from 8/5 to 16/7 or even 24/7.
After 23H45, the IHUs are (mostly) in slumberland, and the DHTs (die-hard techies) too -- only difference is that the DHTs have automated their downloads (news servers, FTP, torrents and darkweb activity) to utilise the full spectrum of the service, so many ISPs offer generous or even "unlimited" services during these hours.

An ISP who decides to no longer take on home users is either:
1) oversubscribed in the "after-hours" timeslots; and/or
2) gatvol of taking consumer complaints after pumpkin time; and/or
3) has recently hired a financial director who does not understand the complementary business model; and/or
4) hasn't got the automation, systems and people to cope with the "cheap" sales and the support cycle associated with consumer service.
Or, various combinations of the above. Go figure.
Click to expand...
Interesting view and makes a lot of sense. I for one am a business customer of Bitco and since we signed up i really have not had to contact their support desk because the connection just works well for our office needs (except when we get throttled when downloading windows updates). So i do understand when you say the home users are more likely to make noise as compared to their corporate clients. However ditching the home indeed means their data pipes are underutilised after hours which is money lost for them. I'm sure if Bitco had the patience they would have made things work, just the same way ADSL ISPs make things work
 
I'm having that problem again where certain sites aren't accessible.

For instance Cracked.com won't load for me again. And some Facebook images don't load. And Disqus doesn't load. :(

Are these things working for other people?
 
Solitude said:
I'm having that problem again where certain sites aren't accessible.

For instance Cracked.com won't load for me again. And some Facebook images don't load. And Disqus doesn't load. :(

Are these things working for other people?
Click to expand...
Also have a few weird things going on yeah. Cracked works for me, but some websites don't load all images.
 
No-Rules said:
Spoke to Richard and according to him nothing changed on the network ��
Click to expand...

To me it looks like the same problem as last time. Just with different sites being affected. So maybe they can just fix whatever they fixed last time.

What was the actual fault last time in any case?

I can't connect to Raptr either.
 
Last edited:
Definitely something wrong on the network. Jhb north on my end. Having all kinds of weird traffic issues to certain locations.
 
Yeah I'm having issues tonight getting into vudu.com and a couple other international streaming services.
 
Hi Guys,

One of the main international upstream providers is experiencing peering & DNS issues.

We have disabled this circuit and re-routed traffic, all services should be operational like normal.

We will work with the international provider to resolve the issue and re-route traffic once the fault has been cleared.

Mike
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X