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

5.187.16.0/24

No anonymizer space · no proxy exits in 30 days

Iomart Cloud Services Limited · space held by Iomart Group Plc

Announcement
5.187.16.0/20
No RPKI
Announced by
AS20860
Type
Hosting
Risk
50 / 100 · Medium

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.187.16.0/204,096UK-IOMART-20120809Iomart Group Plc (ORG-ISTI1-RIPE) · GBALLOCATED PAApr 14, 2021abuse@iomart.com
└ 5.187.16.0/304CustNo-2CORE::NJTE::LoopbackASSIGNED PAAug 23, 2013abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.4/304CustNo-2Serverspace-Net NjteASSIGNED PAAug 23, 2013abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.8/304CustNo-35CMO::NETASSIGNED PAOct 7, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.12/304CustNo-35CMOGlobal-NET (NJTE)ASSIGNED PAAug 23, 2013abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.16/304CustNo-35CMOGlobal-NETASSIGNED PAAug 23, 2013abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.20/304CustNo-35CMO::NETASSIGNED PANov 6, 2013abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.24/304CustNo-35unknownASSIGNED PAFeb 19, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.32/304CustNo-17reci-NETASSIGNED PAJul 3, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.36/304CustNo-35CMO::NETASSIGNED PAJul 24, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.40/304CustNo-35CMO::NETASSIGNED PAAug 6, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.44/304CustNo-35Cmo::net NjteASSIGNED PAOct 22, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.48/304CustNo-35CMO::NETASSIGNED PADec 16, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.52/304CustNo-35CMO-NJTE::NETASSIGNED PAMay 13, 2015abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.56/304CustNo-35CMO::NETASSIGNED PAJul 23, 2015abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.60/304CustNo-443METL::NETASSIGNED PAAug 7, 2015abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.64/304CustNo-35CMO-NJTE::NETASSIGNED PAAug 7, 2015abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.68/304CustNo-35CMO::NETASSIGNED PAAug 27, 2015abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.72/304CustNo-35CMO::NETASSIGNED PANov 25, 2015abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.76/304CustNo-2NJTE::NETASSIGNED PANov 25, 2015abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.100/304CustNo-517unknownASSIGNED PAMay 26, 2016abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.16.128/25128SERVERSPACE-NETSS:::INFRA::NJTEASSIGNED PASep 10, 2013abuse@iomart.com
via UK-IOMART-20120809

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 5.187.16.0/20

5.187.16.0/20

Routing history

Pattern
Stable
First seen
Mar 2014
Current origin since
May 2017 · 9.5 yr
Origin networks
2
Last change of origin
May 2017
Recorded history

History

Handoffs
1