bgpreport

Network · data from 2026-11-12

AS25869 HSBC-US - HSBC Bank USA

Registry name: HSBC-US - HSBC Bank USA, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25869, 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.

205.214.176.0/20 No ROA None 673 100% 67
205.214.182.0/23 No ROA Nonecovered by 205.214.176.0/21 673 100% 67
205.214.184.0/23 No ROA None 673 100% 67
205.214.176.0/21 No ROA Other IRR onlyRADB 673 100% 67
205.214.176.0/23 No ROA Other IRR onlyRADB 673 100% 67
205.214.180.0/23 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS25869 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: none6
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none205.214.176.0/20No ROA covers it. Add a ROA for AS25869, maxLength 20.673 of 673
Route object: none205.214.176.0/20No route object for it. Add a route object with origin AS25869 in the RIR database for the space.673 of 673
ROA: none205.214.182.0/23No ROA covers it. Add a ROA for AS25869, maxLength 23.673 of 673
Route object: none205.214.182.0/23No route object for it. A route object for 205.214.176.0/21 with origin AS25869 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25869 in the RIR database for the space.673 of 673
ROA: none205.214.184.0/23No ROA covers it. Add a ROA for AS25869, maxLength 23.673 of 673
Route object: none205.214.184.0/23No route object for it. Add a route object with origin AS25869 in the RIR database for the space.673 of 673
ROA: none205.214.176.0/21No ROA covers it. Add a ROA for AS25869, maxLength 21.673 of 673
Route object: RIR205.214.176.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.214.176.0/23No ROA covers it. Add a ROA for AS25869, maxLength 23.673 of 673
Route object: RIR205.214.176.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.214.180.0/23No ROA covers it. Add a ROA for AS25869, maxLength 23.673 of 673
Route object: RIR205.214.180.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

204.178.86.0/24RADBNo ROA
205.214.178.0/23RADBNo ROA
205.214.182.0/24RADBNo ROA
205.214.183.0/24RADBNo ROA
205.214.184.0/24RADBNo ROA
205.214.185.0/24RADBNo 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.