Unable to access imgur.com

Hello good day,

This was started around midnight of Jun 12 - 13 Philippine Time, I am not able to browse to imgur.com even on the mobile app if I use the 1.1.1.1 or 1.0.0.1 DNS but works perfectly on google dns or the default ISP dns. For now I’m forced to used the google dns.

Any suggestion I can do on my side to fix this issue?

Thank you

Hi @gilcon,

Are you still having this issue?

If so, can you provide the troubleshooting information requested in Have problems with 1.1.1.1? *Read Me First*.

Yes I’m still having this issue.

1.1.1.1

; <<>> DiG 9.16.16 <<>> imgur.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13188
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;imgur.com.			IN	A

;; ANSWER SECTION:
imgur.com.		82506	IN	A	151.101.40.193

;; Query time: 26 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Jun 21 07:39:53 PST 2021
;; MSG SIZE  rcvd: 54

1.0.0.1

; <<>> DiG 9.16.16 <<>> imgur.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35618
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;imgur.com.			IN	A

;; ANSWER SECTION:
imgur.com.		82442	IN	A	151.101.40.193

;; Query time: 29 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Jun 21 07:40:55 PST 2021
;; MSG SIZE  rcvd: 54

8.8.8.8

; <<>> DiG 9.16.16 <<>> imgur.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58798
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;imgur.com.			IN	A

;; ANSWER SECTION:
imgur.com.		21599	IN	A	151.101.40.193

;; Query time: 53 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Jun 21 07:41:35 PST 2021
;; MSG SIZE  rcvd: 54
~ 
βœ— dig +short CHAOS TXT id.server @1.1.1.1
"MNL"

~ 
➜ dig +short CHAOS TXT id.server @1.0.0.1
"MNL"

~ 
➜ dig @ns3.Cloudflare.com whoami.Cloudflare.com txt +short
"180.194.235.65"

Result from cloudflare-dns.com/help/

This is also the result on firefox network dev tools


and here is from chrome

using the s.imgur.com

➜ dig s.imgur.com @1.1.1.1

; <<>> DiG 9.16.16 <<>> s.imgur.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60512
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;s.imgur.com.			IN	A

;; ANSWER SECTION:
s.imgur.com.		86400	IN	CNAME	ipv4.imgur.map.fastly.net.
ipv4.imgur.map.fastly.net. 30	IN	A	151.101.52.193

;; Query time: 133 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Jun 21 08:03:47 PST 2021
;; MSG SIZE  rcvd: 95


~ 
➜ dig s.imgur.com @1.0.0.1

; <<>> DiG 9.16.16 <<>> s.imgur.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49140
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;s.imgur.com.			IN	A

;; ANSWER SECTION:
s.imgur.com.		86392	IN	CNAME	ipv4.imgur.map.fastly.net.
ipv4.imgur.map.fastly.net. 22	IN	A	151.101.52.193

;; Query time: 26 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Jun 21 08:03:52 PST 2021
;; MSG SIZE  rcvd: 95


~ 
➜ dig s.imgur.com @8.8.8.8

; <<>> DiG 9.16.16 <<>> s.imgur.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55648
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;s.imgur.com.			IN	A

;; ANSWER SECTION:
s.imgur.com.		3585	IN	CNAME	ipv4.imgur.map.fastly.net.
ipv4.imgur.map.fastly.net. 13	IN	A	151.101.40.193

;; Query time: 66 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Jun 21 08:03:58 PST 2021
;; MSG SIZE  rcvd: 95

Is it possible that your browsers are using IPv6? You can click one of the failing entries from the Chrome Network Tools and check which IP it is trying to reach. Alternatively, can you try to ping the IPs? Seems to be working fine from a DNS level.

1 Like

Unfortunately ip address is not shown in the headers. But on the main domain imgur.com it using ipv4

Here is the ping resulto of imgur.com and s.imgur.com

➜ ping imgur.com
PING imgur.com (151.101.24.193) 56(84) bytes of data.
64 bytes from 151.101.24.193 (151.101.24.193): icmp_seq=1 ttl=55 time=177 ms
64 bytes from 151.101.24.193 (151.101.24.193): icmp_seq=2 ttl=55 time=176 ms
64 bytes from 151.101.24.193 (151.101.24.193): icmp_seq=3 ttl=55 time=176 ms
64 bytes from 151.101.24.193 (151.101.24.193): icmp_seq=4 ttl=55 time=176 ms
64 bytes from 151.101.24.193 (151.101.24.193): icmp_seq=5 ttl=55 time=177 ms
64 bytes from 151.101.24.193 (151.101.24.193): icmp_seq=6 ttl=55 time=177 ms
^C64 bytes from 151.101.24.193: icmp_seq=7 ttl=55 time=176 ms

--- imgur.com ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 31254ms
rtt min/avg/max/mdev = 176.080/176.513/177.074/0.307 ms

~ took 32s 
➜ ping s.imgur.com
PING ipv4.imgur.map.fastly.net (151.101.52.193) 56(84) bytes of data.
From 210.213.131.24.static.pldt.net (210.213.131.24) icmp_seq=1 Time to live exceeded
From 210.213.131.24.static.pldt.net (210.213.131.24) icmp_seq=2 Time to live exceeded
From 210.213.131.24.static.pldt.net (210.213.131.24) icmp_seq=3 Time to live exceeded
From 210.213.131.24.static.pldt.net (210.213.131.24) icmp_seq=4 Time to live exceeded
From 210.213.131.24.static.pldt.net (210.213.131.24) icmp_seq=5 Time to live exceeded
^C
--- ipv4.imgur.map.fastly.net ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4006ms

This is the traceroute between 1.1.1.1 and 8.8.8.8

