Network · data from 2026-11-12
AS265965 AS265965 - Pinhais Net Telecom Comercio e Servicos Ltda
Registry name: AS265965 - Pinhais Net Telecom Comercio e Servicos Ltda, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265965, 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.
| 164.163.173.0/24 | No ROA | Nonecovered by 164.163.172.0/22 | 671 100% |
| 164.163.174.0/24 | No ROA | Other origin onlycovered by 164.163.174.0/23 | 665 99% |
| 164.163.175.0/24 | No ROA | Other origin onlycovered by 164.163.174.0/23 | 664 99% |
| 164.163.172.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 164.163.174.0/23 | No ROA | Other IRR onlyRADB | 667 99% |
| 2804:4088::/40 | No ROA | Other IRR onlyRADB | 635 100% |
| 2804:4088::/32 | No ROA | Other IRR onlyRADB | 634 100% |
AS-SET
AS265965 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 15 are in fix.csv.
- ROA: none7
- Route object: none3
- Route object: RIR4
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 164.163.173.0/24 | No ROA covers it. Add a ROA for AS265965, maxLength 24. |
| Route object: none | 164.163.173.0/24 | No route object for it. A route object for 164.163.172.0/22 with origin AS265965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265965 in the RIR database for the space. |
| ROA: none | 164.163.174.0/24 | No ROA covers it. Add a ROA for AS265965, maxLength 24. |
| Route object: none | 164.163.174.0/24 | Route objects for it name AS272470. A route object for 164.163.174.0/23 with origin AS265965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265965 in the RIR database for the space. |
| ROA: none | 164.163.175.0/24 | No ROA covers it. Add a ROA for AS265965, maxLength 24. |
| Route object: none | 164.163.175.0/24 | Route objects for it name AS272470. A route object for 164.163.174.0/23 with origin AS265965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265965 in the RIR database for the space. |
| ROA: none | 164.163.172.0/24 | No ROA covers it. Add a ROA for AS265965, maxLength 24. |
| Route object: RIR | 164.163.172.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 164.163.174.0/23 | No ROA covers it. Add a ROA for AS265965, maxLength 23. |
| Route object: RIR | 164.163.174.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:4088::/40 | No ROA covers it. Add a ROA for AS265965, maxLength 40. |
| Route object: RIR | 2804:4088::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:4088::/32 | No ROA covers it. Add a ROA for AS265965, maxLength 32. |
| Route object: RIR | 2804:4088::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265965 whose prefix no peer sees AS265965 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 164.163.172.0/22 | 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.