LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

81.4.100.0/22

No anonymizer space · no proxy exits in 30 days

RouteLabel V.O.F.

Announcement
this exact prefix
RPKI valid
Announced by
AS198203
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
81.4.100.0 - 81.4.111.2553,072NL-ROUTELABEL-20020510RouteLabel V.O.F. (ORG-WV3-RIPE) · NLALLOCATED PANov 16, 2018abuse@routelabel.net
└ 81.4.100.0/221,024WESERVIT-RAMNODERouteLabel V.O.F. (ORG-WV3-RIPE) · NLSUB-ALLOCATED PAJul 10, 2014abuse@routelabel.net
└ 81.4.100.0/24256WESERVIT-RAMNODERamNode IP SpaceSUB-ALLOCATED PAOct 1, 2014abuse@routelabel.net
via WESERVIT-RAMNODE
└ 81.4.101.0/24256WESERVIT-RAMNODERamNode IP SpaceSUB-ALLOCATED PAOct 1, 2014abuse@routelabel.net
via WESERVIT-RAMNODE
└ 81.4.102.0/24256WESERVIT-RAMNODERamNode IP SpaceSUB-ALLOCATED PANov 28, 2014abuse@routelabel.net
via WESERVIT-RAMNODE
└ 81.4.103.0/24256WESERVIT-RAMNODERamNode IP SpaceSUB-ALLOCATED PANov 28, 2014abuse@routelabel.net
via WESERVIT-RAMNODE
└ 81.4.103.207/321CLIENT1447-FUSIONEDFusioned LtdASSIGNED PAApr 2, 2015abuse@routelabel.net
via WESERVIT-RAMNODE

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2014
Current origin since
Jul 2014 · 12 yr
Origin networks
1