bgpreport

Network · data from 2026-11-12

AS140770 DIGILIFE-AS-VN - Digilife Vietnam Digital Services Company Limited

Registry name: DIGILIFE-AS-VN - Digilife Vietnam Digital Services Company Limited, VN · not in PeeringDB

7IPv4 routes 85.7% RPKI valid · 85.7% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS140770, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS140770, 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.220.85.0/24 Invalid: origin Other origin only 35 5%low visibility 28
103.161.38.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.161.39.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.165.142.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.165.143.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.176.144.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.176.145.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
2400:32e0::/48 Valid RIR databaseAPNIC, NTTCOM 635 100% 69
2407:4940::/48 Valid RIR databaseAPNIC, NTTCOM 635 100% 69

AS-SET

AS140770 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 7 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin103.220.85.0/24ROAs covering it name AS63743, not AS140770. If AS140770 should announce it, add a ROA for AS140770.35 of 673
Route object: none103.220.85.0/24Route objects for it name AS63743. Add a route object with origin AS140770 in the RIR database for the space.35 of 673

Route objects not announced

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

103.140.101.0/24RADBNo ROA
103.161.38.0/23APNIC, NTTCOMValid
103.165.142.0/23APNIC, NTTCOMValid
103.176.144.0/23APNIC, NTTCOMValid
2406:fa40::/48NTTCOMNo ROA

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.