bgpreport

Network · data from 2026-11-12

AS140822 ANPHATIDC-VSIS-AS-VN - ANPHATIDC

Registry name: ANPHATIDC-VSIS-AS-VN - ANPHATIDC, VN · not in PeeringDB

28IPv4 routes 25.0% RPKI valid · 57.1% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
22No ROA 12 with no route object for this origin
22Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS140822, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS140822, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

103.188.164.0/23 No ROA Other origin only 672 100% 67
103.189.72.0/23 No ROA Other origin only 672 100% 67
103.189.74.0/23 No ROA Other origin only 672 100% 67
103.189.76.0/23 No ROA Other origin only 672 100% 67
103.189.78.0/23 No ROA Other origin only 672 100% 67
160.191.36.0/23 No ROA None 632 94% 67
103.175.64.0/23 No ROA None 2 0%low visibility 2
161.248.34.0/23 No ROA None 2 0%low visibility 2
161.248.72.0/23 No ROA None 2 0%low visibility 2
161.248.76.0/23 No ROA None 2 0%low visibility 2
161.248.182.0/23 No ROA None 2 0%low visibility 2
161.248.236.0/23 No ROA None 2 0%low visibility 2
103.176.150.0/23 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.180.142.0/23 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.180.144.0/23 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.180.154.0/23 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.180.158.0/23 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.183.146.0/23 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.183.152.0/23 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.185.186.0/23 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
103.175.144.0/23 No ROA RIR databaseAPNIC 2 0%low visibility 2
2407:c340::/48 No ROA RIR databaseAPNIC, NTTCOM 1 0%low visibility 1
103.169.168.0/23 Valid RIR databaseAPNIC 673 100% 66
103.175.66.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
103.175.68.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
103.175.142.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
103.180.156.0/23 Valid RIR databaseAPNIC, NTTCOM 2 0%low visibility 2
103.183.148.0/23 Valid RIR databaseAPNIC, NTTCOM 2 0%low visibility 2
103.183.150.0/23 Valid RIR databaseAPNIC, NTTCOM 2 0%low visibility 2

AS-SET

AS140822 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 50 are in fix.csv.

  • ROA: none22
  • Route object: none12
  • Route object: RIR8
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none103.188.164.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.672 of 673
Route object: none103.188.164.0/23Route objects for it name AS135905. Add a route object with origin AS140822 in the RIR database for the space.672 of 673
ROA: none103.189.72.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.672 of 673
Route object: none103.189.72.0/23Route objects for it name AS135905. Add a route object with origin AS140822 in the RIR database for the space.672 of 673
ROA: none103.189.74.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.672 of 673
Route object: none103.189.74.0/23Route objects for it name AS135905. Add a route object with origin AS140822 in the RIR database for the space.672 of 673
ROA: none103.189.76.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.672 of 673
Route object: none103.189.76.0/23Route objects for it name AS135905. Add a route object with origin AS140822 in the RIR database for the space.672 of 673
ROA: none103.189.78.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.672 of 673
Route object: none103.189.78.0/23Route objects for it name AS135905. Add a route object with origin AS140822 in the RIR database for the space.672 of 673
ROA: none160.191.36.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.632 of 673
Route object: none160.191.36.0/23No route object for it. Add a route object with origin AS140822 in the RIR database for the space.632 of 673
ROA: none103.175.64.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: none103.175.64.0/23No route object for it. Add a route object with origin AS140822 in the RIR database for the space.2 of 673
ROA: none161.248.34.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: none161.248.34.0/23No route object for it. Add a route object with origin AS140822 in the RIR database for the space.2 of 673
ROA: none161.248.72.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: none161.248.72.0/23No route object for it. Add a route object with origin AS140822 in the RIR database for the space.2 of 673
ROA: none161.248.76.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: none161.248.76.0/23No route object for it. Add a route object with origin AS140822 in the RIR database for the space.2 of 673
ROA: none161.248.182.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: none161.248.182.0/23No route object for it. Add a route object with origin AS140822 in the RIR database for the space.2 of 673
ROA: none161.248.236.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: none161.248.236.0/23No route object for it. Add a route object with origin AS140822 in the RIR database for the space.2 of 673
ROA: none103.176.150.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: RIR103.176.150.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.180.142.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: RIR103.180.142.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.180.144.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: RIR103.180.144.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.180.154.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: RIR103.180.154.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.180.158.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: RIR103.180.158.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.183.146.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: RIR103.183.146.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.183.152.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: RIR103.183.152.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.185.186.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
Route object: RIR103.185.186.0/23Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none103.175.144.0/23No ROA covers it. Add a ROA for AS140822, maxLength 23.2 of 673
ROA: none2407:c340::/48No ROA covers it. Add a ROA for AS140822, maxLength 48.1 of 636

Route objects not announced

Route objects with origin AS140822 whose prefix no peer sees AS140822 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.171.112.0/23APNICInvalid: origin
103.172.234.0/23APNICInvalid: origin
103.174.74.0/23APNICInvalid: origin
103.176.150.0/24NTTCOMNo ROA
103.176.151.0/24NTTCOMNo ROA
160.187.244.0/23APNICValid
2400:1060::/48APNICInvalid: origin
2407:db40::/48APNICInvalid: origin

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.