URLs have stopped loading
URLs have stopped loading
JamesDaniels
Posts: 3Questions: 1Answers: 0
Link to test case:
Debugger code (debug.datatables.net):
Error messages shown:
This site can’t be reached
Description of problem:
The incident here suggests the matter has been resolved:
https://status.datatables.net/incidents/304991
But several members of my organisation can't access several URLs, eg: https://cdn.datatables.net/1.10.12/css/jquery.dataTables.min.css
I can however access this: https://datatables-cdn.com/1.10.12/css/jquery.dataTables.min.css - as suggested in the incident page.
Answers
DNS-Propagation can be very slow due to caching etc. (see the other threads on this topic for more details).
I am staying with datatables-cdn.com for a couple of more days and then revert back to cdn.datatables.net to be on the safe side.
Its almost certainly HTTP caching that is causing the issue now. Try adding
?2025-07-30or something to the URL for the CSS / JS to have it "bust" the cache. The server is responding correctly and I can access the files indicated on all of the networks I have access to. A force refresh (ctrl - f5) might help as well.Allan
Thanks for your quick response Allan and rf1234.
The page I'm loading (I'm afraid it isn't public for me to share) still has the the errors.
I've tried force refreshing, clearing browser cache, disabling cache, etc. Still the same problem.
I've tried pasting the URL directly into my Chrome address bar:
https://cdn.datatables.net/1.10.12/css/jquery.dataTables.min.css
I get the "This site can’t be reached" page
Same situation with your query suggestion:
https://cdn.datatables.net/1.10.12/css/jquery.dataTables.min.css?2025-07-30
This only started happening this morning for me and I'm not aware of it ever happening before.
Both links work for me. Try Allan's last answer in this thread.
Kevin
I tried lots of things (as suggested above and in links), but I think what finally worked for me was going to chrome://net-internals/#dns and entering:
cdn.datatables.net
Then clicking "Clear host cache"
Thanks for this, James!
Tried this in Edge
edge://net-internals/#dns
and it worked as well.
(Probably because both browsers are Chromium based)
In Firefox this should work
about:networking#dns
Roland
My word - that seems bonkers to me. Thank you for sharing that info with us @JamesDaniels. The TTL on cdn.datatables.net's DNS is 300 seconds. This problem should have cleared 5 minutes after the domain was restored! Plenty of routers and it seems browsers(!) appear to think they know better...
If anyone is interested, I've written up what happened.
Allan
I have tried the same and it's still not working.. Adapter DNS cache cleared and browser DNS cache cleared. Users in the South East US seem to still be having an issue. When they make a request to cdn.datatables.com they get a (502) and when I make the same request I get (200) using the same address (104.26.8.123). Any other reports of regional issues? Nobody else is affected outside these regions.
Any remaining problems should be very localised now. I wouldn't expect entire geographical regions to have problems.
The TTL for the subdomain (cdn.datatables.net) is set to 300 seconds. All routers and DNS cache should obay that, and certainly those near the top of the tree absolutely do (set your DNS resolvers to 8.8.8.8 and 8.8.4.4 and the CDN will resolve no issue). It appears some routers are ignoring the TTL. It is possible that some might have some kind of timer and on each request to that domain it restarts the timer, and it won't refresh until the timer expires. So continually refreshing just makes the problem last longer!
From a network that is still having problems, try
dig cdn.datatables.net. It will show what resolver is being used and how it gets resolved. That resolver, if it is showing anything other than a CloudFlare IP, is wrong and needs to be flushed.One small note, which was probably a typo:
Should be cdn.datatables.net.
Allan
Yes, typo... I did it several times today. Thanks
Thanks Allan. Tried it myself and got three IP addresses from the dig tool. All of those were Cloudflare IPs (Just copied them in the browser and got error messages of course, and those messages were from Cloudflare).
I used digwebinterface.com
It seems the original CDN (https://cdn.datatables.net) is still having issues for some users, even though the incident is marked as resolved. Switching to the new URL (https://datatables-cdn.com) is a good workaround for now.
edited by admin - removed what appears to be a spam link, but not 100% certain...