Network · data from 2026-11-12
AS216050 Lietpark Communications
Registry name: lietpark Lietparkas UAB, LT · PeeringDB
83IPv4 routes
97.6% RPKI valid · 98.8% with a route object
0IPv6 routes
1RPKI invalid
1 origin · 0 maxLength
1No ROA
1 with no route object for this origin
9Low visibility
seen by under 10% of full-table peers
1Route objects not announced
registered with origin AS216050, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS216050, 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.
| 66.245.167.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 92.61.111.0/24 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 45.150.16.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.44.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.46.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.38.47.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.61.105.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.113.41.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 92.113.69.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 92.113.78.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 92.113.81.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 92.113.82.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 92.113.84.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 92.113.85.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 92.113.88.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 92.113.90.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 94.74.140.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.135.51.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 95.135.73.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 104.234.34.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 109.203.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.203.167.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.46.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.46.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.92.33.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.92.57.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.94.163.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.94.164.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 185.34.160.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.100.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.100.170.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.222.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.222.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.49.146.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.203.165.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.203.166.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.203.167.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.203.192.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.203.193.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.203.194.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.203.211.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.203.240.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 89.38.41.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.38.43.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 92.112.131.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 92.113.55.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 95.135.128.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 95.135.129.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 95.135.131.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 95.135.235.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 178.92.32.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 178.92.35.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 178.94.166.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.203.170.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 46.203.191.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 92.113.65.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 92.113.79.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 92.113.166.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 95.135.115.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 103.230.9.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 109.203.164.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.203.165.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.222.124.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.202.204.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 46.202.205.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 91.124.48.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 95.135.130.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 156.232.90.0/23 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 46.203.151.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 91.124.50.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 91.124.51.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 178.94.165.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 46.203.181.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 91.124.39.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 92.113.167.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 95.135.132.0/24 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 37.49.149.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 92.113.68.0/24 | Valid | RIR databaseRADB, RIPE | 2 0%low visibility |
| 92.113.75.0/24 | Valid | RIR databaseRADB, RIPE | 2 0%low visibility |
| 92.113.76.0/24 | Valid | RIR databaseRADB, RIPE | 2 0%low visibility |
| 92.113.87.0/24 | Valid | RIR databaseRADB, RIPE | 2 0%low visibility |
| 95.135.114.0/24 | Valid | RIR databaseRADB, RIPE | 2 0%low visibility |
| 95.135.133.0/24 | Valid | RIR databaseRADB, RIPE | 2 0%low visibility |
AS-SET
AS216050'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 4 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 66.245.167.0/24 | ROAs covering it name AS400384, not AS216050. If AS216050 should announce it, add a ROA for AS216050. |
| Route object: none | 66.245.167.0/24 | Route objects for it name AS400384. Add a route object with origin AS216050 in the RIR database for the space. |
| ROA: none | 92.61.111.0/24 | No ROA covers it. Add a ROA for AS216050, maxLength 24. |
Route objects not announced
Route objects with origin AS216050 whose prefix no peer sees AS216050 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 95.135.111.0/24 | RADB, RIPE | Valid |
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.