bgpreport

Network · data from 2026-11-12

AS56696 ASLIQUID-MPLS

Registry name: ASLIQUID-MPLS Liquid Telecommunications Ltd, GB · PeeringDB

22IPv4 routes 72.7% RPKI valid · 9.1% with a route object
0IPv6 routes
5RPKI invalid 5 origin · 0 maxLength
1No ROA 20 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS56696, seen from no peer

Announced routes

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

217.74.224.0/24 Invalid: origin None 83 12% 35
217.74.225.0/24 Invalid: origin None 83 12% 35
217.74.226.0/24 Invalid: origin None 83 12% 35
217.74.227.0/24 Invalid: origin None 83 12% 35
197.221.253.0/24 Invalid: origin Other origin only 60 9%low visibility 32
41.60.53.0/24 No ROA Other origin only 673 100% 67
217.15.120.0/24 Valid Nonecovered by 217.15.120.0/22 673 100% 67
217.15.121.0/24 Valid Nonecovered by 217.15.120.0/22 673 100% 67
217.15.122.0/24 Valid Nonecovered by 217.15.120.0/22 673 100% 67
217.15.123.0/24 Valid Nonecovered by 217.15.120.0/22 673 100% 67
217.74.235.0/24 Valid None 673 100% 67
217.74.239.0/24 Valid Nonecovered by 217.74.238.0/23 673 100% 67
77.246.48.0/24 Valid Nonecovered by 77.246.48.0/22 672 100% 67
77.246.49.0/24 Valid Nonecovered by 77.246.48.0/22 672 100% 67
77.246.50.0/24 Valid Nonecovered by 77.246.48.0/22 672 100% 67
77.246.51.0/24 Valid Nonecovered by 77.246.48.0/22 672 100% 67
77.246.52.0/24 Valid Nonecovered by 77.246.52.0/22 672 100% 67
77.246.53.0/24 Valid Nonecovered by 77.246.52.0/22 672 100% 67
77.246.54.0/24 Valid Nonecovered by 77.246.52.0/22 672 100% 67
77.246.55.0/24 Valid Nonecovered by 77.246.52.0/22 672 100% 67
217.15.117.0/24 Valid RIR databaseRIPE 673 100% 67
217.15.118.0/24 Valid RIR databaseRIPE 673 100% 70

AS-SET

AS56696'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 30 are in fix.csv.

  • ROA: origin5
  • ROA: none1
  • Route object: none20
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin217.74.224.0/24ROAs covering it name AS30844, not AS56696. If AS56696 should announce it, add a ROA for AS56696.83 of 673
Route object: none217.74.224.0/24No route object for it. Add a route object with origin AS56696 in the RIR database for the space.83 of 673
ROA: origin217.74.225.0/24ROAs covering it name AS30844, not AS56696. If AS56696 should announce it, add a ROA for AS56696.83 of 673
Route object: none217.74.225.0/24No route object for it. Add a route object with origin AS56696 in the RIR database for the space.83 of 673
ROA: origin217.74.226.0/24ROAs covering it name AS30844, not AS56696. If AS56696 should announce it, add a ROA for AS56696.83 of 673
Route object: none217.74.226.0/24No route object for it. Add a route object with origin AS56696 in the RIR database for the space.83 of 673
ROA: origin217.74.227.0/24ROAs covering it name AS30844, not AS56696. If AS56696 should announce it, add a ROA for AS56696.83 of 673
Route object: none217.74.227.0/24No route object for it. Add a route object with origin AS56696 in the RIR database for the space.83 of 673
ROA: origin197.221.253.0/24ROAs covering it name AS37204, not AS56696. If AS56696 should announce it, add a ROA for AS56696.60 of 673
Route object: none197.221.253.0/24Route objects for it name AS37204. Add a route object with origin AS56696 in the RIR database for the space.60 of 673
ROA: none41.60.53.0/24No ROA covers it. Add a ROA for AS56696, maxLength 24.673 of 673
Route object: none41.60.53.0/24Route objects for it name AS30844. Add a route object with origin AS56696 in the RIR database for the space.673 of 673
Route object: none217.15.120.0/24No route object for it. A route object for 217.15.120.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.673 of 673
Route object: none217.15.121.0/24No route object for it. A route object for 217.15.120.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.673 of 673
Route object: none217.15.122.0/24No route object for it. A route object for 217.15.120.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.673 of 673
Route object: none217.15.123.0/24No route object for it. A route object for 217.15.120.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.673 of 673
Route object: none217.74.235.0/24No route object for it. Add a route object with origin AS56696 in the RIR database for the space.673 of 673
Route object: none217.74.239.0/24No route object for it. A route object for 217.74.238.0/23 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.673 of 673
Route object: none77.246.48.0/24No route object for it. A route object for 77.246.48.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.672 of 673
Route object: none77.246.49.0/24No route object for it. A route object for 77.246.48.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.672 of 673
Route object: none77.246.50.0/24No route object for it. A route object for 77.246.48.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.672 of 673
Route object: none77.246.51.0/24No route object for it. A route object for 77.246.48.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.672 of 673
Route object: none77.246.52.0/24No route object for it. A route object for 77.246.52.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.672 of 673
Route object: none77.246.53.0/24No route object for it. A route object for 77.246.52.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.672 of 673
Route object: none77.246.54.0/24No route object for it. A route object for 77.246.52.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.672 of 673
Route object: none77.246.55.0/24No route object for it. A route object for 77.246.52.0/22 with origin AS56696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56696 in the RIR database for the space.672 of 673

Route objects not announced

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

77.246.48.0/22RIPEValid
77.246.52.0/22RIPEValid
217.15.120.0/22RIPEValid
217.74.238.0/23RIPEValid

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.