bgpreport

Network · data from 2026-11-12

AS61744 power net telecom eireli-me

Registry name: AS61744 - power net telecom eireli-me, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61744, 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.
131.72.131.0/24 Valid Nonecovered by 131.72.128.0/22 672 100% 67
2804:1bb4:fc00::/46 Valid Nonecovered by 2804:1bb4::/32 634 100% 67
131.72.130.0/23 Valid Nonecovered by 131.72.128.0/22 127 19% 44
131.72.128.0/23 Valid Nonecovered by 131.72.128.0/22 126 19% 44
2804:1bb4::/33 Valid Nonecovered by 2804:1bb4::/32 116 18% 43
2804:1bb4:8000::/33 Valid Nonecovered by 2804:1bb4::/32 116 18% 43
131.72.128.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
131.72.129.0/24 Valid Other IRR onlyRADB 672 100% 67
131.72.130.0/24 Valid Other IRR onlyBBOI, NTTCOM 666 99% 67
2804:1bb4::/32 Valid Other IRR onlyRADB, TC 636 100% 67

AS-SET

AS61744'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 10 are in fix.csv.

  • Route object: none6
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none131.72.131.0/24No route object for it. A route object for 131.72.128.0/22 with origin AS61744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61744 in the RIR database for the space.672 of 673
Route object: none2804:1bb4:fc00::/46No route object for it. A route object for 2804:1bb4::/32 with origin AS61744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61744 in the RIR database for the space.634 of 636
Route object: none131.72.130.0/23No route object for it. A route object for 131.72.128.0/22 with origin AS61744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61744 in the RIR database for the space.127 of 673
Route object: none131.72.128.0/23No route object for it. A route object for 131.72.128.0/22 with origin AS61744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61744 in the RIR database for the space.126 of 673
Route object: none2804:1bb4::/33No route object for it. A route object for 2804:1bb4::/32 with origin AS61744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61744 in the RIR database for the space.116 of 636
Route object: none2804:1bb4:8000::/33No route object for it. A route object for 2804:1bb4::/32 with origin AS61744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61744 in the RIR database for the space.116 of 636
Route object: RIR131.72.128.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR131.72.129.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.72.130.0/24Route object only in BBOI, NTTCOM. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:1bb4::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS61744 is announced.

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.