bgpreport

Network · data from 2026-11-12

AS16640 SILICON-VALLEY-BANK - First-Citizens Bank & Trust Company

Registry name: SILICON-VALLEY-BANK - First-Citizens Bank & Trust Company, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS16640, 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.
192.173.26.0/24 No ROA Nonecovered by 192.173.26.0/23 672 100% 67
192.173.27.0/24 No ROA Nonecovered by 192.173.26.0/23 672 100% 67
199.246.78.0/24 No ROA Other origin onlycovered by 199.246.78.0/23 672 100% 67
199.246.79.0/24 No ROA Other origin onlycovered by 199.246.78.0/23 672 100% 67
208.80.232.0/24 No ROA Nonecovered by 208.80.232.0/23 672 100% 67
208.80.233.0/24 No ROA Nonecovered by 208.80.232.0/23 672 100% 67
198.212.183.0/24 No ROA Other IRR onlyRADB 672 100% 67
199.246.77.0/24 No ROA Other IRR onlyRADB 672 100% 67
208.80.235.0/24 No ROA Other IRR onlyRADB 672 100% 67
198.245.241.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
198.245.242.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS16640 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 25 are in fix.csv.

  • ROA: none11
  • Route object: none6
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none192.173.26.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: none192.173.26.0/24No route object for it. A route object for 192.173.26.0/23 with origin AS16640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16640 in the RIR database for the space.672 of 673
ROA: none192.173.27.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: none192.173.27.0/24No route object for it. A route object for 192.173.26.0/23 with origin AS16640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16640 in the RIR database for the space.672 of 673
ROA: none199.246.78.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: none199.246.78.0/24Route objects for it name AS14430. A route object for 199.246.78.0/23 with origin AS16640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16640 in the RIR database for the space.672 of 673
ROA: none199.246.79.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: none199.246.79.0/24Route objects for it name AS14430. A route object for 199.246.78.0/23 with origin AS16640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16640 in the RIR database for the space.672 of 673
ROA: none208.80.232.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: none208.80.232.0/24No route object for it. A route object for 208.80.232.0/23 with origin AS16640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16640 in the RIR database for the space.672 of 673
ROA: none208.80.233.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: none208.80.233.0/24No route object for it. A route object for 208.80.232.0/23 with origin AS16640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16640 in the RIR database for the space.672 of 673
ROA: none198.212.183.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: RIR198.212.183.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.246.77.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: RIR199.246.77.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none208.80.235.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.672 of 673
Route object: RIR208.80.235.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.245.241.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.2 of 673
Route object: RIR198.245.241.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none198.245.242.0/24No ROA covers it. Add a ROA for AS16640, maxLength 24.2 of 673
Route object: RIR198.245.242.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

192.173.26.0/23RADBNo ROA
199.246.78.0/23RADBNo ROA
208.80.232.0/23RADBNo 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.