Mikhail Fedorov
BGP inherited
Cluster stats
Netblocks12
All fragments 240 blocks across 25 clusters
Cluster ID191547371
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 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
12 0 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-06

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
23.191.40.0/24 Mikhail Fedorov BGP ANNOUNCED ● high
130.12.93.0/24 Mikhail Fedorov BGP ANNOUNCED ● high
195.95.149.0/24 Mikhail Fedorov BGP ANNOUNCED ● high
2602:f7de::/40 Mikhail Fedorov BGP ANNOUNCED ● high
2a0b:4e04::/32 Mikhail Fedorov BGP ANNOUNCED ● high
2a0b:4e04:3a::/48 Mikhail Fedorov BGP ANNOUNCED ● high
195.95.149.0/24 Mikhail Fedorov RIPE ALLOCATED-ASSIGNED PA ● medium
62.182.192.0/21 Mikhail Fedorov RIPE ALLOCATED PA ● low
72.4.64.0/21 Mikhail Fedorov RIPE ALLOCATED PA ● low
91.213.211.64/26 Mikhail Fedorov RIPE ASSIGNED PI ● low
2001:7f8:17d::/48 Mikhail Fedorov RIPE ASSIGNED PI ● low
2a0b:4e00::/29 Mikhail Fedorov RIPE ALLOCATED-BY-RIR ● low

Network trust

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

These blocks are registered to Mikhail Fedorov 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.

62.182.192.0/21 /21 authorized for AS42532 — SIA VEESP

NIC Handles

AS202301 AS26954 AS26954-MNT AS26954-MNT DUMY-RIPE DUMY-RIPE ORG-MF214-RIPE RIPE-NCC-END-MNT RIPE-NCC-HM-MNT