Collected via Torch + whois during live sessions. Blocking these ranges prevents the client (PC/PS5 via router) from reaching Middle East servers and forces matchmaking to other regions. Note: some blocks are large AWS CIDRs and may affect unrelated services—scope to gaming devices if needed.
IP ranges to block
16.20.0.0/14
16.24.0.0/13
18.128.0.0/9
18.64.0.0/10
18.32.0.0/11
15.188.0.0/16
15.179.0.0/16
15.184.0.0/14
15.180.0.0/14
15.185.0.0/16
157.175.0.0/16
MikroTik (RouterOS) — fast, conn-track-friendly block
The rules below use an address-list and drop in /ip firewall raw (earliest stage).
Assumes you use interface lists named LAN and WAN. Rename as needed.
1) Create the address-list
/ip firewall address-list
add list=BF6-me address=16.20.0.0/14 comment="ME/AWS"
add list=BF6-me address=16.24.0.0/13 comment="ME/AWS"
add list=BF6-me address=18.128.0.0/9 comment="ME/AWS"
add list=BF6-me address=18.64.0.0/10 comment="ME/AWS"
add list=BF6-me address=18.32.0.0/11 comment="ME/AWS"
add list=BF6-me address=15.188.0.0/16 comment="ME/AWS"
add list=BF6-me address=15.179.0.0/16 comment="ME/AWS"
add list=BF6-me address=15.184.0.0/14 comment="ME/AWS"
add list=BF6-me address=15.180.0.0/14 comment="ME/AWS"
add list=BF6-me address=15.185.0.0/16 comment="ME/AWS"
add list=BF6-me address=157.175.0.0/16 comment="ME/AWS"
2) Drop traffic to/from those IPs (raw)
/ip firewall raw
# LAN → ME servers (outbound)
add chain=prerouting in-interface-list=LAN dst-address-list=BF6-me action=drop comment="BF ME block: outbound"
# ME servers → LAN (inbound)
add chain=prerouting in-interface-list=WAN src-address-list=BF6-me action=drop comment="BF ME block: inbound"
# Optional: move both rules to the top of raw
:delay 0.2
move [find where comment="BF ME block: inbound"] 0
move [find where comment="BF ME block: outbound"] 0
(Optional) Only target gaming devices
# Put your devices here (or use DHCP static leases)
# Example:
# /ip dhcp-server lease add address=192.168.88.50 mac-address=AA:BB:CC:DD:EE:FF comment="PS5"
# /ip dhcp-server lease add address=192.168.88.51 mac-address=11:22:33:44:55:66 comment="Gaming PC"
/ip firewall address-list
add list=gaming-clients address=192.168.88.50 comment="PS5"
add list=gaming-clients address=192.168.88.51 comment="Gaming PC"
# Replace the two raw rules above with these:
/ip firewall raw
add chain=prerouting src-address-list=gaming-clients dst-address-list=BF6-me in-interface-list=LAN action=drop comment="BF ME: outbound (gaming only)"
add chain=prerouting dst-address-list=gaming-clients src-address-list=BF6-me in-interface-list=WAN action=drop comment="BF ME: inbound (gaming only)"
Verify / monitor
/ip firewall raw print stats where comment~"BF ME"
- Restart the game after applying rules so matchmaking re-evaluates available regions.
- If you use IPv6, either add equivalent IPv6 drops (you’ll need the v6 ranges) or disable IPv6 on gaming devices.
Rollback (remove rules & list)
/ip firewall raw remove [find where comment~"BF ME"]
/ip firewall address-list remove [find where list="BF6-me"]
Windows — hosts file vs. firewall (what actually works)
Why the hosts file won’t reliably help
The Windows hosts file only maps hostnames → IPs. Game servers are contacted by IP (and change frequently). The hosts file cannot block raw IPs or entire CIDR ranges, so it won’t reliably stop connections to the addresses above.
What to use instead: Windows Defender Firewall (GUI)
- Open Windows Defender Firewall with Advanced Security.
- Outbound Rules → New Rule… → Custom
- Program: choose BF6.exe (bf6event.exe for the BETA version, or All programs to block system-wide).
- Protocol/Ports: Any.
- Scope → Remote IP addresses → These IP addresses → Add…
Paste the CIDRs above (one per line). - Action: Block the connection → apply to Domain/Private/Public.
- Name it (e.g., BF ME Block (Outbound)).
- (Optional) Repeat for Inbound Rule.
One-shot PowerShell (Run as Administrator)
$cidrs = @(
"16.20.0.0/14","16.24.0.0/13","18.128.0.0/9","18.64.0.0/10","18.32.0.0/11",
"15.188.0.0/16","15.179.0.0/16","15.184.0.0/14","15.180.0.0/14",
"15.185.0.0/16","157.175.0.0/16"
)
New-NetFirewallRule -DisplayName "BF ME Block (Outbound)" -Direction Outbound -Action Block -RemoteAddress ($cidrs -join ",") -Profile Any
New-NetFirewallRule -DisplayName "BF ME Block (Inbound)" -Direction Inbound -Action Block -RemoteAddress ($cidrs -join ",") -Profile Any
# Scope to the game only by adding: -Program "C:\\Path\\To\\BF6.exe"
Notes
- On consoles (PS5), apply the router method so every device behind it inherits the block.
- Large CIDRs may block unrelated AWS services; prefer the gaming-only scoping if that’s a concern.
- Keep an eye on new addresses as you discover them via Torch/whois; append to the BF6-me list.