[saxenaabhi]

Setting up a replica and then pointing your api requests at it when cloudflare request fails is trivial. This way if you have a SPA and as long as your site/app is open the users won't notice.

The issue is DNS since DNS propagation takes time. Does anyone have any ideas here?

[viraptor]

> Setting up a replica and then pointing your api requests at it when cloudflare request fails is trivial.

Only if you're doing very basic proxy stuff. If you stack multiple features and maybe even start using workers, there may be no 1:1 alternatives to switch to. And definitely not trivially.

[saxenaabhi]

We do use workers, but with hono so it's easy to deploy it on render with node.

There are other cloudflare products for which there are not many alternative(durable objects, workflows etc), but at least for us we don't use them in the critical path. We deliberately avoided them in the critical path because we knew we'll have to setup multi cloud for 99.999% uptime(we run a POS system so any downtime results in angry calls and long lines for our merchants)

[isodev]

Two domains for your api perhaps, a full blown SPA could try one and then the other.

[saxenaabhi]

Yes, that's my approach as well. Issue is when users opens the app during downtime or hit reload. Primary domain would return a 5xx.

[tambre]

Owning your IP space and using Anycast.

[tempaccount420]

Anycast is hard, which is why only clouds bother with it in the first place :(