bgpreport

Network · data from 2026-11-12

AS135921 MAXSERVER-AS-VN - Maxserver Company Limited

Registry name: MAXSERVER-AS-VN - Maxserver Company Limited, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135921, 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.
2407:f1c0::/48 Valid Nonecovered by 2407:f1c0::/32 636 100% 69
2407:f1c0:1000::/36 Valid Nonecovered by 2407:f1c0::/32 636 100% 69
2407:f1c0:2000::/36 Valid Nonecovered by 2407:f1c0::/32 636 100% 69
2407:f1c0:3000::/36 Valid Nonecovered by 2407:f1c0::/32 636 100% 69
2407:f1c0:4000::/36 Valid Nonecovered by 2407:f1c0::/32 636 100% 69
103.45.232.0/22 Valid RIR databaseAPNIC 669 99% 67
103.69.188.0/22 Valid RIR databaseAPNIC 669 99% 67
103.98.148.0/22 Valid RIR databaseAPNIC, NTTCOM 669 99% 67

AS-SET

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

  • Route object: none5
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none2407:f1c0::/48No route object for it. A route object for 2407:f1c0::/32 with origin AS135921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135921 in the RIR database for the space.636 of 636
Route object: none2407:f1c0:1000::/36No route object for it. A route object for 2407:f1c0::/32 with origin AS135921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135921 in the RIR database for the space.636 of 636
Route object: none2407:f1c0:2000::/36No route object for it. A route object for 2407:f1c0::/32 with origin AS135921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135921 in the RIR database for the space.636 of 636
Route object: none2407:f1c0:3000::/36No route object for it. A route object for 2407:f1c0::/32 with origin AS135921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135921 in the RIR database for the space.636 of 636
Route object: none2407:f1c0:4000::/36No route object for it. A route object for 2407:f1c0::/32 with origin AS135921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135921 in the RIR database for the space.636 of 636

Route objects not announced

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

103.45.232.0/23APNICValid
103.45.232.0/24APNICValid
103.45.233.0/24APNICValid
103.45.234.0/23APNICValid
103.45.234.0/24APNICValid
103.45.235.0/24APNICValid
103.109.148.0/22NTTCOMNo ROA
103.109.148.0/23NTTCOMNo ROA
103.109.149.0/24NTTCOMNo ROA
103.109.150.0/23NTTCOMNo ROA
103.109.150.0/24NTTCOMNo ROA
2407:f1c0::/32APNICNo 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.