When I first saw the page (opened along with a bunch of other tabs from HN links), with its "Timeout error!" balloon and "Service disruption" headline, I thought it was a fancy error page and hit reload. Oops.
Doesn't every CDN already accomplish the same functionality with multiple origins and failover detection, while accelerating static content by caching it at the edge? Given how cost competitive CDNs already are, I don't see how they can charge a low enough cost in comparison to be compelling, while still incurring bandwidth costs and at least some network infrastructure which make it almost as expensive to run, minus some caching nodes. And if for whatever reason, there does happen to be some use case for anycasting the IP that's advantageous, any CDN could add this feature overnight while having a much more established footprint and infrastructure in place.
> If your application goes down, all you want is to get it back up. What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses.
I think the idea is that datapath only functions when you go down. ie: if only you go down, datapath will fix it via BGP magic. If datapath is down and you are up, stuff continues to work.
In general, most ISPs will drop any routes more specific than a /24. Presumably datapath has negotiated with some specific providers to allow /32s; it's up to that ISP to scale their routers to handle it; other ISPs will only see the /24 aggregate.
> What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses.
Call me crazy, but I'm not sure I really care about keeping my IPs. Route 53 seems as close to bulletproof as we're going to find with DNS, and it's got cloud-independent failover routing built in. Point the primary record at your nice little EC2 server, and have the secondary record pointing as Azure or Google Cloud or your mom's laptop, whatever, and it'll do what Datapath is doing without futzing with your routing. ...right?
Id adds one hop (our appliance) to the path. It tries to increase performance of your path by taking non-standard BGP metrics into account: congestion and latency
Traffic passes the appliance at the edge of the hosting provider. It takes congestion at all links and the appliance itself into account and re-routes accordingly.
Depending on the characteristics of the location, at least three very unsimilar transit connections are used.
The "vague bullshit in between cute animations" approach really doesn't work at all for this type of product.