Network · data from 2026-11-12
AS265350 AS265350 - CSINET Telecom LTDA
Registry name: AS265350 - CSINET Telecom LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265350, 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.
| 168.205.32.0/23 | No ROA | Nonecovered by 168.205.32.0/22 | 668 99% |
| 168.205.34.0/23 | No ROA | Nonecovered by 168.205.32.0/22 | 668 99% |
| 2804:2e84:1f00::/40 | No ROA | Nonecovered by 2804:2e84::/32 | 635 100% |
| 2804:2e84:1f20::/44 | No ROA | Nonecovered by 2804:2e84::/32 | 346 54% |
| 2804:2e84:1fa0::/44 | No ROA | Nonecovered by 2804:2e84::/32 | 346 54% |
| 2804:2e84:1fb0::/44 | No ROA | Nonecovered by 2804:2e84::/32 | 346 54% |
| 168.205.32.0/22 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 2804:2e84::/32 | No ROA | Other IRR onlyRADB, TC | 634 100% |
AS-SET
AS265350 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 16 are in fix.csv.
- ROA: none8
- Route object: none6
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 168.205.32.0/23 | No ROA covers it. Add a ROA for AS265350, maxLength 23. |
| Route object: none | 168.205.32.0/23 | No route object for it. A route object for 168.205.32.0/22 with origin AS265350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265350 in the RIR database for the space. |
| ROA: none | 168.205.34.0/23 | No ROA covers it. Add a ROA for AS265350, maxLength 23. |
| Route object: none | 168.205.34.0/23 | No route object for it. A route object for 168.205.32.0/22 with origin AS265350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265350 in the RIR database for the space. |
| ROA: none | 2804:2e84:1f00::/40 | No ROA covers it. Add a ROA for AS265350, maxLength 40. |
| Route object: none | 2804:2e84:1f00::/40 | No route object for it. A route object for 2804:2e84::/32 with origin AS265350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265350 in the RIR database for the space. |
| ROA: none | 2804:2e84:1f20::/44 | No ROA covers it. Add a ROA for AS265350, maxLength 44. |
| Route object: none | 2804:2e84:1f20::/44 | No route object for it. A route object for 2804:2e84::/32 with origin AS265350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265350 in the RIR database for the space. |
| ROA: none | 2804:2e84:1fa0::/44 | No ROA covers it. Add a ROA for AS265350, maxLength 44. |
| Route object: none | 2804:2e84:1fa0::/44 | No route object for it. A route object for 2804:2e84::/32 with origin AS265350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265350 in the RIR database for the space. |
| ROA: none | 2804:2e84:1fb0::/44 | No ROA covers it. Add a ROA for AS265350, maxLength 44. |
| Route object: none | 2804:2e84:1fb0::/44 | No route object for it. A route object for 2804:2e84::/32 with origin AS265350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265350 in the RIR database for the space. |
| ROA: none | 168.205.32.0/22 | No ROA covers it. Add a ROA for AS265350, maxLength 22. |
| Route object: RIR | 168.205.32.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:2e84::/32 | No ROA covers it. Add a ROA for AS265350, maxLength 32. |
| Route object: RIR | 2804:2e84::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS265350 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.