bgpreport

Network · data from 2026-11-12

AS41714 SpotNet_Ltd

Registry name: SpotNet_Ltd SPOT-NET LTD, IL · PeeringDB

40IPv4 routes 100.0% RPKI valid · 72.5% with a route object
9IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 20 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS41714, seen from no peer

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% 67
93.157.80.0/24 Valid Nonecovered by 93.157.80.0/21 673 100% 66
93.157.81.0/24 Valid Nonecovered by 93.157.80.0/21 673 100% 66
93.157.82.0/24 Valid Nonecovered by 93.157.80.0/21 673 100% 66
93.157.84.0/24 Valid Nonecovered by 93.157.80.0/21 673 100% 66
93.157.85.0/24 Valid Nonecovered by 93.157.80.0/21 673 100% 67
93.157.86.0/23 Valid Nonecovered by 93.157.80.0/21 673 100% 67
185.225.174.0/24 Valid Nonecovered by 185.225.174.0/23 673 100% 66
185.225.175.0/24 Valid Nonecovered by 185.225.174.0/23 673 100% 67
93.157.82.0/23 Valid Nonecovered by 93.157.80.0/21 672 100% 67
2a06:e300::/32 Valid None 635 100% 67
2a06:e301::/32 Valid None 635 100% 67
2a06:e302::/32 Valid None 635 100% 67
2a06:e303::/32 Valid None 635 100% 67
2a06:e304::/32 Valid None 635 100% 67
2a06:e305::/32 Valid None 635 100% 67
2a06:e306::/32 Valid None 635 100% 67
2a06:e307::/32 Valid None 635 100% 67
2a06:e300::/29 Valid None 634 100% 67
93.157.87.0/24 Valid Nonecovered by 93.157.80.0/21 150 22% 49
193.37.128.0/24 Valid Other IRR onlyRADB 673 100% 66
193.37.129.0/24 Valid Other IRR onlyRADB 673 100% 66
93.157.80.0/21 Valid RIR databaseRADB, RIPE 673 100% 66
93.157.83.0/24 Valid RIR databaseRIPE 673 100% 67
146.185.56.0/21 Valid RIR databaseRIPE 673 100% 66
146.185.56.0/23 Valid RIR databaseRIPE 673 100% 66
146.185.57.0/24 Valid RIR databaseRIPE 673 100% 67
146.185.58.0/24 Valid RIR databaseRIPE 673 100% 67
146.185.59.0/24 Valid RIR databaseRIPE 673 100% 67
146.185.60.0/23 Valid RIR databaseRIPE 673 100% 66
146.185.60.0/24 Valid RIR databaseRIPE 673 100% 66
146.185.61.0/24 Valid RIR databaseRIPE 673 100% 66
146.185.62.0/23 Valid RIR databaseRIPE 673 100% 66
146.185.62.0/24 Valid RIR databaseRIPE 673 100% 67
146.185.63.0/24 Valid RIR databaseRIPE 673 100% 67
185.163.148.0/22 Valid RIR databaseRIPE 673 100% 66
185.163.148.0/23 Valid RIR databaseRIPE 673 100% 66
185.163.150.0/23 Valid RIR databaseRIPE 673 100% 66
185.163.151.0/24 Valid RIR databaseRIPE 673 100% 67
185.225.172.0/22 Valid RIR databaseRIPE 673 100% 66
185.225.172.0/23 Valid RIR databaseRIPE 673 100% 67
185.225.172.0/24 Valid RIR databaseRIPE 673 100% 67
185.225.173.0/24 Valid RIR databaseRIPE 673 100% 67
185.225.174.0/23 Valid RIR databaseRIPE 673 100% 67
193.37.128.0/23 Valid RIR databaseRADB, RIPE 673 100% 67
193.37.130.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
93.157.86.0/24 Valid RIR databaseRIPE 672 100% 67
146.185.58.0/23 Valid RIR databaseRIPE 672 100% 67
146.185.56.0/24 Valid RIR databaseRIPE 36 5%low visibility 27

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
ChangePrefix or setDetailFull-table peers
Route object: none93.157.80.0/23No 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.673 of 673
Route object: none93.157.80.0/24No 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.673 of 673
Route object: none93.157.81.0/24No 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.673 of 673
Route object: none93.157.82.0/24No 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.673 of 673
Route object: none93.157.84.0/24No 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.673 of 673
Route object: none93.157.85.0/24No 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.673 of 673
Route object: none93.157.86.0/23No 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.673 of 673
Route object: none185.225.174.0/24No 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.673 of 673
Route object: none185.225.175.0/24No 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.673 of 673
Route object: none93.157.82.0/23No 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.672 of 673
Route object: none2a06:e300::/32No route object for it. Add a route object with origin AS41714 in the RIR database for the space.635 of 636
Route object: none2a06:e301::/32No route object for it. Add a route object with origin AS41714 in the RIR database for the space.635 of 636
Route object: none2a06:e302::/32No route object for it. Add a route object with origin AS41714 in the RIR database for the space.635 of 636
Route object: none2a06:e303::/32No route object for it. Add a route object with origin AS41714 in the RIR database for the space.635 of 636
Route object: none2a06:e304::/32No route object for it. Add a route object with origin AS41714 in the RIR database for the space.635 of 636
Route object: none2a06:e305::/32No route object for it. Add a route object with origin AS41714 in the RIR database for the space.635 of 636
Route object: none2a06:e306::/32No route object for it. Add a route object with origin AS41714 in the RIR database for the space.635 of 636
Route object: none2a06:e307::/32No route object for it. Add a route object with origin AS41714 in the RIR database for the space.635 of 636
Route object: none2a06:e300::/29No route object for it. Add a route object with origin AS41714 in the RIR database for the space.634 of 636
Route object: none93.157.87.0/24No 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.150 of 673
Route object: RIR193.37.128.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR193.37.129.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

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/24RIPEValid
185.163.149.0/24RIPEValid
185.163.150.0/24RIPEValid

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.