BitCo Consumer Review

Well my connection just went for a ball of ****.

Senshi said:
Reply from 196.22.142.12: bytes=32 time=7ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 196.22.142.12: bytes=32 time=252ms TTL=58
Reply from 196.22.142.12: bytes=32 time=7ms TTL=58
Reply from 196.22.142.12: bytes=32 time=331ms TTL=58
Reply from 196.22.142.12: bytes=32 time=910ms TTL=58
Reply from 196.22.142.12: bytes=32 time=2137ms TTL=58
Reply from 196.22.142.12: bytes=32 time=9ms TTL=58
Reply from 196.22.142.12: bytes=32 time=1717ms TTL=58
Reply from 196.22.142.12: bytes=32 time=11ms TTL=58
Reply from 196.22.142.12: bytes=32 time=404ms TTL=58
Reply from 196.22.142.12: bytes=32 time=287ms TTL=58
Reply from 196.22.142.12: bytes=32 time=8ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Click to expand...

Restarted router and dish, still the same thing.
 
stormj said:
May I take this opportunity to thank BitCo for a very neat installation and high quality equipment.
I like the Tomato OS on the Lyksys E900 router supplied.
The quality of the "line" is very good with a ping of 6 to 15ms to google.com
We had no latency issues with online gaming so far.
BitCo, Please keep up the good work!
Click to expand...

Latency and packet loss are not the same thing, my latency is always low*(although it will spike slightly by like 30-40ms when a packet is lost), yet I rubberband all over, what games do you play?
 
Last edited:
Senshi said:
Well my connection just went for a ball of ****.



Restarted router and dish, still the same thing.
Click to expand...

Thats pretty much what mine does intermittently when the packet loss starts getting bad, can ping anything, and every other request will time out
 
I've had the same issue with Destiny. Sat this past Friday to try and sort it out with the core director with no luck.

What's puzzling is that it's fine after 6. I've played CS:GO during the day, no problems.

Wikkels88 said:
Out of interest sake, is there anyone else on here that uses Bitco to play FPS type games online without any packet loss? (Packet loss causes rubber banding, so you'll notice it pretty quickly) ... It would appear that Bitco is not ideal for this type of gaming...

From what I could gather after some research, fps games use a higher tick rate(the amount of times per second the server updates the client) and WISP type ISP's just can't keep up due to interference in the signal that's pretty much unavoidable seeing that the means of transport is, well, the atmosphere...

I have to praise Bitco on their part, they have really tried a lot to sort out this issue, but no solutions have been found. I have an appointment with their Technical Director on Friday where' he's going to monitor my link while I play, to analyze the game data being sent to and from the client/server, I really do appreciate the effort, but I'm not getting my hopes up.

After reading more into this type of technology, and after experiencing the problems it causes with gaming first hand (without trying to sound like a douche) I really don't think Bitco should advertise their packages for gaming... The connection is perfect for things like browsing, game downloads, streaming etc. But for gaming in my experience its really awful:(
Click to expand...
 
I play Destiny on Xbox 360. Played Saturday, the whole day, without any lag.
I'm connected to the upgraded Helderkruin Highsite, if it makes any difference.
We just had a lekker Storm outside with lots of lightning and my PingTrace shows that my uplink was totally unaffected. :)
 
PingPlotter, not PingTrace in my previous reply. It record traceroutes at set intervals and shows timeline graphs of every hop. It is good for monitoring latency and also packet loss etc.
 
