RU-MEGAFONSIB

BGP inherited
Cluster stats
Netblocks8 · 2,040 IPv4 addresses
All fragments 15 blocks across 8 clusters
Cluster ID210262638
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.173.255.0/24 RU-MEGAFONSIB RIPE ASSIGNED PA ● low
178.176.248.0/24 RU-MEGAFONSIB RIPE ASSIGNED PA ● low
178.176.250.0/24 RU-MEGAFONSIB RIPE ASSIGNED PA ● low
178.176.251.0/24 RU-MEGAFONSIB RIPE ASSIGNED PA ● low
178.176.252.0/24 RU-MEGAFONSIB RIPE ASSIGNED PA ● low
178.176.253.0/24 RU-MEGAFONSIB RIPE ASSIGNED PA ● low
178.176.254.0/24 RU-MEGAFONSIB RIPE ASSIGNED PA ● low
178.176.255.0/24 RU-MEGAFONSIB RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RU MEGAFONSIB” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MF-SIB-MNT