bgpreport

Network · data from 2026-11-12

AS263121 AS263121 - Atende Telecom LTDA

Registry name: AS263121 - Atende Telecom LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263121, 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.
2804:1218:5000::/36 No ROA Other origin only 586 92% 69
177.22.188.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.22.189.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.22.190.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.22.191.0/24 No ROA Other IRR onlyRADB 672 100% 66
2804:1718::/32 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

AS263121 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: none1
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:1218:5000::/36No ROA covers it. Add a ROA for AS263121, maxLength 36.586 of 636
Route object: none2804:1218:5000::/36Route objects for it name AS263456. Add a route object with origin AS263121 in the RIR database for the space.586 of 636
ROA: none177.22.188.0/24No ROA covers it. Add a ROA for AS263121, maxLength 24.672 of 673
Route object: RIR177.22.188.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.22.189.0/24No ROA covers it. Add a ROA for AS263121, maxLength 24.672 of 673
Route object: RIR177.22.189.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.22.190.0/24No ROA covers it. Add a ROA for AS263121, maxLength 24.672 of 673
Route object: RIR177.22.190.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.22.191.0/24No ROA covers it. Add a ROA for AS263121, maxLength 24.672 of 673
Route object: RIR177.22.191.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:1718::/32No ROA covers it. Add a ROA for AS263121, maxLength 32.635 of 636
Route object: RIR2804:1718::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

177.22.188.0/22RADBNo 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.