bgpreport

Network · data from 2026-11-12

AS21350 INTERSPACE-AS Interspace Ltd.

Registry name: INTERSPACE-AS Interspace Ltd., IL · not in PeeringDB

28IPv4 routes 82.1% RPKI valid · 14.3% with a route object
0IPv6 routes
4RPKI invalid 0 origin · 4 maxLength
1No ROA 24 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS21350, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21350, 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.

95.175.56.0/22 Invalid: maxLength Nonecovered by 95.175.32.0/19 61 9%low visibility 35
80.244.173.0/24 Invalid: maxLength Other origin onlycovered by 80.244.160.0/20 23 3%low visibility 20
80.244.160.0/22 Invalid: maxLength Nonecovered by 80.244.160.0/21 1 0%low visibility 1
80.244.164.0/22 Invalid: maxLength Nonecovered by 80.244.160.0/21 1 0%low visibility 1
80.244.168.0/23 No ROA Nonecovered by 80.244.168.0/22 33 5%low visibility 27
80.244.172.0/23 Valid Nonecovered by 80.244.160.0/20 672 100% 67
95.175.32.0/20 Valid Nonecovered by 95.175.32.0/19 672 100% 67
95.175.38.0/24 Valid Nonecovered by 95.175.32.0/19 672 100% 67
95.175.45.0/24 Valid Nonecovered by 95.175.32.0/19 672 100% 67
95.175.48.0/24 Valid Nonecovered by 95.175.32.0/19 672 100% 66
95.175.49.0/24 Valid Nonecovered by 95.175.32.0/19 672 100% 66
95.175.51.0/24 Valid Nonecovered by 95.175.32.0/19 672 100% 66
95.175.52.0/22 Valid Nonecovered by 95.175.32.0/19 672 100% 67
95.175.52.0/24 Valid Nonecovered by 95.175.32.0/19 672 100% 67
95.175.53.0/24 Valid Nonecovered by 95.175.32.0/19 672 100% 67
80.244.160.0/24 Valid Nonecovered by 80.244.160.0/21 671 100% 67
80.244.161.0/24 Valid Nonecovered by 80.244.160.0/21 671 100% 67
80.244.163.0/24 Valid Nonecovered by 80.244.160.0/21 671 100% 67
80.244.164.0/24 Valid Nonecovered by 80.244.160.0/21 671 100% 67
80.244.165.0/24 Valid Nonecovered by 80.244.160.0/21 671 100% 67
80.244.166.0/24 Valid Nonecovered by 80.244.160.0/21 671 100% 67
80.244.168.0/24 Valid Nonecovered by 80.244.168.0/22 671 100% 67
80.244.169.0/24 Valid Nonecovered by 80.244.168.0/22 671 100% 67
80.244.171.0/24 Valid Nonecovered by 80.244.168.0/22 671 100% 67
95.175.60.0/24 Valid RIR databaseRIPE 673 100% 66
95.175.61.0/24 Valid RIR databaseRIPE 673 100% 66
80.244.160.0/21 Valid RIR databaseRIPE 672 100% 67
80.244.170.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS21350 isn't in PeeringDB, where networks name their 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 35 are in fix.csv.

  • ROA: maxLength4
  • ROA: none1
  • Route object: none24
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: maxLength95.175.56.0/22ROA 95.175.56.0/21 AS21350 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 95.175.56.0/22.61 of 673
Route object: none95.175.56.0/22No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.61 of 673
ROA: maxLength80.244.173.0/24ROA 80.244.172.0/23 AS21350 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 80.244.173.0/24.23 of 673
Route object: none80.244.173.0/24Route objects for it name AS44709. A route object for 80.244.160.0/20 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.23 of 673
ROA: maxLength80.244.160.0/22ROA 80.244.160.0/21 AS21350 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 80.244.160.0/22.1 of 673
Route object: none80.244.160.0/22No route object for it. A route object for 80.244.160.0/21 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.1 of 673
ROA: maxLength80.244.164.0/22ROA 80.244.160.0/21 AS21350 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 80.244.164.0/22.1 of 673
Route object: none80.244.164.0/22No route object for it. A route object for 80.244.160.0/21 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.1 of 673
ROA: none80.244.168.0/23No ROA covers it. Add a ROA for AS21350, maxLength 23.33 of 673
Route object: none80.244.168.0/23No route object for it. A route object for 80.244.168.0/22 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.33 of 673
Route object: none80.244.172.0/23No route object for it. A route object for 80.244.160.0/20 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.32.0/20No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.38.0/24No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.45.0/24No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.48.0/24No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.49.0/24No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.51.0/24No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.52.0/22No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.52.0/24No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none95.175.53.0/24No route object for it. A route object for 95.175.32.0/19 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.672 of 673
Route object: none80.244.160.0/24No route object for it. A route object for 80.244.160.0/21 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673
Route object: none80.244.161.0/24No route object for it. A route object for 80.244.160.0/21 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673
Route object: none80.244.163.0/24No route object for it. A route object for 80.244.160.0/21 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673
Route object: none80.244.164.0/24No route object for it. A route object for 80.244.160.0/21 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673
Route object: none80.244.165.0/24No route object for it. A route object for 80.244.160.0/21 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673
Route object: none80.244.166.0/24No route object for it. A route object for 80.244.160.0/21 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673
Route object: none80.244.168.0/24No route object for it. A route object for 80.244.168.0/22 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673
Route object: none80.244.169.0/24No route object for it. A route object for 80.244.168.0/22 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673
Route object: none80.244.171.0/24No route object for it. A route object for 80.244.168.0/22 with origin AS21350 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21350 in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS21350 whose prefix no peer sees AS21350 announce. Many are kept on purpose (backup routes, space announced only in some places).

80.244.160.0/20RIPENo ROA
80.244.168.0/22RIPENo ROA
80.244.172.0/24RIPEInvalid: maxLength
95.175.32.0/19RIPENo ROA
95.175.62.0/24RIPEValid
185.106.128.0/22RIPENo ROA

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.