Network · data from 2026-11-12
AS43656 ПКП Телерадиокомпания Интертелеком
Registry name: INTERTELECOM-TV KP Intertelecom Ltd, UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43656, 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.170.64.1/32 | Invalid: maxLength | Nonecovered by 93.170.64.0/22 | 2 0%low visibility |
| 91.198.83.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.170.64.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 93.170.68.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 194.28.4.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 194.28.6.0/23 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS43656: AS-INTERTELECOM-TV. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS43656 isn't in the set, or no route object for AS43656 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS43656 in it | Not covered |
|---|---|---|---|---|---|
| AS-INTERTELECOM-TV | RIPE | 3 | 1 | Yes | 1 |
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: maxLength1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 93.170.64.1/32 | ROA 93.170.64.0/21 AS43656 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 93.170.64.1/32. |
| Route object: none | 93.170.64.1/32 | No route object for it. A route object for 93.170.64.0/22 with origin AS43656 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43656 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43656 whose prefix no peer sees AS43656 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.170.64.0/21 | RIPE | Valid |
| 194.28.4.0/22 | RIPE | No ROA |
| 2001:678:db8::/48 | 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.