Problem accessing Cloudflare


#1

Hello guys.
I’m getting a timeout when accessing Cloudflare in an India’s region. Accessing a S3 bucket directly that is behind the Cloudflare work as expected but accessing it from the Cloudflare does not work.

The public IP Address where I am trying to access is 219.91.150.84

What do you think that might be the problem?
I’ve submitted a request in the Cloudflare support but It has been 6 days without any answer… The ticket number is #1627555

Thank you for the help


#2

What kind of timeout? Can you post a screenshot and the associated domain?


#3

The timeout is really a timeout using Curl and accessing the Cloudflare url.

For example accessing https://static.amp.services/test-support-cloudflare.html returns a timeout but accessing directly the S3 bucket work as expected https://s3-eu-west-1.amazonaws.com/static.amp.services/test-support-cloudflare.html

The nslookup that I’ve run gave me this:

nslookup static.amp.services
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
Name: static.amp.services
Addresses: 2606:4700:30::6812:2cb4
2606:4700:30::6812:2db4
104.18.45.180
104.18.44.180

What do you think can be the problem?


#4

The problem is when I’m accessing from the following IP Address based in India: 219.91.150.84


#5

Can you post the exact output you receive from the cURL command? If it is a real timeout there might be a network issue. If it is a “Cloudflare timeout”, you can reach Cloudflare but they cant reach your AWS instance for some reason.


#6

I’m also facing problem accessing cloudflare. 502 Bad Gateway is coming even while I try to access cloudflare community.


#7

we are also facing same issue with our websites hosted on Azure.
its giving 502-Bad Gateway error from cloudflare.


#8

It works for me.
https://static.amp.services/test-support-cloudflare.html

The others that are having issues it might help to know where you are accessing from.


#9

It is a real timeout. Also, doing a GET request in the browser to both addresses: the S3 bucket works but the Cloudflare one never answers back. Trying to get the cURL command output @sandro but I think the IP address must be blocked somehow by Cloudflare.


Here @corey1 the location.


#10

Browser? I thought you are talking about a CLI call, where there is presumably no browser.

You need to provide the requested details, otherwise it is impossible to say anything.

Here once more a full list of what you should post.

  • Output of the cURL call
  • Browser screenshots of
    • https://static.amp.services/test-support-cloudflare.html
    • https://static.amp.services/cdn-cgi/trace
    • http://static.amp.services/cdn-cgi/trace
  • Output of ping static.amp.services
  • Output of nslookup static.amp.services

#11

Perhaps this helps explain the situation in India:

Monitoring - A fix has been implemented and we are monitoring the results.
Jan 24, 14:14 UTC

Investigating - Cloudflare is observing network performance issues in Southeast Asia region due to problems in the Singapore point of presence.

We are working to mitigate impact to Internet users in this region.
Jan 24, 10:40 UTC

from: https://www.cloudflarestatus.com/


#12

@sandro here is more information about the problem.

nslookup and ping

accessing directly to the S3 Bucket, that works

Could not get the browser screen shots

Public IP Address

Trace Route

cURL

41

What do you think that could be the problem? Thank you for the help.


#13

Maybe a firewall on your machine (also an Anti-virus software many times includes a firewall nowdays) or close network?

Try a TCP traceroute to that host and port 443 (this is different from a regular traceroute which is usually ICMP-based on Windows an UDP-based on Linux)


#14

You seem to be able to reach Cloudflare, however the TCP connection appears to fail for some reason.

I’d try to rule out any local network security measures (e.g. firewall, router, etc.) and once you are absolutely sure the issue is not on your side I’d open a support ticket.


#15

Hi @cloonan, could you please also help me with this ticket? I’ve checked that is not only in one machine and the problem seems to be in different offices. I’ve asked for informations such as if they use the same ISP and have the same antivirus. Getting back when I have more information. Thank you.


#16

Hi @api1, I see your tickets, added some detail and merged both into 1629835.


closed #17

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.