4/5 cdnjs.cloudflare.com hosts hang when accessed from cloud browser


#1

I work for Authentic8, Inc, which provides a cloud-based browser called Silo.

Since we have a large number of servers in the cloud, we do on occasion have sites that block our traffic (thinking we may be a bot or whatnot), and we do have ways to deal with this. The cdnjs issue is much more of a problem for us because cdnjs is causing various host sites to hang without an error message.

Specifically this recently came up while attempting to log into jira.com. About four out of five times the login page hangs while attempting to load https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.5/require.min.js.

Attempting to load this resource from my app server with wget, I get a list of five servers, one of which works and the others all time out.

$ wget https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.5/require.min.js
–2018-02-26 22:20:32-- https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.5/require.min.js
Resolving cdnjs.cloudflare.com (cdnjs.cloudflare.com)… 104.19.195.102, 104.19.192.102, 104.19.193.102, …
Connecting to cdnjs.cloudflare.com (cdnjs.cloudflare.com)|104.19.195.102|:443… failed: Connection timed out.
Connecting to cdnjs.cloudflare.com (cdnjs.cloudflare.com)|104.19.192.102|:443… failed: Connection timed out.
Connecting to cdnjs.cloudflare.com (cdnjs.cloudflare.com)|104.19.193.102|:443… failed: Connection timed out.
Connecting to cdnjs.cloudflare.com (cdnjs.cloudflare.com)|104.19.196.102|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: unspecified [application/javascript]
Saving to: ‘require.min.js’

Same result with multiple requests, and to different resources show that 104.19.196.102 is the only one of the five dns entries that works from that environment. Who can I talk to about the configuration for this service (I tried posting on cdnjs’s github acct, and they say they don’t handle the cloudflare configuration).

Thanks,

-Adam


#2

Doing some checking on this. Are you still seeing the same behavior?


#3

Yes, exact same behavior. This has been going on for a couple of weeks give or take. Thanks


#4

The failing servers are stopping at 218.30.44.121, the successful server makes it by this ip.


#5

This is back to normal for me today on my app server, I’m going to verify from some of the other servers.


#6

This topic was automatically closed after 14 days. New replies are no longer allowed.