IPV4C-JACK-ALEX
Data as of 2026-11-15
BGP inherited
This organisation
| Netblocks | 14 |
| IPv6 | 14 prefixes (largest 2a0a:37c0:8000::/33) |
| Record ID | 270490819 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (14)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0a:37c0::/33 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0::/35 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0::/34 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:2000::/35 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:4000::/35 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:4000::/34 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:6000::/35 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:8000::/33 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:8000::/34 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:8000::/35 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:a000::/35 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:c000::/34 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:c000::/35 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:37c0:e000::/35 | IPV4C-JACK-ALEX | RIPE | ALLOCATED-BY-LIR | ● low |
IPv6 ranges (14)
Footprint over time
5 weekly snapshots · JSON
14
0 netblocks since 2026-10-18
2026-10-18
peak 14
2026-11-15
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(14 of 14)
RPKI-inferred operator
Enzu Inc
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
ACRO49621-RIPE
DUMY-RIPE
DUMY-RIPE
ipv4center-mnt