bgpreport

Network · data from 2026-11-12

AS21993 SCHLAGE-AS - Schlage Lock Company LLC

Registry name: SCHLAGE-AS - Schlage Lock Company LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21993, 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.
198.102.127.0/24 No ROA None 673 100% 67
198.102.130.0/24 No ROA None 673 100% 67
198.102.131.0/24 No ROA None 673 100% 67
198.102.132.0/24 No ROA None 673 100% 67
198.102.133.0/24 No ROA None 673 100% 67
198.102.134.0/24 No ROA None 673 100% 67
198.102.137.0/24 No ROA Other IRR onlyRADB 671 100% 67
198.102.138.0/24 No ROA Other IRR onlyRADB 671 100% 67
198.97.4.0/22 No ROA RIR databaseARIN 673 100% 70

AS-SET

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

  • ROA: none9
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none198.102.127.0/24No ROA covers it. Add a ROA for AS21993, maxLength 24.673 of 673
Route object: none198.102.127.0/24No route object for it. Add a route object with origin AS21993 in the RIR database for the space.673 of 673
ROA: none198.102.130.0/24No ROA covers it. Add a ROA for AS21993, maxLength 24.673 of 673
Route object: none198.102.130.0/24No route object for it. Add a route object with origin AS21993 in the RIR database for the space.673 of 673
ROA: none198.102.131.0/24No ROA covers it. Add a ROA for AS21993, maxLength 24.673 of 673
Route object: none198.102.131.0/24No route object for it. Add a route object with origin AS21993 in the RIR database for the space.673 of 673
ROA: none198.102.132.0/24No ROA covers it. Add a ROA for AS21993, maxLength 24.673 of 673
Route object: none198.102.132.0/24No route object for it. Add a route object with origin AS21993 in the RIR database for the space.673 of 673
ROA: none198.102.133.0/24No ROA covers it. Add a ROA for AS21993, maxLength 24.673 of 673
Route object: none198.102.133.0/24No route object for it. Add a route object with origin AS21993 in the RIR database for the space.673 of 673
ROA: none198.102.134.0/24No ROA covers it. Add a ROA for AS21993, maxLength 24.673 of 673
Route object: none198.102.134.0/24No route object for it. Add a route object with origin AS21993 in the RIR database for the space.673 of 673
ROA: none198.102.137.0/24No ROA covers it. Add a ROA for AS21993, maxLength 24.671 of 673
Route object: RIR198.102.137.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.102.138.0/24No ROA covers it. Add a ROA for AS21993, maxLength 24.671 of 673
Route object: RIR198.102.138.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.97.4.0/22No ROA covers it. Add a ROA for AS21993, maxLength 22.673 of 673

Route objects not announced

Every route object with origin AS21993 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.