BEL-M

BGP inherited
Limited data: only 1 range 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
Netblocks1
Cluster ID208668286
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (1)

⬇ export CSV
CIDR Org name Registry Status Confidence
93.17.49.136/30 BEL-M RIPE ASSIGNED PA ● medium

Possibly related to this organisation

what's this?
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.
  • KERRIERBEL-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
  • OOOMOMYMENTBEL-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
  • ARTKERAMIKABEL-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
  • AFMENEDZHMENTBEL-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
  • ELHIM_BEL-MRCES via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
  • BIOAMIDBEL-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
  • MODEKORBEL-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
  • KREPKABEL-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT