Data as of Nov 21, 2026

89.104.168.0/23

No anonymizer space · no proxy exits in 30 days

i3D.net B.V

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

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.104.168.0 - 89.104.191.2556,144NL-I3DNET-20060313i3D.net B.V (ORG-IA772-RIPE) · NLALLOCATED PASep 3, 2021abuse@i3d.net
└ 89.104.168.0/23512i3Dnet-frmtl1unknownSUB-ALLOCATED PAMay 28, 2024abuse@i3d.net
via NL-I3DNET-20060313
└ 89.104.168.0/2732i3Dnet-frmtl1-K557229unknownASSIGNED PADec 1, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.32/2732i3Dnet-frmtl1-K170117unknownASSIGNED PADec 1, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.64/2664i3Dnet-frmtl1-K789185unknownASSIGNED PAJun 5, 2024abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.128/2732i3Dnet-frmtl1-K798665unknownASSIGNED PAOct 2, 2024abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.160/2816i3Dnet-frmtl1-K130134unknownASSIGNED PANov 21, 2024abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.176/2816i3Dnet-frmtl1-K783233unknownASSIGNED PAJun 2, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.192/2816i3Dnet-frmtl1-K810477unknownASSIGNED PANov 27, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.208/2816i3Dnet-frmtl1-K557229unknownASSIGNED PADec 2, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.224/2816i3Dnet-frmtl1-K805877unknownASSIGNED PAJun 11, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.168.240/2816i3Dnet-frmtl1-K795150unknownASSIGNED PAJul 2, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.169.0/25128i3Dnet-frmtl1-K798665unknownASSIGNED PAApr 11, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.169.128/2664i3Dnet-frmtl1-K813265unknownASSIGNED PAOct 20, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.169.192/2732i3Dnet-frmtl1-K789185unknownASSIGNED PAOct 29, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 89.104.169.224/2732i3Dnet-frmtl1-K776505unknownASSIGNED PAOct 30, 2025abuse@i3d.net
via i3Dnet-frmtl1

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
May 2024
Current origin since
May 2024 · 2.5 yr
Origin networks
1