IPv6 routing issue affecting VI (Vodafone Idea) network users in India — requests time out

S

Support AI

Based on the provided documentation, it appears that the issue is related to IPv6 compatibility. According to the documentation (https://developers.cloudflare.com/network/ipv6-compatibility/), when IPv6 compatibility is turned on, Cloudflare auto generates

AAAA

AAAA

DNS records to allow IPv6 clients to connect. However, in this case, the traceroute shows packets stopping inside Cloudflare's IPv6 edge, suggesting that there may be an issue with IPv6 connectivity.

It's also worth noting that the documentation (https://developers.cloudflare.com/support/troubleshooting/general-troubleshooting/potential-isp-blocking/) mentions that Cloudflare cannot guarantee that assigned IP addresses are not blocked by any country or Internet service provider (ISP). However, in this case, the issue seems to be specific to the VI mobile network in India and is resolved when disabling the Cloudflare proxy or accessing the origin directly.

Unfortunately, without further information or troubleshooting, it's difficult to provide a more specific solution. However, it may be worth investigating the IPv6 configuration and connectivity for the domain and origin server.

Sources

* Telefónica Spain (AS3352) cannot reach proxied site - works fine when unproxied
* Potential ISP blocking of Cloudflare IP addresses - Cloudflare Support docs
* IPv6 compatibility - Cloudflare Network settings docs

Feedback

Feedback has been submitted! Thank you :)

This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.

..ᗷᗩTTEᖇY [Low]My domain is proxied through Cloudflare. When accessed over the VI (Vodafone Ide...

D

DarkDeviL•11/22/25, 3:26 PM

Can you possibly expand on this?

1. What is the AS number of the problematic ISP?
The AS number can be found here:
* https://1.1.1.1/help
-> AS Number
* https://bgp.tools/
-> The AS number shown under "You are connecting from" like this: "Cloudflare, Inc. (AS13335)"
* https://bgp.he.net/
-> The AS number shown like this: "Your ISP is AS13335 (Cloudflare, Inc.)"

2. What domain?
3. What exact 2606:4700:*
2606:4700:*
2606:4700:*
2606:4700:* IPv6 address(es) are you having these issues with?

DDarkDeviL Can you possibly expand on this? 1. What is the AS number of the problematic IS...

.

.ᗷᗩTTEᖇY [Low]OP•11/24/25, 1:55 PM

1. AS: Vodafone Idea (Vodafone India) (AS38266)
2. Can not share the domain for security reason. But it is a api (expressjs) domain. All other frontend sites(like Nexjs) working even with poroxy on.
3. * IPv6: 2606:4700:3030::6815:1536, 2606:4700:3030::ac43:c47d
* IPv4: 104.21.21.54, 172.67.196.125

Also

curl

curl

command is working on terminal if i connect with mobile hotspot, but our react native app (apk) on the device(mobile) is giving connection error for every VI network.

.

.ᗷᗩTTEᖇY [Low]OP•11/24/25, 2:10 PM

curl -v <domain>

curl -v <domain>

curl -v <domain>

curl -v <domain>

* Host was resolved.
* IPv6: 2606:4700:3030::ac43:c47d, 2606:4700:3030::6815:1536
* IPv4: 172.67.196.125, 104.21.21.54
*   Trying [2606:4700:3030::ac43:c47d]:443...
*   Trying 172.67.196.125:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
*  CApath: none
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305 / x25519 / id-ecPublicKey
* ALPN: server accepted h2
* Server certificate:
*  SSL certificate verify ok.
* Connected to <domain> port 443
* using HTTP/2
* [HTTP/2] [1] OPENED stream for <domain>
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.15.0]
* [HTTP/2] [1] [accept: */*]
GET / HTTP/2
Host: <domain>
User-Agent: curl/8.15.0

* Host was resolved.
* IPv6: 2606:4700:3030::ac43:c47d, 2606:4700:3030::6815:1536
* IPv4: 172.67.196.125, 104.21.21.54
*   Trying [2606:4700:3030::ac43:c47d]:443...
*   Trying 172.67.196.125:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
*  CApath: none
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305 / x25519 / id-ecPublicKey
* ALPN: server accepted h2
* Server certificate:
*  SSL certificate verify ok.
* Connected to <domain> port 443
* using HTTP/2
* [HTTP/2] [1] OPENED stream for <domain>
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.15.0]
* [HTTP/2] [1] [accept: */*]
GET / HTTP/2
Host: <domain>
User-Agent: curl/8.15.0

