Looks like your connection to Bethesda.net Community Beta was lost, please wait while we try to reconnect.



@dev-br said:

Hey!
For almost a month now, I'm not able to play. Servers seem to be available but I even after 30 mins waiting time im not able to play. I guess it fails to make the UDP connection.
I'm from brazil and this is what I get from netstat while waiting:
TCP    192.168.0.119:49886    52.165.153.192:11709   TIME_WAIT
  TCP    192.168.0.119:49887    52.165.153.192:11703   TIME_WAIT
  TCP    192.168.0.119:49888    52.173.204.254:11701   TIME_WAIT
  TCP    192.168.0.119:49889    52.173.201.236:11702   TIME_WAIT
  TCP    192.168.0.119:49890    52.173.201.236:11704   TIME_WAIT
  TCP    192.168.0.119:49891    52.173.205.182:11701   ESTABLISHED
  TCP    192.168.0.119:49892    52.173.94.128:11701    ESTABLISHED
  TCP    192.168.0.119:49893    52.173.201.236:11701   TIME_WAIT
  TCP    192.168.0.119:49894    52.173.206.178:11701   ESTABLISHED
  TCP    192.168.0.119:49895    52.173.207.63:11701    ESTABLISHED
  TCP    192.168.0.119:49896    52.173.201.236:11703   TIME_WAIT
  TCP    192.168.0.119:49897    52.173.201.236:11703   TIME_WAIT
  TCP    192.168.0.119:49898    52.173.207.63:11701    ESTABLISHED
  TCP    192.168.0.119:49899    52.173.207.63:11701    TIME_WAIT
Does any one know what's going on? Can anyone help me?

 Dev - TCP sessions in TIME_WAIT mean that the session is closed but the port is being held for a short period to prevent another connection using that same port. 



@x2hawk said:

Just wanted to add to this topic that blocking the undesired data centers dramatically decreased my ping. Closest server to me here in Canada is US, Iowa. Before this fix, I was getting ~160ms ping, and after I am now getting ~70ms which is about what I would expect considering my distance to the data center and somewhat bad connection. So, this is definitely an unnecessary source of lag that the devs should look into! If you're having connection issues I would highly recommend you try this.

 This appears to only affect the datacenter selector page, in-game it doesn't appear to make a difference.

Blocking the other datacenters stops you seeing inflated pings however that being said, i feel that massive rubber-band lag that happens on the Australian server happens less.



@yakumo said:

13.124.126.150 - Korea
13.54.84.40 - Australia
34.211.139.167 - United States, Oregon, Portland
34.211.229.229 - United States, Oregon, Portland
52.79.231.250 - Korea
54.207.86.124 - Brazil, Sao Paulo
54.232.214.254 - Brazil, Sao Paulo
54.254.218.37 - Singapore
54.255.210.190 - Singapore
54.66.132.147 - Australia
52.173.131.28 - United States, Iowa
34.251.94.226 - Ireland, Dublin
52.49.163.0 - Ireland, Dublin
35.158.9.10 - Germany, Frankfurt
80.93.191.146 - Russia, St. Petersburg
These IP's can all be blocked if they're regions you don't wish to play in using the "Windows Firewall with Advanced Security" built into windows , right click 'Outbound Rules' and chose 'New rule...'. Chose 'Custom rule', then for Program Path  locate QuakeChampions.exe, leave it set to 'Any' protocol type,  all ports, then hit next and leave 'Any IP address' for the local address, then select 'These IP addresses' under the 'Remote Address' field and add the IP's one by one.

Edit:  Apparently some have found disabling flood protection on their own router has solve this issue for them, if you do that re-enable it once there is a fix patch out.

 Hello. You can find the address in Novosibirsk (Russia) servers?