bgpreport

Network · data from 2026-11-12

AS215023 LIME-HOST LIMEE NETWORK LTD

Registry name: LIME-HOST LIMEE NETWORK LTD, GB · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 50.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
15Route objects not announced registered with origin AS215023, seen from no peer

Announced routes

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

151.241.130.0/24 Valid Nonecovered by 151.241.128.0/22 182 27% 55
151.241.131.0/24 Valid Nonecovered by 151.241.128.0/22 182 27% 55
202.155.147.0/24 Valid Other IRR onlyRADB 668 99% 67
151.241.128.0/22 Valid RIR databaseRADB, RIPE 668 99% 67
2a14:c380:17::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS215023 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 18 are in fix.csv.

  • Route object: none2
  • Route object: RIR1
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none151.241.130.0/24No route object for it. A route object for 151.241.128.0/22 with origin AS215023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS215023 in the RIR database for the space.182 of 673
Route object: none151.241.131.0/24No route object for it. A route object for 151.241.128.0/22 with origin AS215023 covers it (filters allowing more-specifics accept it). Add a route object with origin AS215023 in the RIR database for the space.182 of 673
Route object: RIR202.155.147.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

200.180.160.0/21RIPEValid
200.180.160.0/22RIPEValid
200.180.160.0/23RIPEValid
200.180.160.0/24RIPEValid
200.180.161.0/24RIPEValid
200.180.162.0/23RIPEValid
200.180.162.0/24RIPEValid
200.180.163.0/24RIPEValid
200.180.164.0/22RIPEValid
200.180.164.0/23RIPEValid
200.180.164.0/24RIPEValid
200.180.165.0/24RIPEValid
200.180.166.0/23RIPEValid
200.180.166.0/24RIPEValid
200.180.167.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.