ERR_CONNECTION_TIMED_OUT on a specific ISP only

Website, Application, Performance DNS & Network
1

What is the name of the domain?

app.sushovan.de

What is the error number?

ERR_CONNECTION_TIMED_OUT

What is the error message?

app.sushovan.de took too long to respond.

What is the issue you’re encountering

Website works on mobile networks but does not work on cabled internet

What steps have you taken to resolve the issue?

  1. The website is hosted using Amazon S3 static website hosting, then proxied via cloudflare, where SSL is added.
  2. I tried doing nslookup app.sushovan.de and I got two IP addresses that appear to be cloudflare addresses. (104.21.88.143, 172.67.182.96)
  3. I checked if other websites are working fine, including Google and Cloudflare console itself, they are
  4. I checked if I could access the site using my mobile phone on a cellular connection, it is working fine
  5. I checked if I could ping the site ping app.sushovan.de. I could not: Request timeout for icmp_seq 0
  6. I checked if I could access the origin server directly, I could.

What feature, service or problem is this related to?

DNS records

2

I forgot to mention, according to whatismyisp[.]com, my network is

Dreamweavers It Servicesalso known as ‘Alliance Broadband Services Pvt. Ltd.’.

Your IP: 103.102.116.xx

(This is in Kolkata, India)

3

Any tips? This is consistent across many months. I think there is some sort of a routing issue between this ISP and certain Cloudflare endpoints (e.g. Cloudflare Pages endpoints work fine, but my proxied cloudflare sites are not working, multiple of them). How do I debug further / how do I escalate to Cloudflare?

5

Can you share a traceroute to these IP addresses?

What does the problematic ISP have to say about the issue?

So far, it sounds like you’re suffering the consequences of your ISP’s bad actions, such as these outlined in e.g.:

A traceroute may likely be helpful for that.

An ISP that is blocking access to IP addresses, and the consequences and/or collateral damage of these actions, will be something you will need to take up with the individual ISP.

6

Thanks, DarkDeviL!

Here is the result of the traceroute to 172.67.182.96. Traceroute to the other IP is similar. I am quite surprised to see the 192.168.* number at position 4 :frowning:

Any tips on how to contact an ISP? Has anyone done so successfully before? I can very clearly anticipate a frustrating conversation with customer support, who will likely have no clue about something like this.

 1  192.168.0.1 (192.168.0.1)  2.714 ms  2.580 ms  2.588 ms
 2  172.16.132.1 (172.16.132.1)  3.336 ms  3.611 ms  2.952 ms
 3  node-150-107-176-65.alliancebroadband.in (150.107.176.65)  4.413 ms *  35.724 ms
 4  192.168.199.22 (192.168.199.22)  5.949 ms  3.671 ms  4.784 ms
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
7

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