Network · data from 2026-11-12
AS272119 AS272119 - GTITHOST C.A
Registry name: AS272119 - GTITHOST C.A, VE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272119, 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.
| 38.51.57.0/24 | No ROA | Nonecovered by 38.51.56.0/22 | 666 99% |
| 38.51.58.0/24 | No ROA | Nonecovered by 38.51.56.0/22 | 666 99% |
| 38.51.56.0/24 | No ROA | Nonecovered by 38.51.56.0/22 | 2 0%low visibility |
| 38.51.59.0/24 | No ROA | Nonecovered by 38.51.56.0/22 | 2 0%low visibility |
| 38.51.56.0/22 | No ROA | Other IRR onlyRADB | 668 99% |
| 2803:cf10:2000::/35 | Valid | Nonecovered by 2803:cf10::/32 | 631 99% |
| 2803:cf10:e000::/35 | Valid | Nonecovered by 2803:cf10::/32 | 631 99% |
| 2803:cf10::/35 | Valid | Nonecovered by 2803:cf10::/32 | 1 0%low visibility |
| 2803:cf10::/32 | Valid | RIR databaseLACNIC | 631 99% |
AS-SET
AS272119 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: none5
- Route object: none7
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.51.57.0/24 | No ROA covers it. Add a ROA for AS272119, maxLength 24. |
| Route object: none | 38.51.57.0/24 | No route object for it. A route object for 38.51.56.0/22 with origin AS272119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272119 in the RIR database for the space. |
| ROA: none | 38.51.58.0/24 | No ROA covers it. Add a ROA for AS272119, maxLength 24. |
| Route object: none | 38.51.58.0/24 | No route object for it. A route object for 38.51.56.0/22 with origin AS272119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272119 in the RIR database for the space. |
| ROA: none | 38.51.56.0/24 | No ROA covers it. Add a ROA for AS272119, maxLength 24. |
| Route object: none | 38.51.56.0/24 | No route object for it. A route object for 38.51.56.0/22 with origin AS272119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272119 in the RIR database for the space. |
| ROA: none | 38.51.59.0/24 | No ROA covers it. Add a ROA for AS272119, maxLength 24. |
| Route object: none | 38.51.59.0/24 | No route object for it. A route object for 38.51.56.0/22 with origin AS272119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272119 in the RIR database for the space. |
| ROA: none | 38.51.56.0/22 | No ROA covers it. Add a ROA for AS272119, maxLength 22. |
| Route object: RIR | 38.51.56.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2803:cf10:2000::/35 | No route object for it. A route object for 2803:cf10::/32 with origin AS272119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272119 in the RIR database for the space. |
| Route object: none | 2803:cf10:e000::/35 | No route object for it. A route object for 2803:cf10::/32 with origin AS272119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272119 in the RIR database for the space. |
| Route object: none | 2803:cf10::/35 | No route object for it. A route object for 2803:cf10::/32 with origin AS272119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272119 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS272119 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.