Comment by saxenaabhi
6 hours ago
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?
> 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.
Two domains for your api perhaps, a full blown SPA could try one and then the other.
Owning your IP space and using Anycast.
Anycast is hard, which is why only clouds bother with it in the first place :(