bgpreport

Network · data from 2026-11-12

AS52841 Aprimorar

Registry name: AS52841 - APRIMORAR SUPORTE E TELEATENDIMENTO LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52841, 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.26.0/23 No ROA Other IRR onlyRADB, TC 673 100% 66
177.66.24.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
177.66.24.0/23 No ROA Other IRR onlyRADB, TC 672 100% 66
2804:be8::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:be8::/33 No ROA Other IRR onlyRADB 635 100% 67
2804:be8:8000::/33 No ROA Other IRR onlyRADB 635 100% 67
2804:be8:843d::/48 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS52841'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 18 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none177.66.26.0/23No ROA covers it. Add a ROA for AS52841, maxLength 23.673 of 673
Route object: RIR177.66.26.0/23Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
ROA: none177.66.24.0/22No ROA covers it. Add a ROA for AS52841, maxLength 22.672 of 673
Route object: RIR177.66.24.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.66.24.0/23No ROA covers it. Add a ROA for AS52841, maxLength 23.672 of 673
Route object: RIR177.66.24.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:be8::/32No ROA covers it. Add a ROA for AS52841, maxLength 32.635 of 636
Route object: RIR2804:be8::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:be8::/33No ROA covers it. Add a ROA for AS52841, maxLength 33.635 of 636
Route object: RIR2804:be8::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:be8:8000::/33No ROA covers it. Add a ROA for AS52841, maxLength 33.635 of 636
Route object: RIR2804:be8:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:be8:843d::/48No ROA covers it. Add a ROA for AS52841, maxLength 48.634 of 636
Route object: RIR2804:be8:843d::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

177.66.24.0/24TCNo ROA
177.66.25.0/24TCNo ROA
177.66.26.0/24TCNo ROA
177.66.27.0/24TCNo 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.