Network · data from 2026-11-12
AS21100 ITL Company AS21100
Registry name: ITLDC-EU ROUTE 95 LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21100, 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.
| 93.187.64.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.62.0.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.161.202.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 45.128.150.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a0e:40c0:2::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 5.34.180.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 5.34.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.118.16.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.118.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.90.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.223.123.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.228.146.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.235.129.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.198.164.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.106.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.238.152.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.123.216.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 195.123.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.123.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.245.112.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.8.245.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.134.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.200.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.208.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.12.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.28.65.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.66.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.68.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.28.69.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.174.172.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.237.206.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 195.54.162.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a02:27af::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2001:67c:2f5c::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:27a9::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:27ab::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a02:27ae::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:c6c0::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:fcc0:3::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS21100'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 5 are in fix.csv.
- ROA: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 93.187.64.0/24 | No ROA covers it. Add a ROA for AS21100, maxLength 24. |
| ROA: none | 185.62.0.0/24 | No ROA covers it. Add a ROA for AS21100, maxLength 24. |
| ROA: none | 193.161.202.0/24 | No ROA covers it. Add a ROA for AS21100, maxLength 24. |
| ROA: none | 45.128.150.0/24 | No ROA covers it. Add a ROA for AS21100, maxLength 24. |
| ROA: none | 2a0e:40c0:2::/48 | No ROA covers it. Add a ROA for AS21100, maxLength 48. |
Route objects not announced
Every route object with origin AS21100 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.