bgpreport

Network · data from 2026-11-12

AS146812 DBCN-WEB - Deutsche Bank (China) Co., Ltd. Shanghai Branch

Registry name: DBCN-WEB - Deutsche Bank (China) Co., Ltd. Shanghai Branch, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS146812, 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.
103.190.122.0/24 No ROA Nonecovered by 103.190.122.0/23 672 100% 67
103.190.123.0/24 No ROA Nonecovered by 103.190.122.0/23 672 100% 67
2400:9020:f010::/47 No ROA None 636 100% 68
2400:9020:f012::/47 No ROA None 636 100% 67
2400:9020:f010::/46 No ROA None 635 100% 68
103.190.122.0/23 No ROA RIR databaseAPNIC 673 100% 67

AS-SET

AS146812 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 11 are in fix.csv.

  • ROA: none6
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none103.190.122.0/24No ROA covers it. Add a ROA for AS146812, maxLength 24.672 of 673
Route object: none103.190.122.0/24No route object for it. A route object for 103.190.122.0/23 with origin AS146812 covers it (filters allowing more-specifics accept it). Add a route object with origin AS146812 in the RIR database for the space.672 of 673
ROA: none103.190.123.0/24No ROA covers it. Add a ROA for AS146812, maxLength 24.672 of 673
Route object: none103.190.123.0/24No route object for it. A route object for 103.190.122.0/23 with origin AS146812 covers it (filters allowing more-specifics accept it). Add a route object with origin AS146812 in the RIR database for the space.672 of 673
ROA: none2400:9020:f010::/47No ROA covers it. Add a ROA for AS146812, maxLength 47.636 of 636
Route object: none2400:9020:f010::/47No route object for it. Add a route object with origin AS146812 in the RIR database for the space.636 of 636
ROA: none2400:9020:f012::/47No ROA covers it. Add a ROA for AS146812, maxLength 47.636 of 636
Route object: none2400:9020:f012::/47No route object for it. Add a route object with origin AS146812 in the RIR database for the space.636 of 636
ROA: none2400:9020:f010::/46No ROA covers it. Add a ROA for AS146812, maxLength 46.635 of 636
Route object: none2400:9020:f010::/46No route object for it. Add a route object with origin AS146812 in the RIR database for the space.635 of 636
ROA: none103.190.122.0/23No ROA covers it. Add a ROA for AS146812, maxLength 23.673 of 673

Route objects not announced

Every route object with origin AS146812 is announced.

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.