Well, have you checked traceroute without openwrt based router? Just connect the pc/laptop to the modem directly and see if you're able to ping/traceroute 1.1.1.1.
I don't have a laptop and my pc can't reach the cable from modem. I think my isp might be using that ip internally.
No, because you can connect to 1.1.1.1 using 53/udp...now, I am confused why you cannot reach https (443/tcp)...try this link directly, maybe you were only doing HTTP:
To be sure, try this link with HTTPS already added to the URL: https://1.1.1.1
To be clear...what's your issue currently - aside you haven't yet verified web browsing (as we know you can in fact reach 1.1.1.1)? 
This is normal...especially with anycast networks broadcasting an IP like 1.1.1.1. In fact, it's how I knew you could actually reach 1.1.1.1! 
BTW, ISPs are not required to make their intermediate devices respond to traces or pings (although it's helpful in cases like yours).
with https browser says unable to connect, with http, it keeps on loading.
I am able to connect it using tor.
At this point, you'll need to quote actual error messages/codes to assist yourself.
Of course, others told you this already...but since I mentioned anycast; and then you mentioned Tor...I'm realizing that you did not understand my point. 1.1.1.1 is not a single device sitting somewhere, it is an IP that is configured to route to the closest server...so using Tor doesn't help you troubleshoot the issue.
If you are using default OpenWrt configs, then you can safely rule out the device.
1 Like