Network · data from 2026-11-12
AS21305 IPTEL-AS IP TelCom LLC
Registry name: IPTEL-AS IP TelCom LLC, BY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21305, 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.125.26.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 93.125.75.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 87.252.236.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 79.98.48.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 79.98.49.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 79.98.50.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 79.98.51.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 79.98.53.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.224.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.225.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.226.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.227.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.228.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.229.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.230.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.231.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.232.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.233.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.236.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.237.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.238.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.94.239.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.128.64.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.128.67.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.128.69.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.128.70.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a04:9b40::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS21305 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 12 are in fix.csv.
- ROA: none3
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 93.125.26.0/24 | No ROA covers it. Add a ROA for AS21305, maxLength 24. |
| ROA: none | 93.125.75.0/24 | No ROA covers it. Add a ROA for AS21305, maxLength 24. |
| ROA: none | 87.252.236.0/24 | No ROA covers it. Add a ROA for AS21305, maxLength 24. |
Route objects not announced
Route objects with origin AS21305 whose prefix no peer sees AS21305 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.98.48.0/22 | RIPE | Valid |
| 95.128.64.0/21 | RIPE | No ROA |
| 95.128.64.0/23 | RIPE | No ROA |
| 2a04:9b40::/40 | RIPE | Invalid: maxLength |
| 2a04:9b40:80::/48 | RIPE | Invalid: maxLength |
| 2a04:9b40:c0::/48 | RIPE | Invalid: maxLength |
| 2a04:9b40:200::/40 | RIPE | Invalid: maxLength |
| 2a04:9b40:2000::/40 | RIPE | Invalid: maxLength |
| 2a04:9b40:2100::/40 | RIPE | Invalid: maxLength |
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.