0

anycast2 (45.90.30.0) from Shaw/Vancouver lands on zepto-iad (~72ms) despite zepto-sea at 23ms

ISP: Shaw Communications (Rogers), AS6327, Vancouver, BC Diag: https://nextdns.io/diag/21271bf0-e1fe-11f1-99cf-ef3c66372b14

Anycast secondary (45.90.30.0) reaches zepto-iad at ~72 ms. Every other endpoint is local:

45.90.28.0 (anycast primary)    vultr-sea     17 ms
ultra low latency primary       cacloud-yvr   21 ms
ultra low latency secondary     anexia-yvr    23-31 ms
45.90.30.0 (anycast secondary)  zepto-iad     72 ms

zepto-sea pings at 23 ms from here, so anycast2 seems to be taking a bad route from AS6327. In the traceroute the traffic leaves Shaw at 66.163.64.81 (~17 ms), and the next response is from 206.148.25.116 at ~66 ms. I saw the same result repeatedly over several hours on 2026-11-16.

Why it matters: Tailscale's NextDNS integration uses 45.90.28.0 and 45.90.30.0 as fixed DoH endpoints and falls back to anycast2 when anycast1 is slow to connect. When it lands on zepto-iad, CDNs answer for Ashburn. Steam's Akamai and Fastly hosts resolve to nodes ~80 ms away instead of ~17 ms.

Could anycast2 from AS6327 be steered to a West Coast PoP (zepto-sea or one of the yvr PoPs)?

Reply

null

Content aside

  • 3 hrs agoLast active
  • 3Views
  • 1 Following