Minhyeok Park
Data as of 2026-11-15
BGP inherited
This organisation
| Netblocks | 15 |
| IPv6 | 15 prefixes (largest 2a06:9801:ff0::/44) |
| Also registered under this name | 24 netblocks across 2 separate records |
| Record ID | 270425560 |
| Registry | BGP |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 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 (15)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2001:7f8:d0::3:56c6:1/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2406:840:1f:1000:0:21:8822:1/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2602:f919:90f:fffa::2188:22/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::b5/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2602:fed2:fff:ffff:6::11d/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2a06:9801:ff0::/44 | Minhyeok Park | BGP | ANNOUNCED | ● high |
| 2a06:9801:ffa::/48 | Minhyeok Park | BGP | ANNOUNCED | ● high |
| 2a0e:8f01:1000:9::12d/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:9::151/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:11::1c4/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:15::10d/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:16::157/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:19::10e/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:24::12a/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:78::117/128 | Minhyeok Park | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (15)
Footprint over time
11 weekly snapshots · JSON
24
+18 netblocks since 2026-09-06
2026-09-06
peak 24
2026-11-15
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(5 of 15)
Possible discrepancies (1)
These blocks are registered to Minhyeok Park 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.
| 2a06:9801:ff0::/44 /44 | authorized for AS14618 — Amazon.com, Inc. |
NIC Handles
AS218822
AS218822
LAGRANGE-AUTO-MNT