Network · data from 2026-11-12
AS38917 komtel-as INTERCOMTEL Limited Company
Registry name: komtel-as INTERCOMTEL Limited Company, RU · not in PeeringDB
21IPv4 routes
95.2% RPKI valid · 95.2% with a route object
8IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
9 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
8Route objects not announced
registered with origin AS38917, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38917, 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.227.12.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 109.111.70.0/24 | Valid | Nonecovered by 109.111.64.0/19 | 672 100% |
| 2a04:2cc2::/32 | Valid | Nonecovered by 2a04:2cc0::/29 | 601 94% |
| 2a04:2cc3::/32 | Valid | Nonecovered by 2a04:2cc0::/29 | 601 94% |
| 2a04:2cc4::/32 | Valid | Nonecovered by 2a04:2cc0::/29 | 601 94% |
| 2a04:2cc5::/32 | Valid | Nonecovered by 2a04:2cc0::/29 | 601 94% |
| 2a04:2cc6::/32 | Valid | Nonecovered by 2a04:2cc0::/29 | 601 94% |
| 2a04:2cc7::/32 | Valid | Nonecovered by 2a04:2cc0::/29 | 601 94% |
| 2a04:2cc0::/32 | Valid | Nonecovered by 2a04:2cc0::/29 | 587 92% |
| 2a04:2cc1::/32 | Valid | Nonecovered by 2a04:2cc0::/29 | 570 90% |
| 87.255.224.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 87.255.224.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 87.255.240.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 87.255.248.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 87.255.252.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.111.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 109.111.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 149.255.16.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 176.110.184.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 176.110.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 176.110.200.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 176.110.206.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.110.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.24.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.86.112.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 188.0.192.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 188.0.208.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 194.32.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.175.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS38917 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 18 are in fix.csv.
- ROA: none1
- Route object: none9
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.227.12.0/23 | No ROA covers it. Add a ROA for AS38917, maxLength 23. |
| Route object: none | 109.111.70.0/24 | No route object for it. A route object for 109.111.64.0/19 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
| Route object: none | 2a04:2cc2::/32 | No route object for it. A route object for 2a04:2cc0::/29 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
| Route object: none | 2a04:2cc3::/32 | No route object for it. A route object for 2a04:2cc0::/29 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
| Route object: none | 2a04:2cc4::/32 | No route object for it. A route object for 2a04:2cc0::/29 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
| Route object: none | 2a04:2cc5::/32 | No route object for it. A route object for 2a04:2cc0::/29 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
| Route object: none | 2a04:2cc6::/32 | No route object for it. A route object for 2a04:2cc0::/29 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
| Route object: none | 2a04:2cc7::/32 | No route object for it. A route object for 2a04:2cc0::/29 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
| Route object: none | 2a04:2cc0::/32 | No route object for it. A route object for 2a04:2cc0::/29 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
| Route object: none | 2a04:2cc1::/32 | No route object for it. A route object for 2a04:2cc0::/29 with origin AS38917 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38917 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38917 whose prefix no peer sees AS38917 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 87.255.232.0/21 | RIPE | Valid |
| 87.255.236.0/24 | RIPE | Valid |
| 87.255.248.109/32 | RIPE | Invalid: maxLength |
| 87.255.253.0/24 | RIPE | Valid |
| 87.255.254.0/24 | RIPE | Valid |
| 109.111.69.0/24 | RIPE | Valid |
| 176.110.204.0/23 | RIPE | Invalid: origin |
| 2a04:2cc0::/29 | 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.