Network · data from 2026-11-12
AS39159 R.L Internet and Networks Ltd.
Registry name: NV-RL R.L Internet and Networks Ltd., IL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39159, 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.
| 195.60.232.0/24 | No ROA | Nonecovered by 195.60.232.0/22 | 33 5%low visibility |
| 195.60.233.0/24 | No ROA | Nonecovered by 195.60.232.0/22 | 33 5%low visibility |
| 195.60.234.0/24 | No ROA | Nonecovered by 195.60.232.0/22 | 33 5%low visibility |
| 195.60.235.0/24 | No ROA | Nonecovered by 195.60.232.0/22 | 33 5%low visibility |
| 83.229.22.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 83.229.63.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 83.229.95.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 85.8.152.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.60.232.0/22 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 217.194.157.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 213.255.197.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 213.8.65.0/24 | Valid | None | 33 5%low visibility |
| 213.8.151.0/24 | Valid | None | 33 5%low visibility |
| 81.5.20.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS39159'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 17 are in fix.csv.
- ROA: none11
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.60.232.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| Route object: none | 195.60.232.0/24 | No route object for it. A route object for 195.60.232.0/22 with origin AS39159 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39159 in the RIR database for the space. |
| ROA: none | 195.60.233.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| Route object: none | 195.60.233.0/24 | No route object for it. A route object for 195.60.232.0/22 with origin AS39159 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39159 in the RIR database for the space. |
| ROA: none | 195.60.234.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| Route object: none | 195.60.234.0/24 | No route object for it. A route object for 195.60.232.0/22 with origin AS39159 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39159 in the RIR database for the space. |
| ROA: none | 195.60.235.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| Route object: none | 195.60.235.0/24 | No route object for it. A route object for 195.60.232.0/22 with origin AS39159 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39159 in the RIR database for the space. |
| ROA: none | 83.229.22.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| ROA: none | 83.229.63.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| ROA: none | 83.229.95.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| ROA: none | 85.8.152.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| ROA: none | 195.60.232.0/22 | No ROA covers it. Add a ROA for AS39159, maxLength 22. |
| ROA: none | 217.194.157.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| ROA: none | 213.255.197.0/24 | No ROA covers it. Add a ROA for AS39159, maxLength 24. |
| Route object: none | 213.8.65.0/24 | No route object for it. Add a route object with origin AS39159 in the RIR database for the space. |
| Route object: none | 213.8.151.0/24 | No route object for it. Add a route object with origin AS39159 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS39159 is announced.
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.