bgpreport

Network · data from 2026-11-12

AS214760 LS4KDC LS4KDC LIMITED

Registry name: LS4KDC LS4KDC LIMITED, HK · not in PeeringDB

18IPv4 routes 5.6% RPKI valid · 22.2% with a route object
0IPv6 routes
14RPKI invalid 14 origin · 0 maxLength
3No ROA 14 with no route object for this origin
14Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS214760, seen from no peer

Announced routes

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

209.186.78.0/24 Invalid: origin None 36 5%low visibility 24
209.186.79.0/24 Invalid: origin None 36 5%low visibility 24
199.176.76.0/24 Invalid: origin None 33 5%low visibility 22
199.178.88.0/24 Invalid: origin None 33 5%low visibility 22
206.32.38.0/24 Invalid: origin None 33 5%low visibility 22
206.32.39.0/24 Invalid: origin None 33 5%low visibility 22
207.252.51.0/24 Invalid: origin None 33 5%low visibility 22
199.178.83.0/24 Invalid: origin None 10 1%low visibility 6
199.178.84.0/24 Invalid: origin None 10 1%low visibility 6
77.109.8.0/24 Invalid: origin None 4 1%low visibility 4
199.176.73.0/24 Invalid: origin None 4 1%low visibility 4
199.176.74.0/24 Invalid: origin None 4 1%low visibility 4
199.176.75.0/24 Invalid: origin None 4 1%low visibility 4
207.252.50.0/24 Invalid: origin None 4 1%low visibility 4
149.57.5.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.57.23.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.57.41.0/24 No ROA Other IRR onlyRADB 673 100% 67
149.57.7.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS214760 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 38 are in fix.csv.

  • ROA: origin14
  • ROA: none3
  • Route object: none14
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin209.186.78.0/24ROAs covering it name AS7018, not AS214760. If AS214760 should announce it, add a ROA for AS214760.36 of 673
Route object: none209.186.78.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.36 of 673
ROA: origin209.186.79.0/24ROAs covering it name AS7018, not AS214760. If AS214760 should announce it, add a ROA for AS214760.36 of 673
Route object: none209.186.79.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.36 of 673
ROA: origin199.176.76.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.33 of 673
Route object: none199.176.76.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.33 of 673
ROA: origin199.178.88.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.33 of 673
Route object: none199.178.88.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.33 of 673
ROA: origin206.32.38.0/24ROAs covering it name AS3356, not AS214760. If AS214760 should announce it, add a ROA for AS214760.33 of 673
Route object: none206.32.38.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.33 of 673
ROA: origin206.32.39.0/24ROAs covering it name AS3356, not AS214760. If AS214760 should announce it, add a ROA for AS214760.33 of 673
Route object: none206.32.39.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.33 of 673
ROA: origin207.252.51.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.33 of 673
Route object: none207.252.51.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.33 of 673
ROA: origin199.178.83.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.10 of 673
Route object: none199.178.83.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.10 of 673
ROA: origin199.178.84.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.10 of 673
Route object: none199.178.84.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.10 of 673
ROA: origin77.109.8.0/24ROAs covering it name AS42396, not AS214760. If AS214760 should announce it, add a ROA for AS214760.4 of 673
Route object: none77.109.8.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.4 of 673
ROA: origin199.176.73.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.4 of 673
Route object: none199.176.73.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.4 of 673
ROA: origin199.176.74.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.4 of 673
Route object: none199.176.74.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.4 of 673
ROA: origin199.176.75.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.4 of 673
Route object: none199.176.75.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.4 of 673
ROA: origin207.252.50.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214760 should announce it, add a ROA for AS214760.4 of 673
Route object: none207.252.50.0/24No route object for it. Add a route object with origin AS214760 in the RIR database for the space.4 of 673
ROA: none149.57.5.0/24No ROA covers it. Add a ROA for AS214760, maxLength 24.673 of 673
Route object: RIR149.57.5.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.57.23.0/24No ROA covers it. Add a ROA for AS214760, maxLength 24.673 of 673
Route object: RIR149.57.23.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none149.57.41.0/24No ROA covers it. Add a ROA for AS214760, maxLength 24.673 of 673
Route object: RIR149.57.41.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 AS214760 whose prefix no peer sees AS214760 announce. Many are kept on purpose (backup routes, space announced only in some places).

77.109.10.0/24ALTDBNo ROA
77.109.11.0/24ALTDBNo ROA
149.18.64.0/24ARINValid
149.57.228.0/24ARINValid

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.