bgpreport

Network · data from 2026-11-12

AS52675 AS52675 - Pronet Provedor Network Ltda -Me

Registry name: AS52675 - Pronet Provedor Network Ltda -Me, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52675, 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.
177.66.180.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 66
177.66.180.0/23 No ROA Other IRR onlyALTDB 671 100% 66
177.66.182.0/23 No ROA Other IRR onlyALTDB 671 100% 66
177.66.180.0/24 No ROA Other IRR onlyALTDB, RADB 2 0%low visibility 3
177.66.181.0/24 No ROA Other IRR onlyALTDB, RADB 2 0%low visibility 3
177.66.183.0/24 No ROA Other IRR onlyALTDB, RADB 2 0%low visibility 3

AS-SET

AS52675 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 13 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none177.66.180.0/22No ROA covers it. Add a ROA for AS52675, maxLength 22.671 of 673
Route object: RIR177.66.180.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.66.180.0/23No ROA covers it. Add a ROA for AS52675, maxLength 23.671 of 673
Route object: RIR177.66.180.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none177.66.182.0/23No ROA covers it. Add a ROA for AS52675, maxLength 23.671 of 673
Route object: RIR177.66.182.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none177.66.180.0/24No ROA covers it. Add a ROA for AS52675, maxLength 24.2 of 673
Route object: RIR177.66.180.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
ROA: none177.66.181.0/24No ROA covers it. Add a ROA for AS52675, maxLength 24.2 of 673
Route object: RIR177.66.181.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673
ROA: none177.66.183.0/24No ROA covers it. Add a ROA for AS52675, maxLength 24.2 of 673
Route object: RIR177.66.183.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

177.66.182.0/24ALTDB, RADBNo 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.