Unable to update debian servers, goes till singapore via traceroute and then stops, nothing

  • Thread starter Thread starter shirishag75
  • Start date Start date
  • Replies Replies 2
  • Views Views 863

shirishag75

Regular
Messages
247
Location
NA
ISP
BSNL dataone
From last couple of days haven't been able to update my debian installation. While running update I get the -


But I am not using any proxy or something else. I do a daily FUP but have passed it quite some time back and declined increased FUP.

Am able to torrent, wget stuff just apt update doesn't work (which was working.)

traceroute to 151.101.8.204 (151.101.8.204), 30 hops max, 60 byte packets
3 218.248.164.82 (218.248.164.82) 23.243 ms 24.867 ms 27.077 ms
4 218.248.235.197 (218.248.235.197) 33.597 ms 35.702 ms *
5 218.248.235.198 (218.248.235.198) 42.236 ms 66.139 ms *
6 115.113.165.93.static-mumbai.vsnl.net.in (115.113.165.93) 48.830 ms 115.114.89.149.static-Mumbai.vsnl.net.in (115.114.89.149) 12.357 ms 10.345 ms
7 172.23.78.233 (172.23.78.233) 13.858 ms 15.971 ms 19.457 ms
8 172.31.244.45 (172.31.244.45) 38.207 ms 40.569 ms 43.184 ms
9 ix-ae-4-2.tcore2.cxr-chennai.as6453.net (180.87.37.1) 45.813 ms 66.518 ms 50.928 ms
10 if-ae-10-2.tcore2.svw-singapore.as6453.net (180.87.37.65) 95.576 ms if-ae-3-3.tcore1.cxr-chennai.as6453.net (180.87.36.5) 94.641 ms 97.952 ms
11 if-ae-34-2.tcore1.svq-singapore.as6453.net (180.87.36.41) 69.122 ms 71.938 ms 74.665 ms
12 if-ae-11-2.thar1.svq-singapore.as6453.net (180.87.98.37) 69.094 ms if-ae-7-2.thar1.svq-singapore.as6453.net (180.87.98.9) 71.561 ms 74.149 ms
13 ae-9.a01.sngpsi07.sg.bb.gin.ntt.net (129.250.8.241) 76.513 ms 77.152 ms 78.242 ms
14 ae-5.r00.sngpsi07.sg.bb.gin.ntt.net (129.250.2.123) 89.208 ms ae-5.r01.sngpsi07.sg.bb.gin.ntt.net (129.250.2.241) 88.765 ms ae (129.250.2.123) 89.878 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

the IP or IP pool is of a server which serves debian updates. The only thing I have not shared are the first two hops which basically gives my gateway to local BSNL exchange traffic (Pune) and from Pune hop to Bombay/Mumbai on BSNL's own network.
 
It is a common issue with all distros* irrespective of ISP.

Quick solution is to use a (free) VPN for anything related to apt.

Recommended solution is to use a stable mirror that can be found only on trial and error method.
 
Change the update mirror as @pothi said. It is not an ISP issue. The problem is in the update mirror. I faced similar problem in my Centos server a few months back.
 

Top