Network routing information and ISP optimization guide for Valorant servers
Network information for Valorant game servers in the Asia Pacific region
Last Update: 2026-02-01
Most Valorant Asia Pacific servers use AWS Global Accelerator with anycast IP addresses, announced under AS16509 (Amazon's ASN). This makes Valorant traffic indistinguishable from regular AWS/Amazon traffic at the BGP level.
References:
# Riot Direct (SG)
151.106.248.1
# AWS Global Accelerator (SG)
13.248.193.101
75.2.69.178
76.223.1.250
99.83.157.116
Routing Recommendation: Use 151.106.248.0/24 for Singapore routing rules
# Personally Tested (PT)
151.106.246.1/32
# Additional IPs (reported by Riot Support)
99.83.136.104
75.2.66.166
13.248.197.71
76.223.71.164
151.106.246.32
Routing Recommendation: Use 151.106.246.0/24 for Mumbai routing rules
Valorant uses the following ports for gameplay:
| Protocol | Port Range |
|---|---|
| UDP | 7000-8000 |
| UDP | 8180-8181 |
| TCP/UDP | 8088 |
13.248.193.101
13.248.197.71
13.248.205.128
13.248.220.97
151.106.248.1
43.229.65.1
75.2.49.107
75.2.66.166
75.2.69.178
76.223.1.250
76.223.71.142
76.223.71.164
76.223.72.224
99.83.136.104
99.83.157.116
99.83.187.195
Valorant traffic uses AWS Global Accelerator (AS16509), making it indistinguishable from regular AWS traffic. Since BGP cannot filter at the port level, optimizing routing for gaming traffic requires special configuration.
Increase BGP preferences for Amazon routes via Equinix or SGIX Singapore peering points. This forces Amazon to prioritize your direct IXP connection over ITC (International Transit) peers like Airtel/Tata.
Implementation:
- Reference: AWS Direct Connect Routing & BGP Communities
- BGP Community Tag:
7224:7200(Medium local preference) - Alternative:
7224:7300(High preference for primary paths)
Allocate one or more /24 subnets exclusively for gaming/latency-sensitive customers. Do not announce these blocks to Airtel/Tata/ITC transit peers—only advertise via direct peering or high-quality upstream providers.
Benefits:
- Guarantees traffic avoids congested ITC peers
- Provides consistent low-latency paths
- Easier to troubleshoot and monitor
Configure routing to prefer SMW4 (SEA-ME-WE 4) or SMW5 (SEA-ME-WE 5) submarine cable systems for AS16509 traffic between India and Singapore.
Why this matters:
- Direct undersea fiber provides lower latency than terrestrial routes
- More stable than multi-hop ITC peer paths
- Reduces packet loss and jitter
Implementation:
- Set path preferences in BGP to favor routes transiting SMW4/5
- Coordinate with your upstream provider if you don't have direct submarine cable access
- Monitor latency to Singapore AWS edge locations (13.248.193.101, 151.106.248.1)
Most Valorant server IPs will NOT respond to ping (ICMP) requests. This is intentional for security and DDoS protection. A timeout does NOT mean the server is down or unreachable.
What works:
- ✅ In-game latency monitoring (Alt+F for network stats)
- ✅ Traceroute to identify routing path (even if final hop times out)
- ✅ Monitoring connection quality during actual gameplay
What doesn't work:
- ❌
pingcommand (will timeout even when server is working) - ❌ ICMP-based monitoring tools
- ❌ Most online "ping test" websites
Even though ping may not work, you can still trace the route your traffic takes:
Windows (Command Prompt):
tracert -d 151.106.246.1Linux/macOS (Terminal):
traceroute -n 151.106.246.1
# or
mtr --no-dns 151.106.246.1What to look for:
- Number of hops (fewer is better)
- Latency increase at each hop
- Whether traffic goes through Airtel/Tata or direct AWS paths
- Submarine cable exits (look for Singapore/Chennai hops)
If you're experiencing routing issues, you can use VPN split tunneling to route only Valorant traffic through a better path:
- Use a VPN that supports split tunneling (WireGuard, OpenVPN)
- Exclude Riot Client and Vanguard from VPN
- Route only game traffic (IPs listed above) through VPN
- Test with servers closest to your location
Mumbai example:
151.106.246.0/24
Singapore example:
151.106.248.0/24
Have updated IP addresses or routing improvements? Please open an issue or pull request!
When submitting new IPs, please include:
- Source: Riot Support ticket, network capture, community report
- Date discovered: When you found/verified the IP
- Method of verification:
- Network packet capture (Wireshark/tcpdump) during gameplay
- Traceroute showing AS16509 path
- Riot Support confirmation
- Resource monitor during active game
- Your geographic location: City, ISP name
Tools for verification:
- Windows: Resource Monitor → Network tab (filter Valorant processes)
- Wireshark: Filter by UDP ports 7000-8000, 8180-8181
- TCPView (Windows): Real-time connection monitoring
- netstat/ss (Linux): Active connection listing
- AWS Global Accelerator Documentation
- AWS Direct Connect BGP Communities
- Riot Games Network Status
- PeeringDB - AS16509 (Amazon)
- SEA-ME-WE 4 Cable System
- SEA-ME-WE 5 Cable System
This information is provided as-is for educational and network optimization purposes. Use at your own discretion.
This is an unofficial resource maintained by me personally. Riot Games and Amazon Web Services are not affiliated with this project.
Based on my fact-checking:
Verified:
- AS16509 is Amazon's ASN
- AWS Global Accelerator uses anycast IPs
- BGP community
7224:7200is valid for medium preference - UDP ports 7000-8000, 8180-8181, TCP/UDP 8088 are correct
- Mumbai IP: 151.106.246.1/32 confirmed by multiple Riot support tickets
- Singapore IP: 151.106.248.1/32 confirmed by multiple sources
- SMW4/5 submarine cables connect India-Singapore
Partially verified:
- Most IPs in the list appear in community reports but not all have official confirmation
- Some IPs (like 75.2.66.166, 99.83.136.104) were provided by Riot support to users