bgpreport

Network · data from 2026-11-12

AS265291 MP NET

Registry name: AS265291 - MP NET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265291, 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.
45.166.34.0/24 No ROA Nonecovered by 45.166.34.0/23 672 100% 67
45.166.32.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
45.166.32.0/23 No ROA Other IRR onlyRADB 672 100% 67
45.166.33.0/24 No ROA Other IRR onlyRADB 672 100% 67
45.166.34.0/23 No ROA Other IRR onlyRADB 672 100% 67
45.166.35.0/24 No ROA Other IRR onlyRADB 672 100% 67
2804:5560::/33 No ROA Other IRR onlyRADB 635 100% 68
2804:5560:8000::/33 No ROA Other IRR onlyRADB 635 100% 68

AS-SET

AS265291's PeeringDB record names no 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 18 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.166.34.0/24No ROA covers it. Add a ROA for AS265291, maxLength 24.672 of 673
Route object: none45.166.34.0/24No route object for it. A route object for 45.166.34.0/23 with origin AS265291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265291 in the RIR database for the space.672 of 673
ROA: none45.166.32.0/22No ROA covers it. Add a ROA for AS265291, maxLength 22.672 of 673
Route object: RIR45.166.32.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.166.32.0/23No ROA covers it. Add a ROA for AS265291, maxLength 23.672 of 673
Route object: RIR45.166.32.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.166.33.0/24No ROA covers it. Add a ROA for AS265291, maxLength 24.672 of 673
Route object: RIR45.166.33.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.166.34.0/23No ROA covers it. Add a ROA for AS265291, maxLength 23.672 of 673
Route object: RIR45.166.34.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.166.35.0/24No ROA covers it. Add a ROA for AS265291, maxLength 24.672 of 673
Route object: RIR45.166.35.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:5560::/33No ROA covers it. Add a ROA for AS265291, maxLength 33.635 of 636
Route object: RIR2804:5560::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:5560:8000::/33No ROA covers it. Add a ROA for AS265291, maxLength 33.635 of 636
Route object: RIR2804:5560:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.166.32.0/24RADBNo ROA
2804:5560::/32RADB, TCNo 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.