Service provider story about tracking down TCP RSTs

William Herrin bill at
Sat Sep 1 20:00:36 UTC 2018

On Sat, Sep 1, 2018 at 2:51 PM,  <frnkblk at> wrote:
> pointing out that a
> single traceroute to a Fastly site was hitting two of their POPs (they use
> anycast) and because they don’t sync state between POPs the second POP would
> naturally issue a TCP RST (sidebar: fascinating blog article on Fastly’s
> infrastructure here:

Oh for Pete's sake. If they're going to attempt Anycast TCP with a
unicast protocol stack they should at least have the sense to suppress
the RSTs.

Better yet, do the job right and build an anycast TCP stack as
described here:

Bill Herrin

William Herrin ................ herrin at  bill at
Dirtside Systems ......... Web: <>

More information about the NANOG mailing list