bgpreport

Network · data from 2026-11-12

AS210893 Layered Technologies Limited

Registry name: LAYEREDTECH Layered Technologies Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210893, 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.
149.5.55.0/24 No ROA Other IRR onlyRADB 667 99% 67
149.5.56.0/24 No ROA Other IRR onlyRADB 667 99% 67
149.5.57.0/24 No ROA Other IRR onlyRADB 667 99% 67
149.5.58.0/24 No ROA Other IRR onlyRADB 667 99% 67
154.56.236.0/24 No ROA Other IRR onlyRADB 667 99% 67
2a11:2c80::/29 Valid None 633 100% 67
31.41.250.0/24 Valid RIR databaseRIPE 671 100% 67
195.5.127.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS210893: AS210893:AS-LTECH. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS210893 isn't in the set, or no route object for AS210893 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS210893 in itNot covered
AS210893:AS-LTECH RIPE 117 Yes 1

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

  • ROA: none5
  • Route object: none1
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none149.5.55.0/24No ROA covers it. Add a ROA for AS210893, maxLength 24.667 of 673
Route object: RIR149.5.55.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none149.5.56.0/24No ROA covers it. Add a ROA for AS210893, maxLength 24.667 of 673
Route object: RIR149.5.56.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none149.5.57.0/24No ROA covers it. Add a ROA for AS210893, maxLength 24.667 of 673
Route object: RIR149.5.57.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none149.5.58.0/24No ROA covers it. Add a ROA for AS210893, maxLength 24.667 of 673
Route object: RIR149.5.58.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none154.56.236.0/24No ROA covers it. Add a ROA for AS210893, maxLength 24.667 of 673
Route object: RIR154.56.236.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: none2a11:2c80::/29No route object for it. Add a route object with origin AS210893 in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS210893 is announced.

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.