BitCo Consumer Review

[BitCo]

Hi All,

Just wanted to let everyone know that we have cleared the fault related to the Seacom undersea cable and all services are restored over to the primary route

Latency is back to around 160ms return trip to Europe

Mike

 

[disiza]

Thxs for feedback Mike

 

[Goobie]

I'm considering going Bitco in Bloemfontein. I have a clear view of Naval Hill in general to my south with the possibility of a tree being in the way depending at which of the towers on Naval Hill I'm looking at.

Any Bloemfontein users here that can tell me which tower I should have LOS?

Thanks

 

[BitCo]

I'm considering going Bitco in Bloemfontein. I have a clear view of Naval Hill in general to my south with the possibility of a tree being in the way depending at which of the towers on Naval Hill I'm looking at.

Any Bloemfontein users here that can tell me which tower I should have LOS?

Thanks

Hi Goobie,

You are correct we are on the tower up on Naval Hill

It is the 42M red and white Lattice tower

you would need to be within a 6KM Range of the tower and have clear Line of sight to get a connection onto our network

Mike

 

[disiza]

Good News, LOS confirmed I was closer than i thought to the tower...... only 500m away. The friendly and professional installers are busy right now, will be up and running before Friday. They have confirmed the installation to be at its optimal....cant get any better.

So far so good!

Time to soak.

 

[Pitbull]

Good News, LOS confirmed I was closer than i thought to the tower...... only 500m away. The friendly and professional installers are busy right now, will be up and running before Friday. They have confirmed the installation to be at its optimal....cant get any better.

So far so good!

Time to soak.

Congratulations Welcome to the Bitco family

 

[disiza]

Soaking and soaking...................................................................and soaking, looking like a prune.......and soaking

 

[disiza]

Congratulations Welcome to the Bitco family

Thanks Pitbull.

 

[Aluroth]

Just a quick question, is there anyone else experiencing packet loss when just pinging the DNS server?

 

[disiza]

Picked up one small inconvenience, during the soaking period you don't have a LAN network ,no printing , no streaming of movies or music from the media server,no inter peripheral communication....you go dark for 3 days. Not to comfortable that the ISP has that much control over your LAN network.

 

[Sparky_za]

Good News, LOS confirmed I was closer than i thought to the tower...... only 500m away. The friendly and professional installers are busy right now, will be up and running before Friday. They have confirmed the installation to be at its optimal....cant get any better.

So far so good!

Time to soak.

Should have asked them to throw a fibre cable over the wall!

 

[disiza]

Got fibre access, to expensive

 

[koeksGHT]

Been getting 5mbps since yesterday pretty sure its not FUP.

Download Speed: 4733 kbps (591.6 KB/sec transfer rate)
Upload Speed: 1916 kbps (239.5 KB/sec transfer rate)
Latency: 19 ms
2/25/2015, 9:08:02 AM

 

[besterf]

Whoooohooo

Big ups to Brandon and his team, excellent service! And I am getting my router today!!!

This day is going to be a LOOOOOOOOONG @ss day

Let the internets begins.... what to play first....

 

[Aluroth]

Just a quick question, is there anyone else experiencing packet loss when just pinging the DNS server?

Anyone?

 

[Pitbull]

Anyone?

Which DNS?

I changed mine to Unotelly. Don't know what the default one is no more.

 

[Aluroth]

Which DNS?

I changed mine to Unotelly. Don't know what the default one is no more.

I get dropped packets if I ping anything, so I guess the connection between my dish and the tower is not that great.

 

[Pitbull]

I get dropped packets if I ping anything, so I guess the connection between my dish and the tower is not that great.

Just did one and mine seems fine:

Pinging www.bbc.co.uk [46.23.67.190] with 32 bytes of data:
Reply from 46.23.67.190: bytes=32 time=187ms TTL=55
Reply from 46.23.67.190: bytes=32 time=187ms TTL=55
Reply from 46.23.67.190: bytes=32 time=189ms TTL=55
Reply from 46.23.67.190: bytes=32 time=185ms TTL=55
Reply from 46.23.67.190: bytes=32 time=188ms TTL=55
Reply from 46.23.67.190: bytes=32 time=183ms TTL=55
Reply from 46.23.67.190: bytes=32 time=186ms TTL=55
Reply from 46.23.67.190: bytes=32 time=187ms TTL=55
Reply from 46.23.67.190: bytes=32 time=188ms TTL=55
Reply from 46.23.67.190: bytes=32 time=187ms TTL=55
Reply from 46.23.67.190: bytes=32 time=190ms TTL=55
Reply from 46.23.67.190: bytes=32 time=185ms TTL=55
Reply from 46.23.67.190: bytes=32 time=190ms TTL=55
Reply from 46.23.67.190: bytes=32 time=187ms TTL=55
Reply from 46.23.67.190: bytes=32 time=187ms TTL=55
Reply from 46.23.67.190: bytes=32 time=190ms TTL=55
Reply from 46.23.67.190: bytes=32 time=189ms TTL=55
Reply from 46.23.67.190: bytes=32 time=190ms TTL=55
Reply from 46.23.67.190: bytes=32 time=186ms TTL=55
Reply from 46.23.67.190: bytes=32 time=187ms TTL=55

Ping statistics for 46.23.67.190:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 190ms, Average = 187ms

 

[Aluroth]

Just did one and mine seems fine:

Could you maybe try with 250 pings? Thanks anyway

 

[Pitbull]

Could you maybe try with 250 pings? Thanks anyway

will run it and post the result

Ping statistics for 46.23.67.190:
Packets: Sent = 250, Received = 250, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 666ms, Average = 175ms

I just let it run wile watching netflix, don't know where the spike of 666 happened.