Network · data from 2026-11-12
AS42396 Telesystems of Ukraine
Registry name: PPLNETUA-AS PJSC Telesystems of Ukraine, UA · PeeringDB
39IPv4 routes
97.4% RPKI valid · 43.6% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
1No ROA
22 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS42396, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS42396, 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.
| 77.109.48.0/20 | No ROA | RIR databaseRIPE | 669 99% |
| 77.109.26.0/23 | Valid | Nonecovered by 77.109.24.0/21 | 673 100% |
| 77.109.32.0/23 | Valid | Nonecovered by 77.109.32.0/21 | 673 100% |
| 77.109.34.0/23 | Valid | Nonecovered by 77.109.32.0/21 | 673 100% |
| 77.109.36.0/23 | Valid | Nonecovered by 77.109.32.0/21 | 673 100% |
| 77.109.38.0/23 | Valid | Nonecovered by 77.109.32.0/21 | 673 100% |
| 94.248.0.0/21 | Valid | Nonecovered by 94.248.0.0/20 | 673 100% |
| 94.248.18.0/23 | Valid | Nonecovered by 94.248.0.0/18 | 673 100% |
| 94.248.20.0/23 | Valid | Nonecovered by 94.248.0.0/18 | 673 100% |
| 94.248.22.0/23 | Valid | Nonecovered by 94.248.0.0/18 | 673 100% |
| 77.109.24.0/24 | Valid | Nonecovered by 77.109.24.0/21 | 672 100% |
| 77.109.29.0/24 | Valid | Nonecovered by 77.109.24.0/21 | 672 100% |
| 77.109.31.0/24 | Valid | Nonecovered by 77.109.24.0/21 | 672 100% |
| 77.109.32.0/24 | Valid | Nonecovered by 77.109.32.0/21 | 672 100% |
| 77.109.33.0/24 | Valid | Nonecovered by 77.109.32.0/21 | 672 100% |
| 77.109.48.0/22 | Valid | Nonecovered by 77.109.48.0/20 | 672 100% |
| 77.109.52.0/22 | Valid | Nonecovered by 77.109.48.0/20 | 672 100% |
| 77.109.57.0/24 | Valid | Nonecovered by 77.109.48.0/20 | 671 100% |
| 77.109.60.0/24 | Valid | Nonecovered by 77.109.48.0/20 | 671 100% |
| 77.109.61.0/24 | Valid | Nonecovered by 77.109.48.0/20 | 671 100% |
| 77.109.62.0/24 | Valid | Nonecovered by 77.109.48.0/20 | 671 100% |
| 77.109.4.0/24 | Valid | None | 670 100% |
| 77.109.1.0/24 | Valid | Nonecovered by 77.109.0.0/23 | 141 21% |
| 77.109.30.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 77.109.0.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.9.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.12.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.16.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.18.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.20.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.21.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.22.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.23.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.24.0/21 | Valid | RIR databaseRIPE | 669 99% |
| 77.109.40.0/21 | Valid | RIR databaseRIPE | 669 99% |
| 94.248.0.0/20 | Valid | RIR databaseRIPE | 669 99% |
| 94.248.8.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 94.248.12.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 94.248.16.0/23 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS42396'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 30 are in fix.csv.
- ROA: none1
- Route object: none22
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 77.109.48.0/20 | No ROA covers it. Add a ROA for AS42396, maxLength 20. |
| Route object: none | 77.109.26.0/23 | No route object for it. A route object for 77.109.24.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.32.0/23 | No route object for it. A route object for 77.109.32.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.34.0/23 | No route object for it. A route object for 77.109.32.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.36.0/23 | No route object for it. A route object for 77.109.32.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.38.0/23 | No route object for it. A route object for 77.109.32.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 94.248.0.0/21 | No route object for it. A route object for 94.248.0.0/20 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 94.248.18.0/23 | No route object for it. A route object for 94.248.0.0/18 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 94.248.20.0/23 | No route object for it. A route object for 94.248.0.0/18 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 94.248.22.0/23 | No route object for it. A route object for 94.248.0.0/18 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.24.0/24 | No route object for it. A route object for 77.109.24.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.29.0/24 | No route object for it. A route object for 77.109.24.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.31.0/24 | No route object for it. A route object for 77.109.24.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.32.0/24 | No route object for it. A route object for 77.109.32.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.33.0/24 | No route object for it. A route object for 77.109.32.0/21 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.48.0/22 | No route object for it. A route object for 77.109.48.0/20 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.52.0/22 | No route object for it. A route object for 77.109.48.0/20 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.57.0/24 | No route object for it. A route object for 77.109.48.0/20 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.60.0/24 | No route object for it. A route object for 77.109.48.0/20 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.61.0/24 | No route object for it. A route object for 77.109.48.0/20 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.62.0/24 | No route object for it. A route object for 77.109.48.0/20 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.4.0/24 | No route object for it. Add a route object with origin AS42396 in the RIR database for the space. |
| Route object: none | 77.109.1.0/24 | No route object for it. A route object for 77.109.0.0/23 with origin AS42396 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42396 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42396 whose prefix no peer sees AS42396 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.109.16.0/24 | RIPE | Valid |
| 77.109.17.0/24 | RIPE | Valid |
| 77.109.19.0/24 | RIPE | No ROA |
| 77.109.20.0/22 | RIPE | No ROA |
| 77.109.32.0/21 | RIPE | No ROA |
| 94.248.0.0/18 | RIPE | No ROA |
| 94.248.0.0/22 | 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.