Data as of Nov 13, 2026

212.87.166.0/23

No anonymizer space · no proxy exits in 30 days

Netaxis Group Ltd · space held by Granatnet OU

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
Recently moved
Recent change
New origin Jul 2026
from AS47526 handily networks GmbH, after 5 years unannounced
registry: sub-allocated pa to a party the registry does not name by Granatnet OU, Jul 22, 2026
IPv4 market

Path

Reallocated to a party the registry does not name · Jul 22, 2026 · 4 mo ago · by Granatnet OU
1 · Holder
record created Jul 22, 2026 · reallocated to a party the registry does not name Jul 22, 2026
2 · Leased from
its owner, directly
3 · Announced by
AS219153 Netaxis Group Ltd
since Jul 2026 · 4 mo ago
4 · Use
Hosting

Lineage

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

212.87.166.0/23

From the registry to its use

  1. Dec 8, 2009– Sep 1, 2013
    Announced
  2. Sep 8, 2013– Jul 19, 2021
    Announced
    AS47526 handily networks GmbH
    Internet provider
  3. Jul 18, 2026– today
    Announced
    AS219153 Netaxis Group Ltd
    Hosting
  4. Jul 22, 2026
    Registry record
    Granatnet OU
    ALLOCATED PA
    212.87.160.0/19
  5. Jul 25, 2026
    Route object
    AS219153 Netaxis Group Ltd
    RIPE route object for AS219153 Netaxis Group Ltd, maintainer INTERLIR-MNT
  6. today
    Leased from
    InterLIR
    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
212.87.160.0/198,192EE-GRANATNET-20080618Granatnet OU (ORG-GO46-RIPE) · EEALLOCATED PAJul 22, 2026abuse@lir.ee
└ 212.87.160.0/212,048INTERLIRunknownSUB-ALLOCATED PAJul 22, 2026abuse@lir.ee
via EE-GRANATNET-20080618
└ 212.87.166.0/23512CustomerunknownASSIGNED PAJul 25, 2026ripe@interlir.com

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
Reactivated
First seen
Dec 2009
Current origin since
Jul 2026 · 4 mo
Origin networks
3
Last change of origin
Jul 2026
Recorded history

History

Handoffs
2