bgpreport

Network · data from 2026-11-12

AS132434 MAXIS-AS2-AP - MaxisNet International Internet Gateway

Registry name: MAXIS-AS2-AP - MaxisNet International Internet Gateway, MY · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132434, 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.21.33.0/24 No ROA Nonecovered by 103.21.32.0/23 672 100% 66
103.21.34.0/24 No ROA Nonecovered by 103.21.32.0/22 672 100% 66
103.21.35.0/24 No ROA Nonecovered by 103.21.32.0/22 672 100% 66
116.204.203.0/24 No ROA Nonecovered by 116.204.202.0/23 672 100% 66
2405:3240::/36 No ROA None 523 82% 67
103.21.32.0/22 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
103.21.32.0/24 No ROA Other IRR onlyRADB 672 100% 66
116.204.200.0/24 No ROA Other IRR onlyRADB 672 100% 66
116.204.201.0/24 No ROA Other IRR onlyRADB 672 100% 66
116.204.202.0/24 No ROA Other IRR onlyRADB 672 100% 66
141.193.41.0/24 No ROA Other IRR onlyRADB 672 100% 66
141.193.42.0/24 No ROA Other IRR onlyRADB 672 100% 66
141.193.43.0/24 No ROA Other IRR onlyRADB 672 100% 66
141.193.40.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

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

  • ROA: none14
  • Route object: none5
  • Route object: RIR9
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none103.21.33.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: none103.21.33.0/24No route object for it. A route object for 103.21.32.0/23 with origin AS132434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132434 in the RIR database for the space.672 of 673
ROA: none103.21.34.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: none103.21.34.0/24No route object for it. A route object for 103.21.32.0/22 with origin AS132434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132434 in the RIR database for the space.672 of 673
ROA: none103.21.35.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: none103.21.35.0/24No route object for it. A route object for 103.21.32.0/22 with origin AS132434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132434 in the RIR database for the space.672 of 673
ROA: none116.204.203.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: none116.204.203.0/24No route object for it. A route object for 116.204.202.0/23 with origin AS132434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132434 in the RIR database for the space.672 of 673
ROA: none2405:3240::/36No ROA covers it. Add a ROA for AS132434, maxLength 36.523 of 636
Route object: none2405:3240::/36No route object for it. Add a route object with origin AS132434 in the RIR database for the space.523 of 636
ROA: none103.21.32.0/22No ROA covers it. Add a ROA for AS132434, maxLength 22.672 of 673
Route object: RIR103.21.32.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.21.32.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: RIR103.21.32.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none116.204.200.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: RIR116.204.200.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none116.204.201.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: RIR116.204.201.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none116.204.202.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: RIR116.204.202.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none141.193.41.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: RIR141.193.41.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none141.193.42.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: RIR141.193.42.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none141.193.43.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.672 of 673
Route object: RIR141.193.43.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none141.193.40.0/24No ROA covers it. Add a ROA for AS132434, maxLength 24.2 of 673
Route object: RIR141.193.40.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

103.21.32.0/23RADBNo ROA
116.204.200.0/22RADBNo ROA
116.204.200.0/23RADBNo ROA
116.204.202.0/23RADBNo ROA
141.193.40.0/22RADBNo ROA
141.193.40.0/23RADBNo ROA
141.193.42.0/23RADBNo 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.