apkpure.com is blocked on multiple Indian ISPs

  • Thread starter Thread starter JB701
  • Start date Start date
  • Replies Replies 47
  • Views Views 7,982
similar route but its still giving me same message

Code:
Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
1. DESKTOP-MR5T1CK                                                           0.0%     7    0.3   0.3   0.3   0.4   0.0
2. 10.4.192.1                                                                0.0%     7    6.8   3.3   2.2   6.8   1.6
3. (waiting for reply)
4. 103.56.228.65                                                             0.0%     7    8.2   8.7   4.8  16.5   4.3
5. 14.141.116.229.static-Delhi.vsnl.net.in                                   0.0%     7    2.7   3.4   2.6   4.8   0.8
6. 172.31.167.58                                                             0.0%     6   41.6  44.4  40.1  58.8   7.1
7. 14.141.123.226.static-Chennai.vsnl.net.in                                 0.0%     6   41.3  40.7  39.8  41.3   0.6
8. (waiting for reply)
9. 121.240.243.210.STATIC-Mumbai.vsnl.net.in                                40.0%     6   53.8  58.0  50.8  69.3   9.9
10. 104.20.82.194                                                             0.0%     6   49.4  53.0  49.4  60.5   4.9

encrypted dns on ff didn't fix it either.

With GoodByeDPI it works on https
 
what error it say without it? It loads on my backup ISP which uses JIO backend. You are on Airtel looking at your profile.

Only TATA backend ISP seem to be affected.

Code:
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. DESKTOP-MR5T1CK                                                           0.0%     3    0.3   0.3   0.3   0.3   0.0
 2. router.localdomain                                                        0.0%     3    2.8   2.8   2.3   3.2   0.5
 3. dhcp.tripleplay.in                                                        0.0%     3    4.3   3.8   2.6   4.5   1.0
 4. (waiting for reply)
 5. core-router.static.tripleplay.in                                          0.0%     3    2.9  13.4   2.9  26.9  12.3
 6. 136.232.137.57.static.jio.com                                             0.0%     3    5.3   8.2   3.7  15.5   6.4
 7. 172.26.40.64                                                              0.0%     3   28.6  30.9  28.6  35.1   3.7
 8. 172.26.40.64                                                              0.0%     3   29.8  34.0  29.8  37.6   3.9
 9. 49.44.18.38                                                               0.0%     3   28.7  33.2  28.7  41.6   7.3
10. 10.70.14.97                                                               0.0%     3   32.7  32.9  32.4  33.6   0.6
11. (waiting for reply)
12. 49.44.187.43                                                              0.0%     2   28.1  28.5  28.1  28.8   0.5
13. 104.20.83.194                                                             0.0%     2   27.9  36.3  27.9  44.8  11.9
 
Able to access it. Using BSNL FTTH(Default DNS:61.1.1.1)

bQe1Zlo.webp
 
Last edited by a moderator:
Screenshot-2020-12-24-201725.png


DNS shouldn't matter much here though. It seems to be returning same IP for me as others here.

Not sure whats going on maybe TATA is only filtering Excitel users? One BSNL User here was also facing issues so I'm not sure.

Other sites which should be blocked which run on CF such as link-removed, limetorrents etc load fine on https. Apkpure is also on CF but doesn't load. This is definitely TATA's doing.
 
@JB701 On Excitel. Same routing as yours. It seems to be working on FF but not on chromium based browsers. Same error as yours on those.
Maybe google shenanigans? Although I doubt that. Something sure is messed lol.
 
Last edited:
firefox has tls ech. it is very hard to get around it. chrome is yet to add support for it.
 
Huh TIL
That was an interesting read!

I definitely have ESNI enabled on my desktop FF. Seems like that's the reason I can access the website. Might look into enabling ECH now.
 
Back