Unresponsive Servers

These servers have sent a heartbeat but have failed to respond to an appropriate query from a different port. This can happen when:

Server is firewalled and all inbound packets are dropped. Try reconfiguring your firewall to allow packets to that process or port.
An intermediate router implements an Address/Port-Dependant-Filtering NAT. Try setting up port forwarding.
Outgoing connections are asynchronous with regard to port forwarding. Such servers will show with arbitrary ephemerial ports. Docker: you can supposedly work around this with --net=host.
Plain and simple packet loss, servers in this state for less than 5 mins may still be fine.
Server crashed or was reconfigured before it could respond.
MTU limits with failed defragmentation.
Routing table misconfiguration.
Other.

Address	Hostname	Gamedir	Mapname	Players
3.234.52.82:27910	🚫			0/0
3.234.52.82:27911	🚫			0/0
3.234.52.82:27912	🚫			0/0
23.227.170.222:26666	🚫			0/0
74.131.247.218:27910	🚫			0/0
76.139.128.93:6969	🚫			0/0
207.127.95.141:27901	🚫			0/0
217.67.129.82:34383	🚫			0/0
217.67.129.82:52158	🚫			0/0
217.67.129.82:2489	🚫			0/0
217.67.129.82:12334	🚫			0/0
167.71.33.1:27599	🚫FTEQTV	QTV	QTV	0/0
136.33.93.40:26000	🚫🚸Family	ad	start	0/4
54.177.148.230:27505	🚫🔒FortressOne California Scrim	fortress	2fort5r	0/24
54.177.148.230:27504	🚫🔒FortressOne California Tourney	fortress	2fort5r	0/24
35.178.200.80:27505	🚫🔒FortressOne London Scrim	fortress	2fort5r	0/24
35.178.200.80:27504	🚫🔒FortressOne London Tourney	fortress	2fort5r	0/24
13.48.133.81:27505	🚫🔒FortressOne Stockholm Scrim	fortress	2fort5r	0/24
13.48.133.81:27504	🚫🔒FortressOne Stockholm Tourney	fortress	2fort5r	0/24
104.171.240.7:41890	🛡unnamed	id1	start	0/8
104.171.240.7:54174	🛡unnamed	id1	start	0/8
104.171.240.7:54600	🛡unnamed	id1	start	0/8
104.171.240.7:10389	🛡unnamed	id1	start	0/8
177.142.208.227:27500	🚫unnamed	fortress	start	0/24

24 servers