Eve Network
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 |
| Cluster ID | 212021205 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
3 weekly snapshots · JSON
6
0 netblocks since 2026-07-12
2026-07-12
peak 6
2026-07-19
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 206.51.7.116/32 | Eve Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:1b:1::116/128 | Eve Network | PEERINGDB | ASSIGNED | ● high |
| 2a0b:4340:c8::/48 | Eve-WSI | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to Eve 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.
| 2a0b:4340:c8::/48 /48 | authorized for AS44421 — Yifu Yu |
NIC Handles
AS44421
DUMY-RIPE
DUMY-RIPE
Eve-MNT