Wikkels88 said:
Out of interest sake, is there anyone else on here that uses Bitco to play FPS type games online without any packet loss? (Packet loss causes rubber banding, so you'll notice it pretty quickly) ... It would appear that Bitco is not ideal for this type of gaming...

From what I could gather after some research, fps games use a higher tick rate(the amount of times per second the server updates the client) and WISP type ISP's just can't keep up due to interference in the signal that's pretty much unavoidable seeing that the means of transport is, well, the atmosphere...

I have to praise Bitco on their part, they have really tried a lot to sort out this issue, but no solutions have been found. I have an appointment with their Technical Director on Friday where' he's going to monitor my link while I play, to analyze the game data being sent to and from the client/server, I really do appreciate the effort, but I'm not getting my hopes up.

After reading more into this type of technology, and after experiencing the problems it causes with gaming first hand (without trying to sound like a douche) I really don't think Bitco should advertise their packages for gaming... The connection is perfect for things like browsing, game downloads, streaming etc. But for gaming in my experience its really awful:(
Click to expand...

I have played both CoD and battlefield Series on PSN with no issues on a 5MB link. I do believe if you experiencing issues with a specific game you can always call them and they can help out with prioritizing the port the game is running on.
 
Wikkels88 said:
Out of interest sake, is there anyone else on here that uses Bitco to play FPS type games online without any packet loss? (Packet loss causes rubber banding, so you'll notice it pretty quickly) ... It would appear that Bitco is not ideal for this type of gaming...

From what I could gather after some research, fps games use a higher tick rate(the amount of times per second the server updates the client) and WISP type ISP's just can't keep up due to interference in the signal that's pretty much unavoidable seeing that the means of transport is, well, the atmosphere...

I have to praise Bitco on their part, they have really tried a lot to sort out this issue, but no solutions have been found. I have an appointment with their Technical Director on Friday where' he's going to monitor my link while I play, to analyze the game data being sent to and from the client/server, I really do appreciate the effort, but I'm not getting my hopes up.

After reading more into this type of technology, and after experiencing the problems it causes with gaming first hand (without trying to sound like a douche) I really don't think Bitco should advertise their packages for gaming... The connection is perfect for things like browsing, game downloads, streaming etc. But for gaming in my experience its really awful:(
Click to expand...

I play Quake Live online which is arguably the most sensitive FPS in terms of raw latency and tick rate and I have 0 issues.

No rubberbanding, lagging or spiking. The only issue I have is when my link goes down or like last night goes bonkers with packet loss (I think the storm was causing that though), so I have to disagree with your comment about gaming.

Perhaps the area you stay in has lots of interference but that's not necessarily BitCo's fault.
 
Hi Guys

We have added a new, larger international route to Europe and round trip latency to London is now ~160ms. This should improve gaming somewhat.

Garth
 
PING www.bbc.net.uk

64 bytes from 212.58.246.92: icmp_seq=1 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=2 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=3 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=4 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=5 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=6 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=7 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=8 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=9 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=10 ttl=54 time=160 ms
 
garthvs said:
PING www.bbc.net.uk

64 bytes from 212.58.246.92: icmp_seq=1 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=2 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=3 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=4 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=5 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=6 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=7 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=8 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=9 ttl=54 time=160 ms
64 bytes from 212.58.246.92: icmp_seq=10 ttl=54 time=160 ms
Click to expand...

Bitco

Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data:
Reply from 212.58.244.18: bytes=32 time=167ms TTL=52
Reply from 212.58.244.18: bytes=32 time=169ms TTL=52
Reply from 212.58.244.18: bytes=32 time=169ms TTL=52
Reply from 212.58.244.18: bytes=32 time=167ms TTL=52

ADSL

Pinging bbc.co.uk [212.58.246.104] with 32 bytes of data:
Reply from 212.58.246.104: bytes=32 time=223ms TTL=50
Reply from 212.58.246.104: bytes=32 time=215ms TTL=50
Reply from 212.58.246.104: bytes=32 time=265ms TTL=50
Reply from 212.58.246.104: bytes=32 time=281ms TTL=50
 
koeksGHT said:
Bitco

Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data:
Reply from 212.58.244.18: bytes=32 time=167ms TTL=52
Reply from 212.58.244.18: bytes=32 time=169ms TTL=52
Reply from 212.58.244.18: bytes=32 time=169ms TTL=52
Reply from 212.58.244.18: bytes=32 time=167ms TTL=52

ADSL

Pinging bbc.co.uk [212.58.246.104] with 32 bytes of data:
Reply from 212.58.246.104: bytes=32 time=223ms TTL=50
Reply from 212.58.246.104: bytes=32 time=215ms TTL=50
Reply from 212.58.246.104: bytes=32 time=265ms TTL=50
Reply from 212.58.246.104: bytes=32 time=281ms TTL=50
Click to expand...

A nice 50-80ms difference :-)
 
Anyone having connection problems again

Meyersal Alberton

This is happening often now :-(

Support checked line last time and they say all is 100 %

No rain or lightning etc and nothing running currently

Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=1215.394 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=60 time=212.182 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=60 time=154.094 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=60 time=9.157 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=60 time=10.056 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=60 time=9.782 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=60 time=12.208 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=60 time=12.622 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=60 time=13.586 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=60 time=10.129 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=60 time=8.669 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=60 time=11.653 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=60 time=8.582 ms
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
Request timeout for icmp_seq 46
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
64 bytes from 8.8.8.8: icmp_seq=50 ttl=60 time=15.963 ms
Request timeout for icmp_seq 51
64 bytes from 8.8.8.8: icmp_seq=52 ttl=60 time=390.925 ms
Request timeout for icmp_seq 53
Request timeout for icmp_seq 54
64 bytes from 8.8.8.8: icmp_seq=55 ttl=60 time=334.905 ms
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
64 bytes from 8.8.8.8: icmp_seq=58 ttl=60 time=859.828 ms
Request timeout for icmp_seq 59
64 bytes from 8.8.8.8: icmp_seq=60 ttl=60 time=109.160 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=60 time=217.157 ms
Request timeout for icmp_seq 62
64 bytes from 8.8.8.8: icmp_seq=63 ttl=60 time=382.591 ms
64 bytes from 8.8.8.8: icmp_seq=64 ttl=60 time=10.177 ms
64 bytes from 8.8.8.8: icmp_seq=65 ttl=60 time=197.915 ms
64 bytes from 8.8.8.8: icmp_seq=66 ttl=60 time=11.425 ms
64 bytes from 8.8.8.8: icmp_seq=67 ttl=60 time=188.334 ms
64 bytes from 8.8.8.8: icmp_seq=68 ttl=60 time=107.351 ms
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72
Request timeout for icmp_seq 73
Request timeout for icmp_seq 74
Request timeout for icmp_seq 75
 
Viashen said:
Anyone having connection problems again

Meyersal Alberton

This is happening often now :-(

Support checked line last time and they say all is 100 %

No rain or lightning etc and nothing running currently

Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=1215.394 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=60 time=212.182 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=60 time=154.094 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=60 time=9.157 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=60 time=10.056 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=60 time=9.782 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=60 time=12.208 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=60 time=12.622 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=60 time=13.586 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=60 time=10.129 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=60 time=8.669 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=60 time=11.653 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=60 time=8.582 ms
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
Request timeout for icmp_seq 46
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
64 bytes from 8.8.8.8: icmp_seq=50 ttl=60 time=15.963 ms
Request timeout for icmp_seq 51
64 bytes from 8.8.8.8: icmp_seq=52 ttl=60 time=390.925 ms
Request timeout for icmp_seq 53
Request timeout for icmp_seq 54
64 bytes from 8.8.8.8: icmp_seq=55 ttl=60 time=334.905 ms
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
64 bytes from 8.8.8.8: icmp_seq=58 ttl=60 time=859.828 ms
Request timeout for icmp_seq 59
64 bytes from 8.8.8.8: icmp_seq=60 ttl=60 time=109.160 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=60 time=217.157 ms
Request timeout for icmp_seq 62
64 bytes from 8.8.8.8: icmp_seq=63 ttl=60 time=382.591 ms
64 bytes from 8.8.8.8: icmp_seq=64 ttl=60 time=10.177 ms
64 bytes from 8.8.8.8: icmp_seq=65 ttl=60 time=197.915 ms
64 bytes from 8.8.8.8: icmp_seq=66 ttl=60 time=11.425 ms
64 bytes from 8.8.8.8: icmp_seq=67 ttl=60 time=188.334 ms
64 bytes from 8.8.8.8: icmp_seq=68 ttl=60 time=107.351 ms
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72
Request timeout for icmp_seq 73
Request timeout for icmp_seq 74
Request timeout for icmp_seq 75
Click to expand...

Hi Viashen,

please can you log with [email protected] i can see your connection is dropping and has a latency problem

Seems like it has stabilized now but adjustments need to be made ASAP

Please can you PM us if not resolved tomorrow morning once technical make adjustments

Mike
 
Thanks for the update Garth.

Very decent latency from EU.

garthvs said:
Hi Guys

We have added a new, larger international route to Europe and round trip latency to London is now ~160ms. This should improve gaming somewhat.

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