Network · data from 2026-11-12
AS27399 BAM-US - Balyasny Asset Management L.P.
Registry name: BAM-US - Balyasny Asset Management L.P., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27399, 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.
| 38.89.137.0/24 | No ROA | None | 668 99% |
| 38.103.125.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.126.139.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.131.243.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 67.155.2.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 103.158.202.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 103.158.203.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 136.175.142.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 136.175.143.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 185.179.88.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 82.98.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS27399 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 14 are in fix.csv.
- ROA: none10
- Route object: none1
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.89.137.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| Route object: none | 38.89.137.0/24 | No route object for it. Add a route object with origin AS27399 in the RIR database for the space. |
| ROA: none | 38.103.125.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| Route object: RIR | 38.103.125.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.126.139.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| Route object: RIR | 38.126.139.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.131.243.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| Route object: RIR | 38.131.243.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 67.155.2.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| ROA: none | 103.158.202.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| ROA: none | 103.158.203.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| ROA: none | 136.175.142.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| ROA: none | 136.175.143.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
| ROA: none | 185.179.88.0/24 | No ROA covers it. Add a ROA for AS27399, maxLength 24. |
Route objects not announced
Every route object with origin AS27399 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.