bgpreport

Network · data from 2026-11-12

AS3412 CreditSuisseGroup-AS - Credit Suisse Group

Registry name: CreditSuisseGroup-AS - Credit Suisse Group, CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3412, 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.
199.53.16.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
199.53.107.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
199.53.108.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
199.53.183.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
199.53.186.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
198.240.130.0/24 No ROA RIR databaseRADB, RIPE 2 0%low visibility 2
198.240.148.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
198.240.151.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
199.53.25.0/24 No ROA RIR databaseRADB, RIPE 2 0%low visibility 2

AS-SET

AS3412 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 17 are in fix.csv.

  • ROA: none9
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none199.53.16.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673
Route object: RIR199.53.16.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none199.53.107.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673
Route object: RIR199.53.107.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none199.53.108.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673
Route object: RIR199.53.108.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none199.53.183.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673
Route object: RIR199.53.183.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none199.53.186.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673
Route object: RIR199.53.186.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none198.240.130.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673
ROA: none198.240.148.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673
ROA: none198.240.151.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673
ROA: none199.53.25.0/24No ROA covers it. Add a ROA for AS3412, maxLength 24.2 of 673

Route objects not announced

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

199.53.12.0/24RADBNo ROA
199.53.74.0/24RADBNo ROA
199.53.109.0/24RIPENo 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.