bgpreport

Network · data from 2026-11-12

AS269285 AS269285 - Pronetech Fibra

Registry name: AS269285 - Pronetech Fibra, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269285, 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.182.54.0/23 Invalid: maxLength Nonecovered by 45.182.52.0/22 32 5%low visibility 16
45.182.52.0/23 Valid Nonecovered by 45.182.52.0/22 668 99% 67
45.182.52.0/24 Valid Nonecovered by 45.182.52.0/22 668 99% 67
45.182.53.0/24 Valid Nonecovered by 45.182.52.0/22 668 99% 67
45.182.55.0/24 Valid Nonecovered by 45.182.52.0/22 668 99% 67
45.182.54.0/24 Valid Nonecovered by 45.182.52.0/22 667 99% 67
45.182.52.0/22 Valid Other IRR onlyALTDB, RADB 668 99% 67
2804:623c::/32 Valid Other IRR onlyALTDB 635 100% 67

AS-SET

AS269285 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 9 are in fix.csv.

  • ROA: maxLength1
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.182.54.0/23ROA 45.182.52.0/22 AS269285 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 45.182.54.0/23.32 of 673
Route object: none45.182.54.0/23No route object for it. A route object for 45.182.52.0/22 with origin AS269285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269285 in the RIR database for the space.32 of 673
Route object: none45.182.52.0/23No route object for it. A route object for 45.182.52.0/22 with origin AS269285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269285 in the RIR database for the space.668 of 673
Route object: none45.182.52.0/24No route object for it. A route object for 45.182.52.0/22 with origin AS269285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269285 in the RIR database for the space.668 of 673
Route object: none45.182.53.0/24No route object for it. A route object for 45.182.52.0/22 with origin AS269285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269285 in the RIR database for the space.668 of 673
Route object: none45.182.55.0/24No route object for it. A route object for 45.182.52.0/22 with origin AS269285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269285 in the RIR database for the space.668 of 673
Route object: none45.182.54.0/24No route object for it. A route object for 45.182.52.0/22 with origin AS269285 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269285 in the RIR database for the space.667 of 673
Route object: RIR45.182.52.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:623c::/32Route object only in ALTDB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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