MiraLogic Telecommunication Systems

BGP inherited
Cluster stats
Netblocks10
Cluster ID208801335
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
193.232.87.247/32 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
194.85.107.47/32 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
194.226.100.247/32 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
194.226.102.247/32 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
195.208.210.247/32 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
2001:7f8:20:101::210:247/128 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
2001:7f8:20:201::100:247/128 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
2001:7f8:20:202::102:247/128 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
2001:7f8:20:301::107:47/128 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high
2001:7f8:20:401::87:247/128 MiraLogic Telecommunication Systems PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS12668