In HTML/CSS you should be able to specify a fallback source if the first returns a non-200.
Or that companies need to have better DNS strategies.
> In HTML/CSS you should be able to specify a fallback source if the first returns a non-200.
Except if the HTML/CSS is hosted on that CDN?
Web Browsers should probably retry a different server in DNS if they get a 503 - but they don't.
Content-centric networking had been a central research topic for many years. And many potentially useful systems have been proposed and implemented.
At some point some of them will start to become popular.
DNS didn't fail, and there's nothing you can do in HTML/CS/JS if your CDN fails to serve those things
That sometimes they fail but the world goes on.
we had that experience when cloudfare was down for sometime lastyear. We now setup a minor own static server as a backup, if at all this happens again. Althgh we hadn't so far had to use it.