bgpreport

Network · data from 2026-11-12

AS1399 CHARLES-SCHWAB-2 - Charles Schwab & Co., Inc.

Registry name: CHARLES-SCHWAB-2 - Charles Schwab & Co., Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1399, 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.
162.93.62.0/24 No ROA Nonecovered by 162.93.0.0/16 672 100% 67
162.93.64.0/19 No ROA Nonecovered by 162.93.0.0/16 672 100% 67
162.93.124.0/22 No ROA Nonecovered by 162.93.0.0/16 672 100% 67
162.93.160.0/19 No ROA Nonecovered by 162.93.0.0/16 672 100% 67

AS-SET

AS1399 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 24 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none162.93.62.0/24No ROA covers it. Add a ROA for AS1399, maxLength 24.672 of 673
Route object: none162.93.62.0/24No route object for it. A route object for 162.93.0.0/16 with origin AS1399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1399 in the RIR database for the space.672 of 673
ROA: none162.93.64.0/19No ROA covers it. Add a ROA for AS1399, maxLength 19.672 of 673
Route object: none162.93.64.0/19No route object for it. A route object for 162.93.0.0/16 with origin AS1399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1399 in the RIR database for the space.672 of 673
ROA: none162.93.124.0/22No ROA covers it. Add a ROA for AS1399, maxLength 22.672 of 673
Route object: none162.93.124.0/22No route object for it. A route object for 162.93.0.0/16 with origin AS1399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1399 in the RIR database for the space.672 of 673
ROA: none162.93.160.0/19No ROA covers it. Add a ROA for AS1399, maxLength 19.672 of 673
Route object: none162.93.160.0/19No route object for it. A route object for 162.93.0.0/16 with origin AS1399 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1399 in the RIR database for the space.672 of 673

Route objects not announced

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

74.114.36.0/22RADBNo ROA
162.93.0.0/16RADBNo ROA
198.200.170.0/23RADBNo ROA
198.200.170.0/24RADBNo ROA
198.200.171.0/24RADBNo ROA
198.200.172.0/23RADBNo ROA
198.200.172.0/24RADBNo ROA
198.200.174.0/24RADBNo ROA
199.200.8.0/22RADBNo ROA
199.200.12.0/23RADBNo ROA
204.58.24.0/22RADBNo ROA
208.88.144.0/22RADBNo ROA
216.105.240.0/20RADBNo ROA
216.105.249.0/24RADBNo ROA
216.105.251.0/24NTTCOM, RADBNo ROA
216.105.252.0/24NTTCOM, RADBNo 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.