bgpreport

Network · data from 2026-11-12

AS131402 FPTSOFTWARE-AS-VN - FPT Software Company limited

Registry name: FPTSOFTWARE-AS-VN - FPT Software Company limited, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131402, 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.71.180.0/23 No ROA Nonecovered by 103.71.180.0/22 673 100% 66
103.71.180.0/22 No ROA Other IRR onlyRADB 673 100% 66
103.227.216.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
103.227.216.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 66
103.227.218.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 66
103.227.219.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 66
103.227.217.0/24 Valid RIR databaseAPNIC, NTTCOM 672 100% 66
103.71.180.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
103.71.181.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none103.71.180.0/23No ROA covers it. Add a ROA for AS131402, maxLength 23.673 of 673
Route object: none103.71.180.0/23No route object for it. A route object for 103.71.180.0/22 with origin AS131402 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131402 in the RIR database for the space.673 of 673
ROA: none103.71.180.0/22No ROA covers it. Add a ROA for AS131402, maxLength 22.673 of 673
Route object: RIR103.71.180.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

103.227.216.0/23APNICValid
103.227.218.0/23APNICValid

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.