1.1.1.1 blocked by my ISP provider T-Mobile CZ


#1

Hello,

I am not able to reach website or DNS or ping server 1.1.1.1

C:\Users\WIN10PC>tracert -d 1.1.1.1

Tracing route to 1.1.1.1 over a maximum of 30 hops

1 152 ms 13 ms 7 ms 192.168.43.1
2 229 ms 38 ms 36 ms 194.212.194.18
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 202 ms 71 ms 75 ms 1.1.1.1

Trace complete.

C:\Users\WIN10PC>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=55ms TTL=57
Reply from 8.8.8.8: bytes=32 time=74ms TTL=57

Ping statistics for 8.8.8.8:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 74ms, Average = 64ms
Control-C
^C
C:\Users\WIN10PC>

C:\Users\WIN10PC>ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=105ms TTL=53
Reply from 1.1.1.1: bytes=32 time=113ms TTL=53

Ping statistics for 1.1.1.1:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 113ms, Average = 109ms
Control-C
^C
C:\Users\WIN10PC>tracert -d 1.1.1.1

Tracing route to 1.1.1.1 over a maximum of 30 hops

1 152 ms 13 ms 7 ms 192.168.43.1
2 229 ms 38 ms 36 ms 194.212.194.18
3 * * * Request timed out.
4 * * * Request timed out.

can you check that?

thank you

Jan


#2

sorry strange paste.
so can not ping or reach via www or DNS

Tracing route to 1.1.1.1 over a maximum of 30 hops

1 152 ms 13 ms 7 ms 192.168.43.1
2 229 ms 38 ms 36 ms 194.212.194.18
and then timeout.

ISP - AS5588

thanks

Jan


#3

1.1.1.1 not being reachable is typically problem in the ISP network, so I would ask their support. (unless you suspect that some your devices is doing that, but the trace output suggests it’s in ISP)


#4

Would you mind doing this as well? I’ll pass along the consolidate results to our network team.

curl or visit http://www.cloudflare/cdn-cgi/trace and copy the output.


#5

Hi,

thank you for answer looks like that problem is solved now.

Jan

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

1 4 ms 2 ms 3 ms 192.168.43.1
2 35 ms 17 ms 17 ms 194.212.194.18
3 53 ms 33 ms 33 ms 62.29.242.90
4 * * * Request timed out.
5 216 ms 47 ms 207 ms cloudflare.thinx.pl [212.91.0.28]
6 50 ms 49 ms 44 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]

C:\Users\WIN10PC>ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=76ms TTL=55
Reply from 1.1.1.1: bytes=32 time=42ms TTL=55

fl=73f5
h=www.cloudflare.com
ip=37.48.56.162
ts=1523300126.464
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
colo=WAW
spdy=h2
http=h2
loc=CZ