Network · data from 2026-11-12
AS202763 IT-Center-AS INFORMATION TECHNOLOGY CENTER LLC JV
Registry name: IT-Center-AS INFORMATION TECHNOLOGY CENTER LLC JV, UZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202763, 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.
| 91.216.37.0/27 | No ROA | Other origin onlycovered by 91.216.37.0/25 | 36 5%low visibility |
| 91.216.37.32/27 | No ROA | Other origin onlycovered by 91.216.37.0/25 | 36 5%low visibility |
| 91.216.37.64/27 | No ROA | Other origin onlycovered by 91.216.37.0/25 | 36 5%low visibility |
| 91.216.37.96/27 | No ROA | Other origin onlycovered by 91.216.37.0/25 | 36 5%low visibility |
| 91.216.37.128/27 | No ROA | Other origin onlycovered by 91.216.37.128/25 | 36 5%low visibility |
| 91.216.37.160/27 | No ROA | Other origin onlycovered by 91.216.37.128/25 | 36 5%low visibility |
| 91.216.37.192/27 | No ROA | Other origin onlycovered by 91.216.37.128/25 | 36 5%low visibility |
| 91.216.37.224/27 | No ROA | Other origin onlycovered by 91.216.37.128/25 | 36 5%low visibility |
| 91.216.37.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS202763 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 19 are in fix.csv.
- ROA: none9
- Route object: none8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.216.37.0/27 | No ROA covers it. Add a ROA for AS202763, maxLength 27. |
| Route object: none | 91.216.37.0/27 | Route objects for it name AS28910. A route object for 91.216.37.0/25 with origin AS202763 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202763 in the RIR database for the space. |
| ROA: none | 91.216.37.32/27 | No ROA covers it. Add a ROA for AS202763, maxLength 27. |
| Route object: none | 91.216.37.32/27 | Route objects for it name AS28910. A route object for 91.216.37.0/25 with origin AS202763 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202763 in the RIR database for the space. |
| ROA: none | 91.216.37.64/27 | No ROA covers it. Add a ROA for AS202763, maxLength 27. |
| Route object: none | 91.216.37.64/27 | Route objects for it name AS28910. A route object for 91.216.37.0/25 with origin AS202763 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202763 in the RIR database for the space. |
| ROA: none | 91.216.37.96/27 | No ROA covers it. Add a ROA for AS202763, maxLength 27. |
| Route object: none | 91.216.37.96/27 | Route objects for it name AS28910. A route object for 91.216.37.0/25 with origin AS202763 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202763 in the RIR database for the space. |
| ROA: none | 91.216.37.128/27 | No ROA covers it. Add a ROA for AS202763, maxLength 27. |
| Route object: none | 91.216.37.128/27 | Route objects for it name AS28910. A route object for 91.216.37.128/25 with origin AS202763 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202763 in the RIR database for the space. |
| ROA: none | 91.216.37.160/27 | No ROA covers it. Add a ROA for AS202763, maxLength 27. |
| Route object: none | 91.216.37.160/27 | Route objects for it name AS28910. A route object for 91.216.37.128/25 with origin AS202763 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202763 in the RIR database for the space. |
| ROA: none | 91.216.37.192/27 | No ROA covers it. Add a ROA for AS202763, maxLength 27. |
| Route object: none | 91.216.37.192/27 | Route objects for it name AS28910. A route object for 91.216.37.128/25 with origin AS202763 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202763 in the RIR database for the space. |
| ROA: none | 91.216.37.224/27 | No ROA covers it. Add a ROA for AS202763, maxLength 27. |
| Route object: none | 91.216.37.224/27 | Route objects for it name AS28910. A route object for 91.216.37.128/25 with origin AS202763 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202763 in the RIR database for the space. |
| ROA: none | 91.216.37.0/24 | No ROA covers it. Add a ROA for AS202763, maxLength 24. |
Route objects not announced
Route objects with origin AS202763 whose prefix no peer sees AS202763 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.216.37.0/25 | RIPE | No ROA |
| 91.216.37.128/25 | RIPE | 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.