Morton-Telekom Ltd
Data as of 2026-08-09
BGP inherited
Limited data: only 3 ranges 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
| Netblocks | 3 · 3,072 IPv4 addresses |
| Cluster ID | 217752589 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 178.216.160.0/21 | Morton-Telekom Ltd | RIPE | ASSIGNED PI | ● high |
| 185.13.112.0/23 | Morton-Telekom Ltd | RIPE | ASSIGNED PA | ● high |
| 185.13.114.0/23 | Morton-Telekom Ltd | RIPE | ASSIGNED PA | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (2)
These blocks are registered to Morton-Telekom Ltd 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.
| 185.13.112.0/23 /23 | authorized for AS29069 — PJSC Rostelecom |
| 185.13.114.0/23 /23 | authorized for AS29069 — PJSC Rostelecom |
NIC Handles
ARTX-RIPE-MNT
DUMY-RIPE
DUMY-RIPE
MORTONTEL-MNT
ORG-ML207-RIPE
RIPE-NCC-END-MNT
TRANSLINECOM-MNT