Anycast vs. DNS geo-routing: a Tokyo SaaS chases 30ms
A dashboard product had users split between Tokyo and Frankfurt. They used DNS geo-routing — resolver location decided the PoP. Trouble was, half their Japanese users sat behind a corporate resolver in Singapore, so they got routed 5,300 km the wrong way.
Frankfurt-resolved Tokyo users saw 180ms TTFB on an app that needed sub-60ms.
They moved the front to an anycast network where the same IP is announced everywhere and BGP picks the nearest PoP by network topology, not resolver guesswork.
Tokyo TTFB fell from 180ms to 28ms. Frankfurt held at 34ms. Misrouted sessions went to near zero.
DNS routing wins when you need per-user logic or sticky regions. Anycast wins when raw nearest-PoP latency is the whole game.
The number that mattered: 28ms TTFB in Tokyo.
Edge of Glory
@EdgeOfGloryCDN
Anycast vs. DNS geo-routing: a Tokyo SaaS chases 30ms
Этот пост опубликован в Telegram-канале Edge of Glory. Подписаться можно по ссылке: @EdgeOfGloryCDN.