bgpreport

Network · data from 2026-11-12

AS53006 AS53006 - ALGAR TELECOM S/A

Registry name: AS53006 - ALGAR TELECOM S/A, BR · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No 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 AS53006, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS53006, 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.
189.41.0.0/16 No ROA Other IRR onlyRADB 672 100% 67
177.106.0.0/16 No ROA Other IRR onlyRADB 671 100% 67
177.191.0.0/16 No ROA Other IRR onlyRADB 671 100% 67
179.104.0.0/16 No ROA Other IRR onlyRADB 671 100% 67
179.126.0.0/16 No ROA Other IRR onlyRADB 671 100% 67
186.210.0.0/16 No ROA Other IRR onlyRADB 671 100% 67
189.15.0.0/16 No ROA Other IRR onlyRADB 671 100% 67
191.54.0.0/15 No ROA Other IRR onlyRADB 671 100% 67
2804:1e68::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

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

  • ROA: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none189.41.0.0/16No ROA covers it. Add a ROA for AS53006, maxLength 16.672 of 673
Route object: RIR189.41.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.106.0.0/16No ROA covers it. Add a ROA for AS53006, maxLength 16.671 of 673
Route object: RIR177.106.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.191.0.0/16No ROA covers it. Add a ROA for AS53006, maxLength 16.671 of 673
Route object: RIR177.191.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none179.104.0.0/16No ROA covers it. Add a ROA for AS53006, maxLength 16.671 of 673
Route object: RIR179.104.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none179.126.0.0/16No ROA covers it. Add a ROA for AS53006, maxLength 16.671 of 673
Route object: RIR179.126.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none186.210.0.0/16No ROA covers it. Add a ROA for AS53006, maxLength 16.671 of 673
Route object: RIR186.210.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none189.15.0.0/16No ROA covers it. Add a ROA for AS53006, maxLength 16.671 of 673
Route object: RIR189.15.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none191.54.0.0/15No ROA covers it. Add a ROA for AS53006, maxLength 15.671 of 673
Route object: RIR191.54.0.0/15Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:1e68::/32No ROA covers it. Add a ROA for AS53006, maxLength 32.636 of 636
Route object: RIR2804:1e68::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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