bgpreport

Network · data from 2026-11-12

AS40156 The Optimal Link Corporation

Registry name: THEOPT-HOU - The Optimal Link Corporation, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40156, 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.
23.128.116.0/24 No ROA None 673 100% 67
23.189.208.0/24 No ROA None 673 100% 67
38.252.8.0/24 No ROA Other IRR onlyRADB 672 100% 67
193.202.106.0/24 No ROA RIR databaseRIPE 673 100% 67
195.8.117.0/24 No ROA RIR databaseRIPE 673 100% 67
2001:67c:1388::/48 No ROA RIR databaseRIPE 635 100% 67
2602:f7c4:1::/48 No ROA RIR databaseARIN 635 100% 67
66.187.64.0/20 Valid RIR databaseARIN 673 100% 67
139.64.155.0/24 Valid RIR databaseARIN 673 100% 67
142.249.221.0/24 Valid RIR databaseARIN 673 100% 67
162.218.228.0/22 Valid RIR databaseARIN 673 100% 67
216.230.224.0/20 Valid RIR databaseARIN 673 100% 67
2604:e880::/32 Valid RIR databaseARIN 635 100% 67

AS-SET

AS40156'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 10 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none23.128.116.0/24No ROA covers it. Add a ROA for AS40156, maxLength 24.673 of 673
Route object: none23.128.116.0/24No route object for it. Add a route object with origin AS40156 in the RIR database for the space.673 of 673
ROA: none23.189.208.0/24No ROA covers it. Add a ROA for AS40156, maxLength 24.673 of 673
Route object: none23.189.208.0/24No route object for it. Add a route object with origin AS40156 in the RIR database for the space.673 of 673
ROA: none38.252.8.0/24No ROA covers it. Add a ROA for AS40156, maxLength 24.672 of 673
Route object: RIR38.252.8.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none193.202.106.0/24No ROA covers it. Add a ROA for AS40156, maxLength 24.673 of 673
ROA: none195.8.117.0/24No ROA covers it. Add a ROA for AS40156, maxLength 24.673 of 673
ROA: none2001:67c:1388::/48No ROA covers it. Add a ROA for AS40156, maxLength 48.635 of 636
ROA: none2602:f7c4:1::/48No ROA covers it. Add a ROA for AS40156, maxLength 48.635 of 636

Route objects not announced

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