BitCo Consumer Review

W

Wikkels88

Expert Member
Joined
Jul 3, 2012
Messages
1,514
Tested some Counter Strike during the day the past few days, and it runs flawless, sitting at 10-15ms ping, unfortunately I can't game during the day, you know work kinda gets in the way:D Needless to say when I get home in the evenings my ping hovers between 50-100ms (To local JHB servers) and packetloss every minute or so.... Why oh why is my connection so bad for games in the evening:(
 
W

Wikkels88

Expert Member
Joined
Jul 3, 2012
Messages
1,514
FUP seems to be out of wack lately, yesterday when I got home my connection was FUP'd, my gf was at home on her tablet during the day, playing games, checking fb and "abusing" the hell out of the connection I suppose, none the less I gave Bitco the benefit of the doubt.

When I went to bed last night at around 11pm I queued a few p2p downloads, this morning they were still running, did I speed test and my line was not FUP'd:confused: Its almost like my connection is automatically getting FUP's during peak hours, whether I "abuse" the connection or not
 
Last edited:
Solitude

Solitude

Executive Member
Joined
Jul 23, 2008
Messages
7,312
I received my call for the BitCo installation! And then I asked them if we can postpone it for a month. Since there's a possibility of us getting fibre in the complex.

The BitCo lady was very sweet on the phone and she understood my situation.
 
S

Snox

Member
Joined
Nov 8, 2013
Messages
23
Solitude said:
The BitCo lady was very sweet on the phone and she understood my situation.
Click to expand...

Also received a call yesterday (13 May). Technician popping me a visit on Monday (18 May). For these who submitted an application. This was my 5th week after my invoice.
 
M

MJ89

Active Member
Joined
Sep 4, 2014
Messages
61
Has anyone done a ping test to the Bitco supplied router ie ping -n 50 192.168.1.1

This is done directly connected to the router should the pings not all be 1ms or 2ms and not have spikes of 800 to 1500ms?.

C:\Users\Mark Jones>ping -n 50 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=878ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1396ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1521ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1515ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1523ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1523ms, Average = 137ms
 
N

No-Rules

Well-Known Member
Joined
Feb 14, 2011
Messages
309
MJ89 said:
Has anyone done a ping test to the Bitco supplied router ie ping -n 50 192.168.1.1

This is done directly connected to the router should the pings not all be 1ms or 2ms and not have spikes of 800 to 1500ms?.

C:\Users\Mark Jones>ping -n 50 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=878ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1396ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1521ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1515ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1523ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1523ms, Average = 137ms
Click to expand...

Majority of my ping is 1ms and the highest spike is 4ms
 
Pitbull

Pitbull

Verboten
Joined
Apr 8, 2006
Messages
64,307
MJ89 said:
Has anyone done a ping test to the Bitco supplied router ie ping -n 50 192.168.1.1

This is done directly connected to the router should the pings not all be 1ms or 2ms and not have spikes of 800 to 1500ms?.

C:\Users\Mark Jones>ping -n 50 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=878ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1396ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1521ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1515ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1523ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1523ms, Average = 137ms
Click to expand...

When I did my speedtest for that MyBB speed test I saw something like this briefly on mine too. There is a complete drop in speed for about a second then it picks up again. Might have just been a fluke on my side. But I saw it briefly. That is only 50 pings though so the time frame is about 30 seconds with 2 spikes. Doesn't sound right. I'll run a ping test on mine also tonight just to be sure there isn't a drop in speed for brief periods like I saw last night.

I haven't experience it while surfing or gaming. So I'll have to double check.
 
G

goat2285

Member
Joined
May 15, 2015
Messages
23
Hi internet beings.

First time on this forum

Question:

Do anybody stay in Bonaero Park district( literally less than a km from the airport).

Can you please inform me how the service in this area is?

Thanks in advance.
 
Pitbull

Pitbull

Verboten
Joined
Apr 8, 2006
Messages
64,307
goat2285 said:
Hi internet beings.

First time on this forum

Question:

Do anybody stay in Bonaero Park district( literally less than a km from the airport).

Can you please inform me how the service in this area is?

Thanks in advance.
Click to expand...

Have you tried their website by adding your address to see if you've got coverage?

http://bitco.co.za/coverage-map/

Edit: Just checked. Looks like that area is covered by at least 6 towers. You should be able to get coverage no problem.
 
G

goat2285

Member
Joined
May 15, 2015
Messages
23
Thats brilliant news!! Thank you.

I did have a look at thr coverage and its well covered.

I just wondered if the aiport has problems or the trees ...and stuff.

But thank you for the reassurance.
 
W

Wikkels88

Expert Member
Joined
Jul 3, 2012
Messages
1,514
When I signed up with Bitco my pings were never higher than 20ms to local servers, lately im lucky if its below 100ms to jhb servers... The quality of my connection got so bad, its literally better to game on a 3g dongle lately, very dissapointed:( And NO I don't want to cancel my contract, I still need internet for other things, just sad that gaming is so bad on this connection
 
Last edited:
N

No-Rules

Well-Known Member
Joined
Feb 14, 2011
Messages
309
Did anyone notice if your dns is been throttled. One is without unotelly dns and it looks normal and the other one with and it's horrible. uploadfromtaptalk1431854106748.jpg
 

Attachments

  • uploadfromtaptalk1431854119124.jpg
    uploadfromtaptalk1431854119124.jpg
    26.2 KB · Views: 311
Last edited:
N

No-Rules

Well-Known Member
Joined
Feb 14, 2011
Messages
309
OCD said:
No-rules What are the ip's of the two dns you refer to please.
Click to expand...

Unotelly
197.189.212.164
197.242.94.51

I also tried another DNS service Unblock-Us
208.122.23.23
208.122.23.22

Between the two there is 1mg difference.
 
You must log in or register to reply here.
Top