NetCrew
BGP inherited
Cluster stats
| Netblocks | 4 · 1,281 IPv4 addresses |
| All fragments | 10 blocks across 2 clusters |
| Cluster ID | 209921736 |
| Registry | BGP |
| 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 23.176.200.0/24 | NetCrew | BGP | ANNOUNCED | ● high |
| 131.143.180.0/22 | NetCrew | BGP | ANNOUNCED | ● high |
| 2602:f91a::/40 | NetCrew | BGP | ANNOUNCED | ● high |
| 94.23.176.128/30 | Netcrew | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to NetCrew 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.
| 131.143.180.0/22 /22 | authorized for AS906 — DMIT Cloud Services |
| 23.176.200.0/24 /24 | authorized for AS906 — DMIT Cloud Services |
NIC Handles
AS13974
DUMY-RIPE
DUMY-RIPE
OVH-MNT