BitCo Consumer Review

I think BitCo has served me good use lately ;) I couldn't be happier
 

Attachments

  • image.jpg
    image.jpg
    10.1 KB · Views: 163
Well today is the big BF4 test day, for what i have seen so far Bitco have made a huge improvement.
The packet loss seems to have calmed down and the lag has almost become a thing of the past.

However the matchmaking and server entry is still not 100% sorted.If possible if anybody else is having this issue please post the IP addresses of the sever that is giving you hell and Mike will investigate further.

How to find the xbox one server IP

1. Log on to battlelog http://battlelog.battlefield.com/bf4/
2. Go to the multiplayer option
3. Look for server history
4.Select server details
5.Bottom right hand side you will see the IP address for the server.

5ur1e.jpg

aI0w9.png

Please note the above should apply for all platforms as they all use the Battlelog app


I will try and feedback as much info as possible but would also like the others guys on the forum to share their results and feedback, on all platforms.

It would be great if we could create a squad and do a community test simultaneously which would give a broader view of experiences and results.
If you keen, Im on Xbox One I should be on line at about 3:30pm.

Gamertag:- disiza

Best regards

disiza
 
Last edited:
Well I can't see the improvement on my side.

Reply from 196.28.69.6: bytes=32 time=7ms TTL=122

Ping statistics for 196.28.69.6:
Packets: Sent = 1431, Received = 1429, Lost = 5 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 49ms, Average = 12ms

bf4 dc.jpg
 
No-Rules said:
Well I can't see the improvement on my side.

Reply from 196.28.69.6: bytes=32 time=7ms TTL=122

Ping statistics for 196.28.69.6:
Packets: Sent = 1431, Received = 1429, Lost = 5 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 49ms, Average = 12ms

View attachment 221048
Click to expand...

Hi NO-RULES

1.I am assume that server is a SA server?
2. The 30000 port is it forwarded on your router and all the other ports required?
3.Can you confirm that other players connecting to the server, are they having the same problem or not?

Im going to do a ping test to the SA server and then to a international server and see if there is any difference.


Watch this space
 
Last edited:
disiza said:
Hi NO-RULES

1.I am assume that server is a SA server?
2. The 30000 port is it forwarded on your router?
3.Can you confirm that other players connecting to the server, are they having the same problem or not?

Im going to do a ping test to the SA server and then to a international server and see if there is any difference.


Watch this space
Click to expand...

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

ping -n 200 196.28.69.6

Pinging 196.28.69.6 with 32 bytes of data:
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Request timed out.
Reply from 196.28.69.6: bytes=32 time=7ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=5ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=5ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=5ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Request timed out.
Reply from 196.28.69.6: bytes=32 time=105ms TTL=122
Reply from 196.28.69.6: bytes=32 time=5ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=8ms TTL=122
Reply from 196.28.69.6: bytes=32 time=7ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=5ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=5ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Request timed out.
Reply from 196.28.69.6: bytes=32 time=106ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=5ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122

Reply from 196.28.69.6: bytes=32 time=5ms TTL=122
Reply from 196.28.69.6: bytes=32 time=7ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=9ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Request timed out.
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=6ms TTL=122
Reply from 196.28.69.6: bytes=32 time=5ms TTL=122

Ping statistics for 196.28.69.6:
Packets: Sent = 200, Received = 196, Lost = 4 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 106ms, Average = 7ms

There seems to be a re-occurring packet loss pattern on the SA server above.

ping -n 200 31.204.140.157

Pinging 31.204.140.157 with 32 bytes of data:
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=173ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=177ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=174ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=173ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=174ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=173ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=173ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=173ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=171ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116
Reply from 31.204.140.157: bytes=32 time=172ms TTL=116

Ping statistics for 31.204.140.157:
Packets: Sent = 200, Received = 200, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 177ms, Average = 172ms

This was a server in the UK and as you can see........ stable
 
PC Battlefield 4 Ports to be forwarded:- TCP 80, 443, 9988, 17502, 20000-20100, 22990, 42127, 30000 to 30170 -- UDP 3659, 14000-14016, 22990-23006, 25200-25300, 30000 to 30170

Try this it might improve the connection
 
disiza said:
PC Battlefield 4 Ports to be forwarded:- TCP 80, 443, 9988, 17502, 20000-20100, 22990, 42127, 30000 to 30170 -- UDP 3659, 14000-14016, 22990-23006, 25200-25300, 30000 to 30170

Try this it might improve the connection
Click to expand...

Thanks Disiza this helped a bit, seen it on battlelog but they left out the 30000-30170 ports

I went and looked at the Telkom gaming server I play on, the port there is 31554 opened this on my router and played for 40min instead of 5min before getting the connection timed out error some hope here!

No other server works
 
Last edited:
disiza said:
PC Battlefield 4 Ports to be forwarded:- TCP 80, 443, 9988, 17502, 20000-20100, 22990, 42127, 30000 to 30170 -- UDP 3659, 14000-14016, 22990-23006, 25200-25300, 30000 to 30170

Try this it might improve the connection
Click to expand...

disiza said:
Hi NO-RULES

1.I am assume that server is a SA server?
2. The 30000 port is it forwarded on your router and all the other ports required?
3.Can you confirm that other players connecting to the server, are they having the same problem or not?

Im going to do a ping test to the SA server and then to a international server and see if there is any difference.


Watch this space
Click to expand...

Hi Disiza,

1.Yes all lobby's I join is local.
2.All relevant port are open.
3.I know my friends is playing just fine. (Telkom line)

thank you for helping out.
 
Tough job there Mike :P

Regarding the issues that everyone has been having the BF. I play on PC and with the exception of sometimes being kicked off the server I haven't had any major issues. Quite smooth actually.

BitCo said:
Hi Guys,

BF4 - Update

We have made significant progress on BF4 and we have been testing with both the Xbox One & PS4 consoles throughout the week.

We can confirm it is working much better and you should be able to connect to majority of the international servers

We confirm a few servers are still giving errors and we are working hard on a fix.

I will be taking the Xbox One home with me today and playing as much as possible over the weekend on my 10Mbps Home link to ensure everything is working 100%

I will also be engaging with a few users on this forum to ensure our test results are consistent between all the users on the network.

Mike
Click to expand...
 
Simply put .......BF4 issue, connection to the game has improved however the quality of gaming is shocking, heavy lag, rubberbanding(around 2 blocks of buildings).......Bitco still unacceptable please advise
 
Solitude said:
That sucks. May they arrive soon! Let us know how it goes.
Click to expand...
They just pitched
20150601_160948.jpg
EDIT: No clear LoS or related issue, so no install. Will have to wait for the report I suppose. Honestly, judging by the haste of their arrival and departure, I do not think there was any intention to install..
 
Last edited:
disiza said:
Simply put .......BF4 issue, connection to the game has improved however the quality of gaming is shocking, heavy lag, rubberbanding(around 2 blocks of buildings).......Bitco still unacceptable please advise
Click to expand...

Cant even play ten minutes, do you know if it is purely bitco blocking ports? Nothing done on my router works, i play on pc
 
lcbxx said:
They just pitched
View attachment 221432
EDIT: No clear LoS or related issue, so no install. Will have to wait for the report I suppose. Honestly, judging by the haste of their arrival and departure, I do not think there was any intention to install..
Click to expand...

That sucks so much. And surely that guy could have lifted the dish much higher? The other guy is standing in the way!
 
BF 4 absolutely shocking, packet loss ranging from 11% to 100%
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X