Network · data from 2026-11-12
AS26955 ITAGROUP-AS - ITA GROUP
Registry name: ITAGROUP-AS - ITA GROUP, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26955, 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.
| 162.223.132.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 162.223.133.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 162.223.134.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 209.180.44.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 65.121.140.0/24 | Valid | RIR databaseARIN | 671 100% |
| 65.127.129.0/24 | Valid | RIR databaseARIN | 671 100% |
| 207.108.43.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS26955 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: none4
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 162.223.132.0/24 | No ROA covers it. Add a ROA for AS26955, maxLength 24. |
| ROA: none | 162.223.133.0/24 | No ROA covers it. Add a ROA for AS26955, maxLength 24. |
| ROA: none | 162.223.134.0/23 | No ROA covers it. Add a ROA for AS26955, maxLength 23. |
| ROA: none | 209.180.44.0/24 | No ROA covers it. Add a ROA for AS26955, maxLength 24. |
Route objects not announced
Route objects with origin AS26955 whose prefix no peer sees AS26955 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.94.177.0/24 | RADB | No ROA |
| 162.223.134.0/24 | ARIN | No ROA |
| 162.223.135.0/24 | ARIN | No ROA |
| 2001:470:184::/48 | ARIN | Valid |
| 2620:117:7000::/40 | ARIN | No ROA |
| 2620:117:7001::/48 | ARIN | No ROA |
| 2620:117:700f::/48 | ARIN | No ROA |
| 2620:117:70f0::/48 | ARIN | No ROA |
| 2620:117:70ff::/48 | ARIN | 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.