bgpreport

Network · data from 2026-11-12

AS19950 CBNEPTUNE-AS-19950 - CB Neptune Holdings, LLC

Registry name: CBNEPTUNE-AS-19950 - CB Neptune Holdings, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19950, 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.
64.75.15.0/24 No ROA None 673 100% 67
192.41.226.0/24 No ROA None 673 100% 67
204.76.212.0/24 No ROA None 673 100% 67
208.92.82.0/24 No ROA None 673 100% 67
208.92.84.0/24 No ROA None 673 100% 67
192.44.255.0/24 No ROA None 672 100% 67
206.31.50.0/23 No ROA None 672 100% 67
208.92.81.0/24 No ROA Other IRR onlyRADB 673 100% 67
208.92.80.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS19950 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 18 are in fix.csv.

  • ROA: none9
  • Route object: none7
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none64.75.15.0/24No ROA covers it. Add a ROA for AS19950, maxLength 24.673 of 673
Route object: none64.75.15.0/24No route object for it. Add a route object with origin AS19950 in the RIR database for the space.673 of 673
ROA: none192.41.226.0/24No ROA covers it. Add a ROA for AS19950, maxLength 24.673 of 673
Route object: none192.41.226.0/24No route object for it. Add a route object with origin AS19950 in the RIR database for the space.673 of 673
ROA: none204.76.212.0/24No ROA covers it. Add a ROA for AS19950, maxLength 24.673 of 673
Route object: none204.76.212.0/24No route object for it. Add a route object with origin AS19950 in the RIR database for the space.673 of 673
ROA: none208.92.82.0/24No ROA covers it. Add a ROA for AS19950, maxLength 24.673 of 673
Route object: none208.92.82.0/24No route object for it. Add a route object with origin AS19950 in the RIR database for the space.673 of 673
ROA: none208.92.84.0/24No ROA covers it. Add a ROA for AS19950, maxLength 24.673 of 673
Route object: none208.92.84.0/24No route object for it. Add a route object with origin AS19950 in the RIR database for the space.673 of 673
ROA: none192.44.255.0/24No ROA covers it. Add a ROA for AS19950, maxLength 24.672 of 673
Route object: none192.44.255.0/24No route object for it. Add a route object with origin AS19950 in the RIR database for the space.672 of 673
ROA: none206.31.50.0/23No ROA covers it. Add a ROA for AS19950, maxLength 23.672 of 673
Route object: none206.31.50.0/23No route object for it. Add a route object with origin AS19950 in the RIR database for the space.672 of 673
ROA: none208.92.81.0/24No ROA covers it. Add a ROA for AS19950, maxLength 24.673 of 673
Route object: RIR208.92.81.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.92.80.0/24No ROA covers it. Add a ROA for AS19950, maxLength 24.672 of 673
Route object: RIR208.92.80.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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