I recently switched my cellular subscription to the Dutch telco Tele2. I noticed I can’t reach 1.1.1.1 on that 4G connection. 1.0.0.1 works though. This is observed on an iPhone, as well as on a desktop that is tethered to the same mobile connection. The desktop is what I used for the manual tests (for output see Pastebin).
Link to test in help tool: 1.1.1.1 — the Internet’s Fastest, Privacy-First DNS Resolver
The traceroute is interesting, it seems that is already blocked at your own gateway. Is there any way you could remove that block, so it would be more clear where it eventually stops.
This concerns a consumer mobile carrier network, where there’s no hardware of my own involved besides my phone. However I now did the traceroutes from my phone itself (instead of a tethered PC as mentioned above), which might give more useful results.
traceroute to 1.1.1.1 (1.1.1.1) , 5 relative hops max, 52 byte packets
1 * * *
2 95.36.65.65 (95.36.65.65) 47.288 ms 55.007 ms 57.955 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
traceroute to 1.0.0.1 (1.0.0.1) , 5 relative hops max, 52 byte packets
1 * * *
2 95.36.65.65 (95.36.65.65) 68.280 ms 193.666 ms 196.906 ms
3 * * *
4 217.16.44.25 (217.16.44.25) 211.718 ms 253.635 ms 256.408 ms
5 ae6-0.br04sara.versatel.net (212.53.25.201) 65.145 ms 189.543 ms 191.476 ms
6 ae5-0.br04tc2.versatel.net (212.53.25.193) 36.769 ms 157.327 ms 159.125 ms
7 ams5-core-1.bundle-ether6.tele2.net (212.151.190.0) 37.086 ms 196.774 ms 199.292 ms
8 ams5-peer-1.ae0-unit0.tele2.net (130.244.82.55) 35.931 ms 194.674 ms 197.200 ms
9 ams13-peer-1.ae5-unit0.tele2.net (212.151.176.245) 30.712 ms 156.420 ms 158.302 ms
10 * * *
11 one.one.one.one (1.0.0.1) 36.218 ms 191.860 ms 195.434 ms