Source
r/duckduckgo•
grimman

Unable to consistently load DDG recently

I have no idea what's up; I simply can't load DDG at times, though I can resolve the DNS just fine, and every other site works without a hitch.

Like I said though, it's not always a problem -- often the issue will persist for a handful of minutes and then go away. So whatever the issue is, it's intermittent and all the more annoying for it.

I have looked up the resolved IP at times, and it appears to not be tied to one specific IP address either.

Is this on my end, on DDG's end, or somewhere else along the line?

Posted Jun 4, 2018, 12:49 PM UTC

49
tagawaStaff•

I'm not seeing any issues here. As u/x-15a2 says, trying a different browser is an easy first step to double-check (as you have done), and then trying on a different network, e.g. mobile. That would clarify if it's a local network/ISP issue.

Beyond that, I recommend testing with a site checking service such as https://downforeveryoneorjustme.com/duckduckgo.com which will show if it's a global issue with our servers, or a local problem.

2
touristtam•

does that website calls DDG from multiple site/region? If it doesn't it isn't a very good indicator.

1
Prandur666•

You're completly right. It is a local problem, as it isn't present on my smartphone at the same moment (which is also using the same DNS and Router). But the behaviour is very strange nonetheless, because DDG is the only site I could see this kind of behaviour. Sometimes this issue persists through a reboot, sometimes not. Usually it resolves itself on the next day. I will look into it with wireshark the next time it comes up ... maybe this will give a hint.

1
CommonMisspellingBot•

Hey, Prandur666, just a quick heads-up:
completly is actually spelled completely. You can remember it by ends with -ely.
Have a nice day!

^^^^The ^^^^parent ^^^^commenter ^^^^can ^^^^reply ^^^^with ^^^^'delete' ^^^^to ^^^^delete ^^^^this ^^^^comment.

1
Prandur666•

I just git this behaviour again. Different Browsers -> no change

DNS -> I use my own recursive resolver which resolves duckduckgo.com to the same ip adresses as the google.dns (176.34.155.23 46.51.179.90 79.125.105.113)

Telnet or Ping to the IPs gets a timeout

Capture with wireshark gets no result. I can see the syn and retransmission but no answer

My Firewall has a localnetwork -> any allowed rule

And the most bizarre thing is that ddg most of the time without any change works

Has someone any further idea to debug this?

edit The last hop I can see in a traceroute is aws

traceroute to 176.34.155.23 (176.34.155.23), 30 hops max, 40 byte packets using UDP
1  62.155.240.149 (62.155.240.149)  8.003 ms   7.321 ms   7.105 ms
2  217.239.40.46 (217.239.40.46)  8.138 ms   8.686 ms   8.643 ms
3  80.157.206.246 (80.157.206.246)  7.780 ms   8.076 ms   8.133 ms
4  52.93.39.26 (52.93.39.26)  10.970 ms 52.93.39.42 (52.93.39.42)  8.000 ms 52.93.39.58 (52.93.39.58)  8.256 ms
5  52.93.39.113 (52.93.39.113)  8.273 ms 52.93.39.145 (52.93.39.145)  8.290 ms 52.93.39.51 (52.93.39.51)  9.502 ms
6  54.239.43.235 (54.239.43.235)  37.861 ms 54.239.45.16 (54.239.45.16)  39.824 ms 54.239.43.173 (54.239.43.173)  39.862 ms
7  205.251.232.102 (205.251.232.102)  39.738 ms 178.236.3.76 (178.236.3.76)  38.264 ms 205.251.232.102 (205.251.232.102)  39.921 ms
8  54.239.44.140 (54.239.44.140)  40.371 ms 52.93.128.210 (52.93.128.210)  40.631 ms 54.239.44.146 (54.239.44.146)  40.341 ms
9  * * *
10  52.93.6.174 (52.93.6.174)  40.731 ms 52.93.7.220 (52.93.7.220)  64.538 ms 52.93.7.210 (52.93.7.210)  39.212 ms
11  52.93.101.3 (52.93.101.3)  39.475 ms 52.93.101.11 (52.93.101.11)  39.499 ms 52.93.101.1 (52.93.101.1)  39.764 ms
12  52.93.101.20 (52.93.101.20)  52.307 ms 52.93.101.10 (52.93.101.10)  53.861 ms 52.93.101.54 (52.93.101.54)  37.877 ms
13  52.93.36.191 (52.93.36.191)  38.154 ms 52.93.7.155 (52.93.7.155)  41.188 ms 52.93.7.143 (52.93.7.143)  38.497 ms
14  * 178.236.0.89 (178.236.0.89)  40.057 ms *
15  * * *
16  * * *
17  * * *
2
touristtam•

I concurre: I have just made a tracert from a windows machine and the last hop before a "request time out" was on 52.93.7.107, which is an amazon owned ip.

Now the odd thing is that it happens while connected to my ISP and not my cell phone provider.

1
x-15a2ComLeader•

When this is happening, have you tried using a different browser? Just wondering if you're browser's cache might need to be flushed.

1
grimmanOP•

Oh, aye mate. Different browsers, different computers. Different DNS servers even (but not different networks).

1
Prandur666•

Hi, I've got the same issue. Also with different browsers and DNS servers (also tried a selfhosted recursive dns). It seems as if the connections somehow dies while TLS is negotiated.

1