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

5.102.174.0/24

No anonymizer space · no proxy exits in 30 days

CustodianDC Limited

Announcement
this exact prefix
RPKI valid
Announced by
AS50300
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
5.102.168.0/212,048UK-CUSTDC-20120628CustodianDC Limited (ORG-CL129-RIPE) · GBALLOCATED PAJun 28, 2012abuse@CustodianDC.com
└ 5.102.174.32/298TRAVEL_INSURANCE_FACILITIES_2unknownASSIGNED PADec 19, 2023abuse@CustodianDC.com
via UK-CUSTDC-20120628
└ 5.102.174.40/298CUSTDC_CLIENT_TELIGENTTeligentASSIGNED PAJul 4, 2014abuse@CustodianDC.com
via UK-CUSTDC-20120628
└ 5.102.174.112/2816CUSTDC_CLIENT_KMGROUP_2KM GroupASSIGNED PAMay 1, 2018abuse@CustodianDC.com
└ 5.102.174.128/2816CLIENT_CUSTDC_JE_HallunknownASSIGNED PAMar 5, 2024abuse@CustodianDC.com
via UK-CUSTDC-20120628
└ 5.102.174.144/2816CUSTDC_CLIENT_TRAVELBRANDSunknownASSIGNED PANov 11, 2026abuse@CustodianDC.com
via UK-CUSTDC-20120628

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
Apr 2018
Current origin since
Apr 2018 · 8.6 yr
Origin networks
1