Traceroute on 1.1.1.1
~ 
βœ— traceroute s.imgur.com
traceroute to s.imgur.com (151.101.52.193), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.273 ms  0.346 ms  0.399 ms
 2  180.194.224.1 (180.194.224.1)  10.744 ms  9.942 ms  10.865 ms
 3  124.106.9.182 (124.106.9.182)  14.057 ms  14.264 ms 124.106.9.186 (124.106.9.186)  15.921 ms
 4  210.213.131.26.static.pldt.net (210.213.131.26)  29.634 ms 210.213.131.24.static.pldt.net (210.213.131.24)  31.961 ms  31.919 ms
 5  122.2.203.106.static.pldt.net (122.2.203.106)  29.513 ms  29.770 ms  29.583 ms
 6  122.2.203.109.static.pldt.net (122.2.203.109)  56.913 ms  50.166 ms  50.099 ms
 7  210.213.133.228.static.pldt.net (210.213.133.228)  51.694 ms  57.723 ms  57.795 ms
 8  210.213.130.157.static.pldt.net (210.213.130.157)  56.827 ms  56.137 ms 210.213.130.161.static.pldt.net (210.213.130.161)  56.838 ms
 9  210.213.131.26.static.pldt.net (210.213.131.26)  59.665 ms 210.213.131.24.static.pldt.net (210.213.131.24)  57.886 ms  58.321 ms
10  122.2.203.106.static.pldt.net (122.2.203.106)  56.584 ms  55.945 ms  56.635 ms
11  122.2.203.109.static.pldt.net (122.2.203.109)  82.399 ms  82.333 ms  79.306 ms
12  210.213.133.228.static.pldt.net (210.213.133.228)  80.782 ms  80.738 ms  80.263 ms
13  210.213.130.161.static.pldt.net (210.213.130.161)  123.745 ms  123.171 ms 210.213.130.157.static.pldt.net (210.213.130.157)  78.099 ms
14  210.213.131.26.static.pldt.net (210.213.131.26)  84.234 ms 210.213.131.24.static.pldt.net (210.213.131.24)  82.476 ms 210.213.131.26.static.pldt.net (210.213.131.26)  81.854 ms
15  122.2.203.106.static.pldt.net (122.2.203.106)  79.831 ms  75.412 ms  75.392 ms
16  122.2.203.109.static.pldt.net (122.2.203.109)  98.644 ms  100.211 ms  97.557 ms
17  210.213.133.228.static.pldt.net (210.213.133.228)  101.293 ms  100.059 ms  102.244 ms
18  210.213.130.157.static.pldt.net (210.213.130.157)  104.933 ms  106.101 ms 210.213.130.161.static.pldt.net (210.213.130.161)  106.115 ms
19  210.213.131.24.static.pldt.net (210.213.131.24)  108.147 ms 210.213.131.26.static.pldt.net (210.213.131.26)  106.149 ms 210.213.131.24.static.pldt.net (210.213.131.24)  107.834 ms
20  122.2.203.106.static.pldt.net (122.2.203.106)  105.500 ms  106.020 ms  102.099 ms
21  122.2.203.109.static.pldt.net (122.2.203.109)  126.909 ms  126.864 ms  125.497 ms
22  210.213.133.228.static.pldt.net (210.213.133.228)  127.495 ms  128.245 ms  128.205 ms
23  210.213.130.161.static.pldt.net (210.213.130.161)  127.692 ms 210.213.130.157.static.pldt.net (210.213.130.157)  130.557 ms 210.213.130.161.static.pldt.net (210.213.130.161)  125.950 ms
24  210.213.131.26.static.pldt.net (210.213.131.26)  122.800 ms 210.213.131.24.static.pldt.net (210.213.131.24)  126.627 ms  124.757 ms
25  122.2.203.106.static.pldt.net (122.2.203.106)  123.836 ms  123.785 ms  123.251 ms
26  122.2.203.109.static.pldt.net (122.2.203.109)  149.486 ms  149.417 ms  148.405 ms
27  210.213.133.228.static.pldt.net (210.213.133.228)  150.967 ms  150.184 ms  150.117 ms
28  210.213.130.157.static.pldt.net (210.213.130.157)  149.307 ms  149.190 ms  148.520 ms
29  210.213.131.24.static.pldt.net (210.213.131.24)  151.210 ms  150.366 ms  150.921 ms
30  122.2.203.106.static.pldt.net (122.2.203.106)  148.430 ms  148.428 ms  147.730 ms

Traceroute 8.8.8.8
~ took 28s 
➜ traceroute s.imgur.com
traceroute to s.imgur.com (151.101.40.193), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.596 ms  0.551 ms  0.524 ms
 2  180.194.224.1 (180.194.224.1)  10.357 ms  10.319 ms  10.907 ms
 3  124.106.9.186 (124.106.9.186)  11.308 ms  11.916 ms 124.106.9.182 (124.106.9.182)  10.175 ms
 4  210.213.131.26.static.pldt.net (210.213.131.26)  29.317 ms  28.165 ms  29.385 ms
 5  122.2.203.106.static.pldt.net (122.2.203.106)  25.430 ms  25.836 ms  25.175 ms
 6  122.2.203.109.static.pldt.net (122.2.203.109)  51.772 ms  50.153 ms  51.852 ms
 7  10ge1-7.core1.hkg1.he.net (74.82.46.121)  204.664 ms  222.055 ms  222.101 ms
 8  100ge10-1.core1.tyo1.he.net (184.105.64.130)  208.251 ms  203.108 ms  207.402 ms
 9  100ge12-2.core1.sjc2.he.net (184.104.194.37)  206.931 ms  207.448 ms  202.316 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

P.S.
Also on my mobile devices if I set the dns to 1.1.1.1 same issue happened and their mobile app wont work either.

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