* Host was resolved.
* IPv6: 2606:4700:3030::ac43:c47d, 2606:4700:3030::6815:1536
* IPv4: 172.67.196.125, 104.21.21.54
*   Trying [2606:4700:3030::ac43:c47d]:443...
*   Trying 172.67.196.125:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
*  CApath: none
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305 / x25519 / id-ecPublicKey
* ALPN: server accepted h2
* Server certificate:
*  SSL certificate verify ok.
* Connected to <domain> port 443
* using HTTP/2
* [HTTP/2] [1] OPENED stream for <domain>
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.15.0]
* [HTTP/2] [1] [accept: */*]
GET / HTTP/2
Host: <domain>
User-Agent: curl/8.15.0

* Host was resolved.
* IPv6: 2606:4700:3030::ac43:c47d, 2606:4700:3030::6815:1536
* IPv4: 172.67.196.125, 104.21.21.54
*   Trying [2606:4700:3030::ac43:c47d]:443...
*   Trying 172.67.196.125:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
*  CApath: none
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305 / x25519 / id-ecPublicKey
* ALPN: server accepted h2
* Server certificate:
*  SSL certificate verify ok.
* Connected to <domain> port 443
* using HTTP/2
* [HTTP/2] [1] OPENED stream for <domain>
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.15.0]
* [HTTP/2] [1] [accept: */*]
GET / HTTP/2
Host: <domain>
User-Agent: curl/8.15.0

.

.ᗷᗩTTEᖇY [Low]OP•11/24/25, 2:10 PM

Accept: */*
* Request completely sent off
< HTTP/2 404 
< date: Mon, 24 Nov 2025 13:57:07 GMT
< content-type: application/json; charset=utf-8
< content-length: 76
< access-control-allow-credentials: true
< alt-svc: h3=":443"; ma=86400
< content-security-policy: default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
< cross-origin-opener-policy: same-origin
< cross-origin-resource-policy: same-origin
< etag: W/"4c-4SAk1an57TdVsiQKL8xettWWl3E"
< origin-agent-cluster: ?1
< referrer-policy: no-referrer
< vary: Accept-Encoding
< vary: Origin, Accept-Encoding
< x-content-type-options: nosniff
< x-dns-prefetch-control: off
< x-download-options: noopen
< x-frame-options: SAMEORIGIN
< x-permitted-cross-domain-policies: none
< x-xss-protection: 0
< cf-cache-status: DYNAMIC
< nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
< report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=FwTXnQbw6qcfhRsS6bhJzcZVb6rRGg8u5niQ7MFRkXpz%2FcBiGxJJwg3EVm10Exzzl2fR%2FGHJbZGu4OW0tNXWRj8u9fD%2F84EdGOFzra3qk2rKBuc8Btzn3g2ygQuYA31uiszvU%2BJw2%2B8%3D"}]}
< server: cloudflare
< cf-ray: 9a3969e16c623815-FRA
< 
* Connection #0 to host <domain> left intact

Accept: */*
* Request completely sent off
< HTTP/2 404 
< date: Mon, 24 Nov 2025 13:57:07 GMT
< content-type: application/json; charset=utf-8
< content-length: 76
< access-control-allow-credentials: true
< alt-svc: h3=":443"; ma=86400
< content-security-policy: default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
< cross-origin-opener-policy: same-origin
< cross-origin-resource-policy: same-origin
< etag: W/"4c-4SAk1an57TdVsiQKL8xettWWl3E"
< origin-agent-cluster: ?1
< referrer-policy: no-referrer
< vary: Accept-Encoding
< vary: Origin, Accept-Encoding
< x-content-type-options: nosniff
< x-dns-prefetch-control: off
< x-download-options: noopen
< x-frame-options: SAMEORIGIN
< x-permitted-cross-domain-policies: none
< x-xss-protection: 0
< cf-cache-status: DYNAMIC
< nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
< report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=FwTXnQbw6qcfhRsS6bhJzcZVb6rRGg8u5niQ7MFRkXpz%2FcBiGxJJwg3EVm10Exzzl2fR%2FGHJbZGu4OW0tNXWRj8u9fD%2F84EdGOFzra3qk2rKBuc8Btzn3g2ygQuYA31uiszvU%2BJw2%2B8%3D"}]}
< server: cloudflare
< cf-ray: 9a3969e16c623815-FRA
< 
* Connection #0 to host <domain> left intact

