bgpreport

Network · data from 2026-11-12

AS265398 nobre telecom

Registry name: AS265398 - nobre telecom ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265398, 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.
170.254.146.0/23 Valid Nonecovered by 170.254.144.0/22 671 100% 67
170.254.144.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
170.254.144.0/23 Valid Other IRR onlyRADB 672 100% 67
2804:3378::/32 Valid Other IRR onlyRADB 635 100% 67
170.254.144.0/24 Valid Other IRR onlyRADB 186 28% 53
170.254.145.0/24 Valid Other IRR onlyRADB 185 27% 53
170.254.146.0/24 Valid Other IRR onlyRADB 185 27% 53
170.254.147.0/24 Valid Other IRR onlyRADB 185 27% 53

AS-SET

AS265398'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 8 are in fix.csv.

  • Route object: none1
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: none170.254.146.0/23No route object for it. A route object for 170.254.144.0/22 with origin AS265398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265398 in the RIR database for the space.671 of 673
Route object: RIR170.254.144.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.254.144.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:3378::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR170.254.144.0/24Route object only in RADB. Add it in the RIR database for the space.186 of 673
Route object: RIR170.254.145.0/24Route object only in RADB. Add it in the RIR database for the space.185 of 673
Route object: RIR170.254.146.0/24Route object only in RADB. Add it in the RIR database for the space.185 of 673
Route object: RIR170.254.147.0/24Route object only in RADB. Add it in the RIR database for the space.185 of 673

Route objects not announced

Every route object with origin AS265398 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.