Data as of Nov 11, 2026

5.187.18.0/24

No anonymizer space · no proxy exits in 30 days

Iomart Cloud Services Limited · space held by Iomart Group Plc

Announcement
No RPKI
Announced by
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.18.0/304SERVERSPACE-NETSS::INFRA LoopbackASSIGNED PAJun 30, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.18.4/304SERVERSPACE-NETSs::infra MGMTASSIGNED PAJun 30, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.18.8/298SERVERSPACE-NETunknownASSIGNED PAJun 30, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.18.32/2732CustNo-35CMGl-NETASSIGNED PAJun 30, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.18.64/2732CustNo-35CMO::NETASSIGNED PAAug 19, 2014abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.18.96/2816CustNo-35CMO::NETASSIGNED PAMar 21, 2016abuse@iomart.com
via UK-IOMART-20120809
└ 5.187.18.128/25128SERVERSPACE-NETSYNT-NET:::RESERVEDASSIGNED PAJun 30, 2014abuse@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

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