TetraGG四面体电竞

// Technical guide · OCE servers

Why your OCE Valorant ping is what it is — and what you can do

A no-nonsense look at how Riot routes OCE traffic, what ping ranges Australian and New Zealand players can realistically expect, which ISP/router/VPN tweaks help, and which are myths. Written by boosters who play these servers 6+ hours a day.

No fabricated numbers · ranges onlyMethodology disclosed belowUpdated 2026

The three servers that matter for OCE players

Riot doesn't publish exact datacenter locations or IPs, and both change over time as peering contracts shift. What we consistently see across our booster pool:

Sydney · Primary

The anchor of OCE. The overwhelming majority of ranked Australian games route here. If you live in Sydney metro you're basically on the doorstep; everyone else on the east coast routes in via Sydney.

Melbourne · Secondary

Used in some peering arrangements and occasionally as a Premier mode fallback. Don't assume Melbourne players automatically connect locally — your traffic may still hairpin through Sydney first depending on ISP.

Singapore · SEA fallback

When OCE population is low (late nights, early mornings) or you queue Premier mode, Riot can route you via SEA. Perth players often see better numbers here than to Sydney — the geography wins.

Practical takeaway: don't hardcode any datacenter assumption into your setup. Use the in-client server picker and confirm the green-tick server before locking in ranked.

Typical OCE ping by Australian/New Zealand city

What we observe across our booster roster and 1,200+ orders. All values are ranges — your mileage depends on ISP, NBN tier, time of day and current Riot peering.

City / regionOCE ping (typical)Notes
Sydney (metro)5-15 msClosest to primary OCE peering; most stable.
Newcastle / Wollongong10-20 msWithin NSW backbone; very playable.
Canberra15-25 msRouted via Sydney; rarely an issue.
Melbourne15-25 msSydney-routed; varies by ISP peering choices.
Brisbane20-30 msComfortable for ranked; rare spikes during peak.
Gold Coast22-32 msSimilar to Brisbane.
Adelaide30-40 msLonger haul; still playable for Immortal-level aim.
Hobart40-55 msSubsea cable to mainland adds latency.
Darwin50-70 msLimited backhaul; some ISPs route via SEA.
Perth50-80 msFar side of continent — SEA server is often the better pick.
Auckland (NZ)30-45 msTrans-Tasman cable; reasonable for OCE.
Wellington (NZ)35-50 msSimilar to Auckland; depends on Spark/Vodafone routing.
Christchurch (NZ)40-55 msSouth Island adds a hop.

Methodology & caveat

These ranges are aggregated from TetraGG's active booster pool across 2024-2026, sampled across NBN, 5G HFC, and university residence networks. They are not lab benchmarks. Your actual ping depends on your ISP's peering choices, your NBN technology tier (FTTP vs FTTN vs HFC vs FW), congestion at your local exchange, and Riot's current routing — all of which shift over time. Always verify against your own measurement (in-client ping, ping against a known Riot edge, or a tool like PingPlotter) before treating these as personal ground truth.

How your ISP and NBN tier change the picture

Two players on the same street, same suburb, can see meaningfully different OCE ping. The differences come from three layers stacked on top of physical distance:

ISP backbone & peering

Telstra tends to have the most consistent baseline routing — not always the shortest, but rarely surprising. Aussie Broadband and Superloop advertise gaming-friendly peering and frequently show cleaner traceroutes to OCE. TPG / iiNet routing varies by region, sometimes excellent in Sydney/Melbourne and less so in regional areas. Optus is solid on the east coast but occasionally takes longer paths during peering renegotiations. The honest rule: peering quality is a moving target, not a permanent property of the brand.

NBN technology tier

FTTP (fibre-to-the-premises) gives the lowest and most stable last-mile latency. FTTC / HFC are generally fine but can show jitter under load. FTTN (fibre-to-the-node) is where most ping complaints live — the copper run from node to home introduces noticeable variance, and long node distances make it worse. Fixed Wireless and Satellite add their own delay layer; competitive Valorant is hard on these unless you're close to the tower.

If you're shopping: ask the prospective ISP for a Sydney traceroute sample before committing. Any honest residential ISP can run one from a nearby PoP.

The actual checklist that lowers ping

