bgpreport

Network · data from 2026-11-12

AS14016 Capcon Networks, LLC

Registry name: CAPCON-NETWORK-LLC - Capcon Networks, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14016, 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.
38.75.248.0/23 No ROA RIR databaseARIN 673 100% 67
198.203.173.0/24 No ROA RIR databaseARIN 673 100% 67
38.57.187.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
38.252.10.0/24 No ROA RIR databaseARIN, RADB 670 100% 67
38.252.11.0/24 No ROA RIR databaseARIN, RADB 670 100% 67
38.57.107.0/24 No ROA RIR databaseARIN, RADB 669 99% 67
199.245.156.0/24 Valid RIR databaseARIN 673 100% 67
206.53.16.0/20 Valid RIR databaseARIN 673 100% 67
2602:fbcb:1::/48 Valid RIR databaseARIN 635 100% 67
2602:fbcb:2::/48 Valid RIR databaseARIN 635 100% 67
2602:fbcb:4::/48 Valid RIR databaseARIN 635 100% 67
2602:fbcb:3::/48 Valid RIR databaseARIN 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS14016: ARIN::AS14016:AS-CAPCON. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS14016 isn't in the set, or no route object for AS14016 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS14016 in itNot covered
ARIN::AS14016:AS-CAPCON ARIN3 member sets in no database: AS40128:AS-CONE, AS40128:AS-TRANSIT, AS40749:AS-CUSTOMERS 38208,575 Yes 0

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: none6
  • AS-SET: missing member3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.75.248.0/23No ROA covers it. Add a ROA for AS14016, maxLength 23.673 of 673
ROA: none198.203.173.0/24No ROA covers it. Add a ROA for AS14016, maxLength 24.673 of 673
ROA: none38.57.187.0/24No ROA covers it. Add a ROA for AS14016, maxLength 24.672 of 673
ROA: none38.252.10.0/24No ROA covers it. Add a ROA for AS14016, maxLength 24.670 of 673
ROA: none38.252.11.0/24No ROA covers it. Add a ROA for AS14016, maxLength 24.670 of 673
ROA: none38.57.107.0/24No ROA covers it. Add a ROA for AS14016, maxLength 24.669 of 673
AS-SET: missing memberARIN::AS14016:AS-CAPCONAS14016:AS-CAPCON (ARIN) lists AS40128:AS-CONE; no IRR database read has it.
AS-SET: missing memberARIN::AS14016:AS-CAPCONAS14016:AS-CAPCON (ARIN) lists AS40128:AS-TRANSIT; no IRR database read has it.
AS-SET: missing memberARIN::AS14016:AS-CAPCONAS14016:AS-CAPCON (ARIN) lists AS40749:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

207.174.208.0/24ARINNo ROA
207.174.209.0/24ARINNo 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.