The only downside is you cannot do BGP on those IPv6-only hosts, as their BGP speaker is IPv4-only, so you cannot BYOIPv4 to those hosts, unless you route via their private network to another IPv4 enabled host first.
Oh, I wasn't even aware that was a thing. How does that work? Don't you have to buy blocks of IPv4 (which would be rather expensive) and then route them all the the Host. What advantage would Bringing your own IP have anyway?
> If you want some serious redundancy nothing beats running services anycast with BGP across multiple cloud providers.
Unless they're TCP services. Or stateful UDP services. Then you're in for a world of pain if you try to anycast them.
The list of sensibly anycast services is surprisingly low. Stateless UDP services, essentially, which isn't a big list. Especially if you're the kind of person who's using Vultr's cloud, and not a megacorp.
If you have the resources to develop backend state sync, you're probably still better serviced with a (set of) load balancer(s).
No way. Stateful TCP over anycast works fine reliably to many nines.
I run a CDN with anycast BGP, this obviously uses TCP. Works great. I've also done it with a global network of physical datacenters and our own transit/peering network but eventually migated to the cloud for reasons.
This is absolutely awesome. I'm not sure if you're a maintainer of this list, but, this is VERY useful. You just found me a provider who is scratching an itch for a specific niche location which I've had for years. I owe you a beer or three.
