MKNETWORK TELECOM

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks6
IPv6 3 prefixes (largest 2001:12f8:0:13::53/128)
Also registered under this name 22 netblocks across 2 separate records
Record ID246700190
RegistryPEERINGDB
Customerssee who runs inside 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 · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.184.144.53/32 MKNETWORK TELECOM PEERINGDB ASSIGNED ● high
187.16.218.207/32 MKNETWORK TELECOM PEERINGDB ASSIGNED ● high
200.219.139.7/32 MKNETWORK TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::218:207/128 MKNETWORK TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:3::7/128 MKNETWORK TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:13::53/128 MKNETWORK TELECOM PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-19
2026-07-19 peak 6 2026-09-06

Network trust

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

NIC Handles

AS263456