Data as of Nov 11, 2026

89.46.36.0/24

No anonymizer space · no proxy exits in 30 days

Telecolanza, S.L.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Unknown
Risk
40 / 100 · Medium
Leased space
Recent change
New origin Jul 2026
from AS206089 Telecolanza, S.L., after 1.1 years unannounced
IPv4 market

Path

Announced by AS206089 since Jul 2026 · 4 mo ago
1 · Holder
Telecolanza, S.L.
record created Mar 2, 2018
2 · Leased from
its owner, directly
3 · Announced by
AS206089 Telecolanza, S.L.
since Jul 2026 · 4 mo ago
4 · Use
Unknown

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

89.46.36.0/24

From the registry to its use

  1. Oct 8, 2009– May 8, 2010
    Announced
    AS46816 DirectSpace Networks, LLC.
  2. Feb 1, 2014– Feb 8, 2014
    Announced
  3. Mar 2, 2018
    Registry record
    Telecolanza, S.L.
    ALLOCATED PA
    89.46.36.0/24
  4. Mar 7, 2018
    Route object
    AS206089 Telecolanza, S.L.
    RIPE route object for AS206089 Telecolanza, S.L., maintainer ES-TELECOLANZA-1-MNT
  5. May 13, 2018– Jun 4, 2025
    Announced
    AS206089 Telecolanza, S.L.
    Internet provider
  6. Jul 6, 2026– today
    Announced
    AS206089 Telecolanza, S.L.
    Internet provider
  7. today
    Leased from
    EGIHosting
    Lessor

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.46.36.0/24256ES-TELECOLANZA-20051129Telecolanza, S.L. (ORG-TS364-RIPE) · ESALLOCATED PAMar 2, 2018ripe@telecomunicacioneslanzarote.com
└ 89.46.36.0/25128TELECOLANZA-NETTelecolanza, S.L.ASSIGNED PAMay 7, 2024ripe@telecomunicacioneslanzarote.com
via ES-TELECOLANZA-20051129
└ 89.46.36.128/25128TELECOLANZA-NETTelecolanza, S.L.ASSIGNED PAMay 7, 2024ripe@telecomunicacioneslanzarote.com
via ES-TELECOLANZA-20051129

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Oct 2009
Current origin since
Jul 2026 · 4 mo
Origin networks
3
Last change of origin
May 2018
Recorded history

History

Handoffs
2