1.1.1.1 is not reachable in my country!


#1

Hello cloudflare guys!
I hope that you are doing great, i am from Libya and I have been using cloudflare for a while now, the closest servers to Libya are located in Greece…the problem is that 1.1.1.1 isn’t reachable at all, 1.0.0.1 works fine.
Does 1.1.1.1 & 1.0.0.1 have the same quality and speed?, can I depend only on 1.0.0.1?
I am using a CPE (wimax route …SWC 9100).


#2

Can you post a traceroute to 1.1.1.1?


#3

Hello Sandro … Would you please help me out how to do that exactly?.. I will be grateful to you


#4

I presume you are using Windows, right?


#5

I am using Windows 7 and Android 8.0


#6

In this case, open the start menu, type “cmd”, that should select the “Command Prompt” or cmd.exe, open that, and type the following command, followed by enter

tracert -d 1.1.1.1

Copy its output and post it here.


#7

Sorry for being late … Here is my results


#8

For 1.0.0.1


#9

It seems your router hijacked 1.1.1.1 and does not forward the request to its actual destination.

Maybe there is some way to configure it so that it releases the address or maybe you could change to another model which does not hijack the address. I’d contact the ISP and try to clarify that. A quick search for that model unfortunately did not reveal much.


#10

Thank you very much
I will keep just using 1.0.0.1 for now
Do you think it will give me the same quality of 1.1.1.1 ?.. Can I depend just on 1.0.0.1?


#11

Thats a question to be answered in detail by Cloudflare, but considering 1.0.0.1 is the complementary server I’d expect it to work just as fine.

Though, I’d still try to fix the issue with the hijacked address. No device should that, thats a matter of principle :slight_smile:


#12

The alternate addresses provide exactly the same performance, what might differ is the routing quality, but if you can’t reach 1.1.1.1, then 1.0.0.1 or the IPv6 addresses are your best bet.


#13

https://cloudflare-dns.com/help/#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiTm8iLCJyZXNvbHZlcklwLTEuMS4xLjEiOiJObyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkFUSCIsImlzcE5hbWUiOiJDbG91ZGZsYXJlIiwiaXNwQXNuIjoiMTMzMzUifQ==


#14

That doesnt tell us much more than what we already know :wink:

The problem appears to be with your router.