FOP Dmytro Nedilskyi
BGP inherited
Cluster stats
Netblocks8
All fragments 467 blocks across 151 clusters
Cluster ID191761314
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-06

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.43.185.0/24 FOP Dmytro Nedilskyi RIPE ASSIGNED PI ● high
31.43.191.0/24 FOP Dmytro Nedilskyi RIPE ASSIGNED PI ● high
88.210.63.0/24 FOP Dmytro Nedilskyi BGP ANNOUNCED ● high
88.210.63.0/24 FOP Dmytro Nedilskyi RIPE ASSIGNED PA ● high
92.63.197.0/24 FOP Dmytro Nedilskyi BGP ANNOUNCED ● high
185.156.73.0/24 FOP Dmytro Nedilskyi BGP ANNOUNCED ● high
193.8.187.0/24 FOP Dmytro Nedilskyi BGP ANNOUNCED ● high
194.113.39.0/24 FOP Dmytro Nedilskyi BGP ANNOUNCED ● high

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
Possible discrepancies (1)

These blocks are registered to FOP Dmytro Nedilskyi 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.

193.8.187.0/24 /24 authorized for AS201814 — MEVSPACE sp. z o.o.

NIC Handles

AS206378 AS211736 DUMY-RIPE DUMY-RIPE FDN3-MNT LocalNCC-mnt LocalNCC-mnt MNT-NETERRA ORG-FDN3-RIPE RIPE-NCC-END-MNT ru-ip84-1-mnt