Accept: */*
* Request completely sent off
< HTTP/2 404 
< date: Mon, 24 Nov 2025 13:57:07 GMT
< content-type: application/json; charset=utf-8
< content-length: 76
< access-control-allow-credentials: true
< alt-svc: h3=":443"; ma=86400
< content-security-policy: default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
< cross-origin-opener-policy: same-origin
< cross-origin-resource-policy: same-origin
< etag: W/"4c-4SAk1an57TdVsiQKL8xettWWl3E"
< origin-agent-cluster: ?1
< referrer-policy: no-referrer
< vary: Accept-Encoding
< vary: Origin, Accept-Encoding
< x-content-type-options: nosniff
< x-dns-prefetch-control: off
< x-download-options: noopen
< x-frame-options: SAMEORIGIN
< x-permitted-cross-domain-policies: none
< x-xss-protection: 0
< cf-cache-status: DYNAMIC
< nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
< report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=FwTXnQbw6qcfhRsS6bhJzcZVb6rRGg8u5niQ7MFRkXpz%2FcBiGxJJwg3EVm10Exzzl2fR%2FGHJbZGu4OW0tNXWRj8u9fD%2F84EdGOFzra3qk2rKBuc8Btzn3g2ygQuYA31uiszvU%2BJw2%2B8%3D"}]}
< server: cloudflare
< cf-ray: 9a3969e16c623815-FRA
< 
* Connection #0 to host <domain> left intact

Accept: */*
* Request completely sent off
< HTTP/2 404 
< date: Mon, 24 Nov 2025 13:57:07 GMT
< content-type: application/json; charset=utf-8
< content-length: 76
< access-control-allow-credentials: true
< alt-svc: h3=":443"; ma=86400
< content-security-policy: default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
< cross-origin-opener-policy: same-origin
< cross-origin-resource-policy: same-origin
< etag: W/"4c-4SAk1an57TdVsiQKL8xettWWl3E"
< origin-agent-cluster: ?1
< referrer-policy: no-referrer
< vary: Accept-Encoding
< vary: Origin, Accept-Encoding
< x-content-type-options: nosniff
< x-dns-prefetch-control: off
< x-download-options: noopen
< x-frame-options: SAMEORIGIN
< x-permitted-cross-domain-policies: none
< x-xss-protection: 0
< cf-cache-status: DYNAMIC
< nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
< report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=FwTXnQbw6qcfhRsS6bhJzcZVb6rRGg8u5niQ7MFRkXpz%2FcBiGxJJwg3EVm10Exzzl2fR%2FGHJbZGu4OW0tNXWRj8u9fD%2F84EdGOFzra3qk2rKBuc8Btzn3g2ygQuYA31uiszvU%2BJw2%2B8%3D"}]}
< server: cloudflare
< cf-ray: 9a3969e16c623815-FRA
< 
* Connection #0 to host <domain> left intact

