jimaek

Based on the output it seems like the service is working fine and its not banned.
The screenshot is very small but it looks like the problem is not even jsDelivr? Could you press on that failed request and screenshot the whole thing with the details it offers as well?

I assume you use windows? Can you open your command line and do the following?

ping cdn.jsdelivr.net

nslookup cdn.jsdelivr.net

And send me the output. Thank you

Hey, jsDelivr team here.
We are not aware of being blocked in any countries. But we do get some reports of people using misconfigured firewalls in their networks that accidentally block cdn.jsdelivr.net.
They always fix the issue and continuing using us without problems.

I would appreciate more information about this issue.
What country are you in. What is the output when pinging cdn.jsdelivr.net. What is the output when doing dig cdn.jsdelivr.net

Thanks

Can you anyone provide some more information?
For example the HTTP headers of the slow request for that file.
Also your location would be helpful as well.

They renamed their project. This is the latest now https://www.jsdelivr.com/package/npm/@fortawesome/fontawesome-free

Hey all, I am from the jsDelivr team. I am really sorry about the issues our API had.
It was related to our Redis instance running out of RAM. Only our API was impacted, and only partially for un-cached URLs. So the outage was fairly limited. The CDN itself had no issues at all!

I wanted to let you know what we plan to take precautions and avoid this kind of problems in the future. We take this kind of issues very seriously and plan to make our API backend even more reliable.

But I also wanted to let you know that while our CDN at cdn.jsdelivr.net has multiple failover strategies and uses multiple providers, our API does not share the same infrastructure. Ideally applications using it should have a failover logic to ensure an API timeout does not break anything. For example cache API responses and re-use the cache if the API is having issues. This applies for all APIs in general.

Regardless we will be making sure you nothing similar will happen ever again!

I am really sorry for the inconvenience this caused everyone

Next to “Save all settings” there is a dropdown. You can select “Enabled” and save the settings.
It should solve your problem.

You need to raise your PHP memory value.

You need to increase your PHP memory https://docs.woothemes.com/document/increasing-the-wordpress-memory-limit/

I see. Unfortunately not, we are trying to get as much information we can to fix all existing bugs.

I guess I can close this issue then

Thanks

https://support.godaddy.com/help/article/1197/working-with-error-logs

If you are on a shared hosting the logs should be in your cPanel.
Cant help unless I know more about your hosting.

Can you provide any logs?

Can you provide any logs?

1. This is not related to jsDelivr Plugin. This is W3 Total Cache error
2. You need to raise your PHP RAM limit.