Network · data from 2026-11-12
AS264689 Ubnet Datacenter
Registry name: AS264689 - Luciano Gabriel Chersanaz (Ubnet Datacenter), AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264689, 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.
| 206.0.16.0/24 | No ROA | Nonecovered by 206.0.16.0/23 | 671 100% |
| 206.0.17.0/24 | No ROA | Nonecovered by 206.0.16.0/23 | 671 100% |
| 38.210.216.0/24 | No ROA | Nonecovered by 38.210.216.0/21 | 669 99% |
| 206.0.16.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 38.224.254.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 38.43.79.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 168.228.140.0/24 | Valid | Nonecovered by 168.228.140.0/22 | 671 100% |
| 168.228.141.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 168.228.142.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 168.228.143.0/24 | Valid | Other IRR onlyRADB | 671 100% |
AS-SET
AS264689'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 19 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: RIR6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 206.0.16.0/24 | No ROA covers it. Add a ROA for AS264689, maxLength 24. |
| Route object: none | 206.0.16.0/24 | No route object for it. A route object for 206.0.16.0/23 with origin AS264689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264689 in the RIR database for the space. |
| ROA: none | 206.0.17.0/24 | No ROA covers it. Add a ROA for AS264689, maxLength 24. |
| Route object: none | 206.0.17.0/24 | No route object for it. A route object for 206.0.16.0/23 with origin AS264689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264689 in the RIR database for the space. |
| ROA: none | 38.210.216.0/24 | No ROA covers it. Add a ROA for AS264689, maxLength 24. |
| Route object: none | 38.210.216.0/24 | No route object for it. A route object for 38.210.216.0/21 with origin AS264689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264689 in the RIR database for the space. |
| ROA: none | 206.0.16.0/23 | No ROA covers it. Add a ROA for AS264689, maxLength 23. |
| Route object: RIR | 206.0.16.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.224.254.0/24 | No ROA covers it. Add a ROA for AS264689, maxLength 24. |
| Route object: RIR | 38.224.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.43.79.0/24 | No ROA covers it. Add a ROA for AS264689, maxLength 24. |
| Route object: RIR | 38.43.79.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 168.228.140.0/24 | No route object for it. A route object for 168.228.140.0/22 with origin AS264689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264689 in the RIR database for the space. |
| Route object: RIR | 168.228.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.142.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.143.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264689 whose prefix no peer sees AS264689 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.210.216.0/21 | RADB | No ROA |
| 168.228.140.0/22 | RADB | Valid |
| 206.0.16.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.