1.1.1.1 returns ERR_CONNECTION_RESET for provider "Rostelecom" (rt.ru) in Russia

https://1.0.0.1 works fine, the problem occurs only for https://1.1.1.1 (in browser).
ERR_CONNECTION_RESET usually means the ip is censored by ISP.
I have written to Rostelecom support, waiting for a reply.
dig works fine though.

[email protected]:~$ tracepath 1.0.0.1
 1?: [LOCALHOST]                      pmtu 1500
 1:  192.168.1.1                                           1.521ms 
 1:  192.168.1.1                                           1.330ms 
 2:  192.168.1.1                                           1.415ms pmtu 1492
 2:  87.226.146.219                                       17.914ms 
 3:  79.133.87.226                                        12.749ms 
 4:  79.133.87.169                                        17.961ms 
 5:  87.226.133.121                                       59.917ms asymm  6 
 6:  no reply
 7:  no reply
 8:  no reply
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
20:  no reply
21:  no reply
22:  no reply
23:  no reply
24:  no reply
25:  no reply
^C
[email protected]:~$ tracepath 1.1.1.1
 1?: [LOCALHOST]                      pmtu 1500
 1:  192.168.1.1                                           1.410ms 
 1:  192.168.1.1                                           1.331ms 
 2:  192.168.1.1                                           1.360ms pmtu 1492
 2:  87.226.146.219                                        7.812ms 
 3:  79.133.87.226                                         8.863ms 
 4:  79.133.87.169                                         7.877ms 
 5:  213.59.208.17                                         6.911ms 
 6:  rostelecom-ic-319651-ffm-b1.c.telia.net              75.697ms 
 7:  ffm-b1-link.telia.net                                73.051ms 
 8:  no reply
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
13:  no reply
14:  no reply
15:  no reply
16:  no reply
17:  no reply
18:  no reply
19:  no reply
^C

I’m having this issue too.

ilyaigpetrov, have you received a reply from Rostelecom Support Team? If yes, would you please share it here for the public interest.

I can’t find their response in my inbox.
If you write them then don’t forget to send them results of commands ping and tracert as email attachments (they have problems with newlines in letter bodies).

Also 1.1.1.1 works fine as a DNS service, the only problem I have with DNS is that the Android app 1.1.1.1 sometimes stalls and you have to restart it.

And finally I have a rumor for you: Rostelecom blocks 1.1.1.1 because one of the censored domains resolves to 1.1.1.1 and their DPI can’t figure out if your browser visits 1.1.1.1 or another blocked domain because for 1.1.1.1 browser may not be sending SNI “header”.