bgpreport

Network · data from 2026-11-12

AS10692 DLS-LITH

Registry name: DLS-LITH - DLS Internet Services, Inc, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10692, 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.
66.117.160.0/19 No ROA None 672 100% 67
209.242.0.0/18 No ROA Other origin only 672 100% 67
216.145.224.0/19 No ROA None 672 100% 67
216.180.160.0/20 No ROA None 672 100% 67
209.242.50.0/24 No ROA None 670 100% 67
216.180.166.0/24 No ROA None 670 100% 68

AS-SET

AS10692's PeeringDB record names no 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 15 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none66.117.160.0/19No ROA covers it. Add a ROA for AS10692, maxLength 19.672 of 673
Route object: none66.117.160.0/19No route object for it. Add a route object with origin AS10692 in the RIR database for the space.672 of 673
ROA: none209.242.0.0/18No ROA covers it. Add a ROA for AS10692, maxLength 18.672 of 673
Route object: none209.242.0.0/18Route objects for it name AS7029. Add a route object with origin AS10692 in the RIR database for the space.672 of 673
ROA: none216.145.224.0/19No ROA covers it. Add a ROA for AS10692, maxLength 19.672 of 673
Route object: none216.145.224.0/19No route object for it. Add a route object with origin AS10692 in the RIR database for the space.672 of 673
ROA: none216.180.160.0/20No ROA covers it. Add a ROA for AS10692, maxLength 20.672 of 673
Route object: none216.180.160.0/20No route object for it. Add a route object with origin AS10692 in the RIR database for the space.672 of 673
ROA: none209.242.50.0/24No ROA covers it. Add a ROA for AS10692, maxLength 24.670 of 673
Route object: none209.242.50.0/24No route object for it. Add a route object with origin AS10692 in the RIR database for the space.670 of 673
ROA: none216.180.166.0/24No ROA covers it. Add a ROA for AS10692, maxLength 24.670 of 673
Route object: none216.180.166.0/24No route object for it. Add a route object with origin AS10692 in the RIR database for the space.670 of 673

Route objects not announced

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

216.145.224.0/23RADBNo ROA
216.180.170.0/24RADBNo ROA
216.180.171.0/24RADBNo 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.