bgpreport

Network · data from 2026-11-12

AS7235 LanMinds

Registry name: LANMINDS - LanMinds, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7235, 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.152.0/23 Valid Other origin onlycovered by 66.117.128.0/19 649 96% 67
66.117.128.0/19 Valid RIR databaseALTDB, ARIN 670 100% 67

AS-SET

AS7235'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 14 are in fix.csv.

  • Route object: none1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none66.117.152.0/23Route objects for it name AS36734. A route object for 66.117.128.0/19 with origin AS7235 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7235 in the RIR database for the space.649 of 673

Route objects not announced

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

66.117.128.0/22ALTDBValid
192.67.166.0/24NTTCOMNo ROA
192.190.48.0/24ALTDBNo ROA
204.182.55.0/24RADBNo ROA
204.182.56.0/24RADBNo ROA
204.182.57.0/24RADBNo ROA
205.162.6.0/24RADBNo ROA
205.162.7.0/24RADBNo ROA
205.162.54.0/24RADBNo ROA
205.162.58.0/24RADBNo ROA
205.162.59.0/24RADBNo ROA
208.1.127.0/24RADBNo ROA
208.25.64.0/19NTTCOMNo 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.