..ᗷᗩTTEᖇY [Low]1. AS: Vodafone Idea (Vodafone India) (AS38266) 2. Can not share the domain for ...

D

DarkDeviL•11/25/25, 2:40 AM

Can you try (and provide the output of the following)?

1.

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47d]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47d]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47d]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47d]" https://example.com

2.

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::6815:1536]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::6815:1536]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::6815:1536]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::6815:1536]" https://example.com

3.

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:104.21.21.54" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:104.21.21.54" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:104.21.21.54" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:104.21.21.54" https://example.com
4.

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:172.67.196.125" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:172.67.196.125" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:172.67.196.125" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:172.67.196.125" https://example.com

Note: Change both instances of

example.com

example.com

to match the domain name you're having issues with.

If Windows: Change "

-o /dev/null

-o /dev/null

-o /dev/null

-o /dev/null" to "

-o nul

-o nul

-o nul

-o nul".

DDarkDeviL Can you try (and provide the output of the following)? 1. `curl -sS -o /dev/nul...

.

.ᗷᗩTTEᖇY [Low]OP•11/25/25, 6:27 AM

All are ok, i mean 200

..ᗷᗩTTEᖇY [Low]All are ok, i mean 200

D

DarkDeviL•11/25/25, 1:18 PM

Sounds like the problem is gone then.

D

DarkDeviL•11/25/25, 1:20 PM

I was however suspecting that your ISP was being silly, ... e.g. as outlined over here: https://blog.cloudflare.com/consequences-of-ip-blocking/

The Cloudflare Blog

The unintended consequences of blocking IP addresses

A discussion about IP blocking: why we see it, what it is, what it does, who it affects, and why it’s such a problematic way to address content online.

DDarkDeviL I was however suspecting that your ISP was being silly, ... e.g. as outlined ove...

.

.ᗷᗩTTEᖇY [Low]OP•11/27/25, 8:49 AM

Problem is not solved. But i guess it is not an issue with Cloudflare.

..ᗷᗩTTEᖇY [Low]Problem is not solved. But i guess it is not an issue with Cloudflare.

D

DarkDeviL•11/28/25, 6:09 PM

You indicated a 200 response as a result of the commands, which would mean it was working at the time you ran the commands.

D

DarkDeviL•11/28/25, 6:12 PM

As you indicated the problem was with e.g.

2606:4700:3030::ac43:c47d

2606:4700:3030::ac43:c47d

2606:4700:3030::ac43:c47d

2606:4700:3030::ac43:c47d, you can also try if you experience further trouble:

1.

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47d]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47d]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47d]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47d]" https://example.com

If that is failing during the issue, then switch one of the ending characters (

a-f

a-f

a-f

a-f,

0-9

0-9

0-9

0-9), so e.g. switch

c47d

c47d

c47d

c47d to

c47e

c47e

c47e

c47e, so it becomes:

2.

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47e]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47e]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47e]" https://example.com

curl -sS -o /dev/null -w "%{response_code}\n" --resolve "example.com:443:[2606:4700:3030::ac43:c47e]" https://example.com

If the IP switch to a surrounding IP address (e.g.

c47d

c47d

c47d

c47d to

c47e

c47e

c47e

c47e) works, but the other one doesn't, ... then you're looking at your ISP blocking the specific IP address.

D

DarkDeviL•11/28/25, 6:14 PM

LaLiga, in Spain, to mention one example, they apparently have the ability to blocking (certain) IP addresses during football matches, making these blocks randomly appear while the football matches are live, and disappear once they are no longer live.

D

DarkDeviL•11/28/25, 6:15 PM

Most often with IP blocks though, they are usually quite "permanent", rather than "intermittent", like the ones with LaLiga & Spain.

.

.ᗷᗩTTEᖇY [Low]OP•11/29/25, 7:49 AM

Okay, thanks

IPv6 routing issue affecting VI (Vodafone Idea) network users in India — requests time out

Similar Threads

Similar Threads

Similar Threads