bgpreport

Network · data from 2026-11-12

AS13458 DKP-ASN - DAVIDSON KEMPNER CAPITAL MANAGEMENT LP

Registry name: DKP-ASN - DAVIDSON KEMPNER CAPITAL MANAGEMENT LP, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13458, 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.138.242.0/24 No ROA None 672 100% 67
206.142.235.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 3
62.189.210.0/24 No ROA RIR databaseRIPE 4 1%low visibility 3
8.36.88.0/24 Valid None 673 100% 67
167.150.155.0/24 Valid RIR databaseARIN, RADB 673 100% 67
204.137.18.0/24 Valid RIR databaseARIN 673 100% 67
204.137.19.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

AS13458 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 10 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none205.138.242.0/24No ROA covers it. Add a ROA for AS13458, maxLength 24.672 of 673
Route object: none205.138.242.0/24No route object for it. Add a route object with origin AS13458 in the RIR database for the space.672 of 673
ROA: none206.142.235.0/24No ROA covers it. Add a ROA for AS13458, maxLength 24.2 of 673
Route object: RIR206.142.235.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none62.189.210.0/24No ROA covers it. Add a ROA for AS13458, maxLength 24.4 of 673
Route object: none8.36.88.0/24No route object for it. Add a route object with origin AS13458 in the RIR database for the space.673 of 673

Route objects not announced

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

65.200.162.0/24RADBNo ROA
204.137.16.0/24ARINValid
204.137.17.0/24ARINValid
204.137.20.0/24ARINValid

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.