Embed Notice

@erincandescent @disarray Well, that's the thing.
You can't do traffic engineering with them at all.

That might not matter if you just have one single location, but as soon as you have multiple and wanna do something like anycast or something, HE is such a pain because they just run one dumb, flat network worldwide.
No communities, no geo balancing no noting.

Lets say I have a PoP in DE and one in US.
Both with a tier 2 transit.

I do peer with He.net in DE.
Now all the US traffic flows to DE, because HE thinks this is the best route.

Now lets say your transit in US is buying transit form HE.net.
Now all the traffic, including the one form DE is going to the US.
You might think traffic form DE should go via your DE peering, because this is obviously the shorter way, geographically and also virtually (AS path), but transit routes have a lower metric in the HE network, so the route HE.net learned in the US has a higher priority, even in DE, where you peer with them.

Soo.. the only way to do "traffic engineering" (if you wanna call it that) with them is either by peer with them at all location you are present, no exceptions, or by avoiding exporting any route to them as a transit route (directly or trough your transits) so HE.net is forced to route via a different tier1 which allows you to do proper traffic engineering, via for example action communities.