bgpreport

Network · data from 2026-11-12

AS19065 LRS - Levi, Ray & Shoup, Inc.

Registry name: LRS - Levi, Ray & Shoup, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19065, 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.
199.96.8.0/24 No ROA Nonecovered by 199.96.8.0/23 671 100% 67
199.96.0.0/24 Valid RIR databaseARIN 671 100% 67
199.96.1.0/24 Valid RIR databaseARIN 671 100% 67
199.96.2.0/24 Valid RIR databaseARIN 671 100% 67
199.96.3.0/24 Valid RIR databaseARIN 671 100% 67
199.96.4.0/24 Valid RIR databaseARIN 671 100% 67
199.96.5.0/24 Valid RIR databaseARIN 671 100% 67
199.96.6.0/24 Valid RIR databaseARIN 671 100% 67
199.96.7.0/24 Valid RIR databaseARIN 671 100% 67
2602:802:5000::/40 Valid RIR databaseARIN 636 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none199.96.8.0/24No ROA covers it. Add a ROA for AS19065, maxLength 24.671 of 673
Route object: none199.96.8.0/24No route object for it. A route object for 199.96.8.0/23 with origin AS19065 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19065 in the RIR database for the space.671 of 673

Route objects not announced

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

63.167.204.0/24NTTCOMNo ROA
63.167.205.0/24NTTCOMNo ROA
63.167.206.0/24NTTCOMNo ROA
63.167.207.0/24NTTCOMNo ROA
65.121.196.0/24NTTCOMNo ROA
65.174.51.0/24NTTCOMNo ROA
199.96.0.0/21ARINValid
199.96.8.0/23RADBNo ROA
208.4.48.0/24NTTCOMNo ROA

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.