Network · data from 2026-11-12
AS263434 Akto Tecnologia
Registry name: AS263434 - Akto Tecnologia - EIRELI - EPP, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263434, 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:11b8:254::c/126 | No ROA | Nonecovered by 2804:11b8::/33 | 2 0%low visibility |
| 206.85.4.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 206.85.7.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 177.53.236.0/22 | No ROA | Other IRR onlyRADB, TC | 671 100% |
| 177.53.237.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 177.53.239.0/24 | No ROA | Other IRR onlyRADB | 667 99% |
| 2804:11b8::/32 | No ROA | Other IRR onlyRADB, TC | 635 100% |
| 2804:11b8::/33 | No ROA | Other IRR onlyRADB, TC | 635 100% |
| 2804:11b8:8000::/33 | No ROA | Other IRR onlyRADB, TC | 635 100% |
| 2804:11b8:ffaa:1::/64 | No ROA | Other IRR onlyRADB | 5 1%low visibility |
AS-SET
AS263434'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 24 are in fix.csv.
- ROA: none10
- Route object: none1
- Route object: RIR9
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:11b8:254::c/126 | No ROA covers it. Add a ROA for AS263434, maxLength 126. |
| Route object: none | 2804:11b8:254::c/126 | No route object for it. A route object for 2804:11b8::/33 with origin AS263434 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS263434 in the RIR database for the space. |
| ROA: none | 206.85.4.0/22 | No ROA covers it. Add a ROA for AS263434, maxLength 22. |
| Route object: RIR | 206.85.4.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.85.7.0/24 | No ROA covers it. Add a ROA for AS263434, maxLength 24. |
| Route object: RIR | 206.85.7.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.53.236.0/22 | No ROA covers it. Add a ROA for AS263434, maxLength 22. |
| Route object: RIR | 177.53.236.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 177.53.237.0/24 | No ROA covers it. Add a ROA for AS263434, maxLength 24. |
| Route object: RIR | 177.53.237.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 177.53.239.0/24 | No ROA covers it. Add a ROA for AS263434, maxLength 24. |
| Route object: RIR | 177.53.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:11b8::/32 | No ROA covers it. Add a ROA for AS263434, maxLength 32. |
| Route object: RIR | 2804:11b8::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:11b8::/33 | No ROA covers it. Add a ROA for AS263434, maxLength 33. |
| Route object: RIR | 2804:11b8::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:11b8:8000::/33 | No ROA covers it. Add a ROA for AS263434, maxLength 33. |
| Route object: RIR | 2804:11b8:8000::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:11b8:ffaa:1::/64 | No ROA covers it. Add a ROA for AS263434, maxLength 64. |
| Route object: RIR | 2804:11b8:ffaa:1::/64 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263434 whose prefix no peer sees AS263434 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.53.236.0/23 | TC | No ROA |
| 177.53.236.0/24 | RADB | No ROA |
| 177.53.238.0/23 | TC | No ROA |
| 177.53.238.0/24 | RADB | No 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.