Network · data from 2026-11-12
AS41714 SpotNet_Ltd
Registry name: SpotNet_Ltd SPOT-NET LTD, IL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41714, 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.157.80.0/23 | Valid | Nonecovered by 93.157.80.0/21 | 673 100% |
| 93.157.80.0/24 | Valid | Nonecovered by 93.157.80.0/21 | 673 100% |
| 93.157.81.0/24 | Valid | Nonecovered by 93.157.80.0/21 | 673 100% |
| 93.157.82.0/24 | Valid | Nonecovered by 93.157.80.0/21 | 673 100% |
| 93.157.84.0/24 | Valid | Nonecovered by 93.157.80.0/21 | 673 100% |
| 93.157.85.0/24 | Valid | Nonecovered by 93.157.80.0/21 | 673 100% |
| 93.157.86.0/23 | Valid | Nonecovered by 93.157.80.0/21 | 673 100% |
| 185.225.174.0/24 | Valid | Nonecovered by 185.225.174.0/23 | 673 100% |
| 185.225.175.0/24 | Valid | Nonecovered by 185.225.174.0/23 | 673 100% |
| 93.157.82.0/23 | Valid | Nonecovered by 93.157.80.0/21 | 672 100% |
| 2a06:e300::/32 | Valid | None | 635 100% |
| 2a06:e301::/32 | Valid | None | 635 100% |
| 2a06:e302::/32 | Valid | None | 635 100% |
| 2a06:e303::/32 | Valid | None | 635 100% |
| 2a06:e304::/32 | Valid | None | 635 100% |
| 2a06:e305::/32 | Valid | None | 635 100% |
| 2a06:e306::/32 | Valid | None | 635 100% |
| 2a06:e307::/32 | Valid | None | 635 100% |
| 2a06:e300::/29 | Valid | None | 634 100% |
| 93.157.87.0/24 | Valid | Nonecovered by 93.157.80.0/21 | 150 22% |
| 193.37.128.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 193.37.129.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 93.157.80.0/21 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 93.157.83.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.56.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.56.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.57.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.58.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.59.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.60.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.62.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.62.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.185.63.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.163.148.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.163.148.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.163.150.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.163.151.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.225.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.225.172.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.225.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.225.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.225.174.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.37.128.0/23 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.37.130.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 93.157.86.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 146.185.58.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 146.185.56.0/24 | Valid | RIR databaseRIPE | 36 5%low visibility |
AS-SET
AS41714'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 25 are in fix.csv.
- Route object: none20
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 93.157.80.0/23 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 93.157.80.0/24 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 93.157.81.0/24 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 93.157.82.0/24 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 93.157.84.0/24 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 93.157.85.0/24 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 93.157.86.0/23 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 185.225.174.0/24 | No route object for it. A route object for 185.225.174.0/23 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 185.225.175.0/24 | No route object for it. A route object for 185.225.174.0/23 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 93.157.82.0/23 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e300::/32 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e301::/32 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e302::/32 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e303::/32 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e304::/32 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e305::/32 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e306::/32 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e307::/32 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 2a06:e300::/29 | No route object for it. Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: none | 93.157.87.0/24 | No route object for it. A route object for 93.157.80.0/21 with origin AS41714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41714 in the RIR database for the space. |
| Route object: RIR | 193.37.128.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 193.37.129.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41714 whose prefix no peer sees AS41714 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.163.148.0/24 | RIPE | Valid |
| 185.163.149.0/24 | RIPE | Valid |
| 185.163.150.0/24 | 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.