In rough order of how much they help, free first:

  1. 01

    Use ethernet, not Wi-Fi

    Single biggest free upgrade. Wi-Fi can match ethernet on average ping but loses on jitter, and jitter is what kills clutches. Run a cable — even a flat 10m one along the skirting beats wireless.

  2. 02

    Close everything else before queuing ranked

    Chrome with 30 tabs, OBS recording at 1080p60, Discord screen-share, Spotify, Steam download — each adds CPU pressure and (more importantly) competes for upstream bandwidth. Stream/record after the climb session, not during.

  3. 03

    Verify your server selection in the Riot client

    Open the server picker before the queue, confirm OCE shows green (or SEA if you're in Perth), and don't queue if the latency reading is unusually high — that's Riot telling you something is wrong with the route right now.

  4. 04

    Disable Vanguard background scans during play

    Vanguard itself stays on, but its scheduled background scans can spike CPU and disk I/O. Schedule scans for outside your usual play hours via Windows Task Scheduler.

  5. 05

    Restart your modem/router weekly

    ISP-issued routers leak memory over weeks. A weekly power-cycle clears the NAT table and re-establishes a fresh BGP-influenced path. Free, takes 60 seconds.

  6. 06

    Test routing optimisers honestly before paying

    ExitLag, NoPing and similar tools work for some routes and hurt others. Use the free trial, compare in-game ping with and without across 5+ matches, and only pay if you see a real, consistent improvement of 5ms+. Don't subscribe because someone on Reddit said it helped them.

  7. 07

    If you're on FTTN and serious, look into FTTP upgrade

    NBN's FTTP-on-demand program can convert FTTN homes for a one-off cost. Not cheap, but if you're spending 4+ hours a day in ranked the latency stability is real.

  8. 08

    Stop trying to use a VPN to lower ping

    VPNs add a hop. On a clean Sydney→Sydney route they will never beat your ISP's default path. They're only useful if you can prove with traceroute that your ISP is misrouting — and that's rare.

When TetraGG can actually help

Lower ping is a hardware/ISP problem. Winning more games on the ping you already have is a gameplay problem. We do the second:

FAQ — OCE servers & ping

Why is OCE Valorant ping higher than NA or KR ping I see on streamers?
Two reasons. (1) Population density — OCE serves ~25M people across AU/NZ, NA serves ~370M and KR has ~50M on a single landmass with dense fibre. Riot puts physical infrastructure where the playerbase justifies it, so OCE has fewer datacenters. (2) Geography — light still has to travel through fibre, and Australia is huge. Even the best routing can't get a Perth player below ~50ms to an east-coast server. Sub-10ms is mostly a Sydney-metro privilege.
Will a VPN lower my Valorant ping on OCE?
Almost always no — and usually worse. VPN adds a hop and an encryption layer, which adds latency, not removes it. The only edge case where a VPN helps is when your ISP is routing oddly (e.g. some Perth ISPs send Valorant traffic via Singapore even when OCE would be shorter), and a well-chosen VPN exit forces a saner path. Test with `tracert` before and after. If your route already goes Sydney→Sydney, a VPN cannot beat physics.
Is Optus, Telstra, TPG or Aussie Broadband better for Valorant?
There is no universal winner — peering changes quarterly. As a pattern, Aussie Broadband and Superloop tend to have cleaner gaming-oriented routing, Telstra has the most consistent backbone but isn't always the lowest hop count, and budget ISPs (some TPG resellers, Dodo) occasionally route through Singapore in odd hours. The honest test is your own `tracert valorant.servers.riotcdn.net` — that tells you more than any forum poll.
Do I need a gaming router to lower my OCE ping?
Not for latency to Riot. A gaming router does not change the path your packets take across the public internet. Where it does help: local Wi-Fi jitter, QoS when your housemate streams 4K, and tighter buffer management. If you're already wired with ethernet and your housemates aren't saturating the line, a gaming router will not lower your in-game ping.
Why does my ping sometimes spike to 80ms+ in OCE for one game then go back to 20ms?
Most often it's not the server — it's a server selection issue (you got matched to SEA because of a Premier flag, party leader region, or a low-population time window) or an ISP route flap (your ISP's BGP path changed mid-match). Check the in-game scoreboard during the spike — if the lobby shows other Australian players at 90ms too, it's the server; if only you're high, it's your local link.
Is wired ethernet actually that much better than Wi-Fi for Valorant?
For raw ping average, on modern Wi-Fi 6 with a strong signal, the difference can be small (~1-3ms). The real win is jitter and packet loss. Wi-Fi has higher variance — your ping graph looks like a heartbeat instead of a flat line, and in clutch 1v1s that variance is what costs trades. Ethernet for ranked is the easiest free upgrade in the game.
Should I use ExitLag, NoPing or similar routing optimizers?
They work for some players on some routes, and not at all for others. The mechanism is real — they own private peering paths that can be shorter than your ISP's default. But on a clean OCE Sydney route they often add latency rather than removing it. Use the free trial, compare honestly with `tracert`, and only pay if you see a consistent 5ms+ improvement. We don't endorse any specific provider.
Does the Riot server selection in client always pick the lowest-ping option?
Usually, but not always. Riot picks based on a mix of your measured ping, population, and party leader's region. If your duo is on a different ISP whose ping to OCE is worse, you may end up on SEA together. Manually check the server list before queueing for ranked, and if your duo's home server differs from yours, the party leader's region usually wins.

Stuck on the same rank despite decent ping?

That's a gameplay problem, not a network problem. Jump into our Discord for a free 10-minute VOD look, or book a paid coach if you want the full breakdown.