Jockey Club Network
Data as of 2026-08-23
BGP inherited
Cluster stats
| Netblocks | 5 · 514 IPv4 addresses |
| IPv6 | 2 prefixes (largest 2001:13c7:6001::103/128) |
| Cluster ID | 227009719 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.8.90/32 | Jockey Club Network | PEERINGDB | ASSIGNED | ● high |
| 45.68.8.103/32 | Jockey Club Network | PEERINGDB | ASSIGNED | ● high |
| 45.230.34.0/23 | JOCKEY CLUB A.C. | ARIN | ASSIGNED | ● high |
| 2001:13c7:6001::90/128 | Jockey Club Network | PEERINGDB | ASSIGNED | ● high |
| 2001:13c7:6001::103/128 | Jockey Club Network | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (1)
These blocks are registered to Jockey Club Network but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 45.230.34.0/23 /23 | authorized for AS64109 — AS64109 |
NIC Handles
AHA
AHA
AHA
AR-JCAC-LACNIC
AS64109