bgpreport

Network · data from 2026-11-12

AS52575 Clara Luz Internet

Registry name: AS52575 - Clara Luz Internet Ltda ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52575, 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.86.184.0/21 Valid Other IRR onlyRADB, TC 672 100% 66
177.86.187.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
177.86.185.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
2804:cec::/32 Valid Other IRR onlyRADB, TC 635 100% 67
177.86.184.0/22 Valid Other IRR onlyTC 197 29% 54
177.86.184.0/23 Valid Other IRR onlyTC 197 29% 54
177.86.186.0/23 Valid Other IRR onlyTC 197 29% 54
177.86.186.0/24 Valid Other IRR onlyRADB, TC 197 29% 54
177.86.188.0/22 Valid Other IRR onlyTC 197 29% 54
177.86.188.0/23 Valid Other IRR onlyTC 197 29% 54
177.86.190.0/23 Valid Other IRR onlyTC 197 29% 54

AS-SET

AS52575'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 11 are in fix.csv.

  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: RIR177.86.184.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.86.187.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.86.185.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:cec::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR177.86.184.0/22Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR177.86.184.0/23Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR177.86.186.0/23Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR177.86.186.0/24Route object only in RADB, TC. Add it in the RIR database for the space.197 of 673
Route object: RIR177.86.188.0/22Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR177.86.188.0/23Route object only in TC. Add it in the RIR database for the space.197 of 673
Route object: RIR177.86.190.0/23Route object only in TC. Add it in the RIR database for the space.197 of 673

Route objects not announced

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