Data as of Nov 12, 2026

77.72.238.0/24

No anonymizer space · no proxy exits in 30 days

IP Nexia N.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

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
77.72.232.0/212,048BE-TOLEDO-20070226IP Nexia N.V. (ORG-TTS7-RIPE) · BEALLOCATED PAFeb 26, 2007abuse@ipnexia.com
└ 77.72.238.0/24256IPNEXIAIPNEXIA customersLIR-PARTITIONED PAJun 21, 2016abuse@ipnexia.com
via BE-TOLEDO-20070226
└ 77.72.238.0/2732IPNEXIAIPNEXIA customer SILVERLININGASSIGNED PAJun 21, 2016abuse@ipnexia.com
via IPNEXIA
└ 77.72.238.32/304IPNEXIAIPNEXIA customer THERABEL BEASSIGNED PADec 19, 2017abuse@ipnexia.com
via IPNEXIA
└ 77.72.238.36/304IPNEXIAIPNEXIA customer CORE EQUITYASSIGNED PADec 19, 2017abuse@ipnexia.com
via IPNEXIA
└ 77.72.238.40/304IPNEXIAIPNEXIA customer MERCURI URVALASSIGNED PADec 19, 2017abuse@ipnexia.com
via IPNEXIA
└ 77.72.238.44/304IPNEXIAIPNEXIA customer BLOOMZASSIGNED PADec 19, 2017abuse@ipnexia.com
via IPNEXIA
└ 77.72.238.48/2816IPNEXIAIPNEXIA customer BLOOMZASSIGNED PADec 19, 2017abuse@ipnexia.com
via IPNEXIA
└ 77.72.238.64/298IPNEXIAIPNEXIA customer K-I Chemical EuropeASSIGNED PADec 19, 2017abuse@ipnexia.com
via IPNEXIA
└ 77.72.238.72/304IPNEXIAIPNEXIA customer MERCURI URVALASSIGNED PADec 19, 2017abuse@ipnexia.com
via IPNEXIA

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
Jun 2016
Current origin since
Jun 2016 · 10 yr
Origin networks
1