bgpreport

Network · data from 2026-11-12

AS48431 MAXNET-AS Bozorg Net-e Aria

Registry name: MAXNET-AS Bozorg Net-e Aria, IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48431, 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.

95.80.140.0/22 Invalid: maxLength Nonecovered by 95.80.136.0/21 95 14% 38
95.80.168.0/22 Invalid: maxLength Nonecovered by 95.80.168.0/21 95 14% 38
95.80.172.0/22 Invalid: maxLength Nonecovered by 95.80.168.0/21 95 14% 38
95.80.186.0/24 Invalid: maxLength Nonecovered by 95.80.184.0/21 95 14% 38
185.57.132.0/23 Invalid: maxLength Nonecovered by 185.57.132.0/22 95 14% 38
185.57.134.0/23 Invalid: maxLength Nonecovered by 185.57.132.0/22 95 14% 38
95.80.128.0/18 Valid RIR databaseRIPE 670 100% 66
95.80.128.0/20 Valid RIR databaseRIPE 670 100% 66
95.80.144.0/20 Valid RIR databaseRIPE 670 100% 66
185.57.132.0/22 Valid RIR databaseRIPE 670 100% 66

AS-SET

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

  • ROA: maxLength6
  • Route object: none6
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: maxLength95.80.140.0/22ROA 95.80.128.0/18 AS48431 has maxLength 18; ROA 95.80.128.0/20 AS48431 has maxLength 20; the route is a /22. Raise the maxLength, or add a ROA for 95.80.140.0/22.95 of 673
Route object: none95.80.140.0/22No route object for it. A route object for 95.80.136.0/21 with origin AS48431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48431 in the RIR database for the space.95 of 673
ROA: maxLength95.80.168.0/22ROA 95.80.128.0/18 AS48431 has maxLength 18; the route is a /22. Raise the maxLength, or add a ROA for 95.80.168.0/22.95 of 673
Route object: none95.80.168.0/22No route object for it. A route object for 95.80.168.0/21 with origin AS48431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48431 in the RIR database for the space.95 of 673
ROA: maxLength95.80.172.0/22ROA 95.80.128.0/18 AS48431 has maxLength 18; the route is a /22. Raise the maxLength, or add a ROA for 95.80.172.0/22.95 of 673
Route object: none95.80.172.0/22No route object for it. A route object for 95.80.168.0/21 with origin AS48431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48431 in the RIR database for the space.95 of 673
ROA: maxLength95.80.186.0/24ROA 95.80.128.0/18 AS48431 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 95.80.186.0/24.95 of 673
Route object: none95.80.186.0/24No route object for it. A route object for 95.80.184.0/21 with origin AS48431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48431 in the RIR database for the space.95 of 673
ROA: maxLength185.57.132.0/23ROA 185.57.132.0/22 AS48431 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 185.57.132.0/23.95 of 673
Route object: none185.57.132.0/23No route object for it. A route object for 185.57.132.0/22 with origin AS48431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48431 in the RIR database for the space.95 of 673
ROA: maxLength185.57.134.0/23ROA 185.57.132.0/22 AS48431 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 185.57.134.0/23.95 of 673
Route object: none185.57.134.0/23No route object for it. A route object for 185.57.132.0/22 with origin AS48431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48431 in the RIR database for the space.95 of 673

Route objects not announced

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

95.80.128.0/19RIPEInvalid: maxLength
95.80.128.0/21RIPEInvalid: maxLength
95.80.136.0/21RIPEInvalid: maxLength
95.80.144.0/21RIPEInvalid: maxLength
95.80.152.0/21RIPEInvalid: maxLength
95.80.160.0/19RIPEInvalid: maxLength
95.80.160.0/20RIPEInvalid: maxLength
95.80.160.0/21RIPEInvalid: maxLength
95.80.168.0/21RIPEInvalid: maxLength
95.80.176.0/20RIPEInvalid: maxLength
95.80.176.0/21RIPEInvalid: maxLength
95.80.184.0/21RIPEInvalid: maxLength
2a00:ff8::/32RIPENo 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.