1.1.1.1 not working, 1.0.0.1 is fine

I’ve not changed anything on my system, and I’ve been using 1.1.1.1 for a long time so I think it’s a Cloudflare issue
1.0.0.1 works fine but 1.1.1.1 is timing out for a couple of hours now

Should have included this: https://1.0.0.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiTm8iLCJyZXNvbHZlcklwLTEuMS4xLjEiOiJObyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkFNUyIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6IkNsb3VkZmxhcmUiLCJpc3BBc24iOiIxMzMzNSJ9

shows no connectivity to 1.1.1.1

There’s nothing in cloudflarestatus.com. Give these tips a try:
Have problems with 1.1.1.1? *Read Me First*

1 Like

The status page is showing some re-directs, one of which is Johanesburg, I’m based in Netherlands but tracert seems to be directing to Johanesburg just before the time out, so possibly something wrong with that re-direct?

1.0.0.1 for reference (working fine)
C:\WINDOWS\system32>tracert 1.0.0.1

Tracing route to one.one.one.one [1.0.0.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 13 ms 11 ms 16 ms 213.51.197.213
4 14 ms 12 ms 14 ms asd-tr0021-cr101-be156-10.core.as9143.net [213.51.158.2]
5 12 ms 10 ms 11 ms nl-ams14a-ri1-ae51-0.aorta.net [213.51.64.186]
6 14 ms 13 ms 13 ms bundle-ether1.amstr1.amsterdam.opentransit.net [193.251.150.95]
7 13 ms 11 ms 14 ms cloudflare-1.gw.opentransit.net [193.251.150.136]
8 11 ms 12 ms 10 ms one.one.one.one [1.0.0.1]

1.1.1.1
C:\Windows\System32>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms * 192.168.1.1
2 * * * Request timed out.
3 14 ms 15 ms 16 ms 213.51.197.213
4 14 ms 14 ms 12 ms asd-tr0021-cr101-be156-10.core.as9143.net [213.51.158.2]
5 11 ms 11 ms 13 ms nl-ams14a-ri1-ae51-0.aorta.net [213.51.64.186]
6 20 ms 12 ms 11 ms bundle-ether1.amstr1.amsterdam.opentransit.net [193.251.150.95]
7 17 ms 13 ms 14 ms hundredgige0-7-0-2.amscr6.amsterdam.opentransit.net [193.251.241.223]
8 37 ms 33 ms 25 ms hundredgige0-1-0-7.partr1.paris.opentransit.net [193.251.133.214]
9 69 ms 25 ms 26 ms hundredgige0-8-0-27.auvtr5.aubervilliers.opentransit.net [193.251.131.7]
10 25 ms 25 ms 25 ms gigabitethernet7-0-2.auvcr3.aubervilliers.opentransit.net [193.251.133.176]
11 190 ms 189 ms 190 ms tengige0-3-0-3.jnbcr1.johannesburg.opentransit.net [193.251.133.67]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.

That’s certainly interesting that your 1.1.1.1 trace works its way down to Johannesburg. I know @cscharff is hovering around, as is @tobi. Either can probably give this a look.

https://community.cloudflare.com/t/issues-with-1-1-1-1/236143

1 Like

I had the same problem yesterday around 17h local time for about an hour at least, I’m also based in The Netherlands.
Was a bit disappointed that 1.1.1.1 went down to be honest, especially since I couldn’t find a clear confirmation online that that was the case. Spend quite some time troubleshooting the local network before realizing 1.1.1.1 was actually unreachable from at least my location.

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