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

89.16.162.0/23

No anonymizer space · no proxy exits in 30 days

Iomart Managed Services Limited

Announcement
89.16.160.0/19
No RPKI
Announced by
AS35425
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
89.16.160.0/198,192UK-RAPIDSWITCH-20060717Iomart Managed Services Limited (ORG-RL20-RIPE) · GBALLOCATED PAApr 15, 2021abuse@rapidswitch.com
└ 89.16.162.0/23512BYTEMARK-CUSTOMERBLOCKS-MANCHESTERunknownLIR-PARTITIONED PAJun 11, 2007abuse@rapidswitch.com
via UK-RAPIDSWITCH-20060717
└ 89.16.162.16/2816YCPV-OPENSTREETMAPunknownASSIGNED PAMay 3, 2016abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.32/2816BYTEMARK-GLADSERVunknownASSIGNED PADec 14, 2006abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.56/298YCPV-TDE-WANunknownASSIGNED PAJan 4, 2016abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.64/298YCPV-TDE-LANunknownASSIGNED PAJan 19, 2016abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.72/298YCPV-3DMARCOMMS-WANunknownASSIGNED PAMay 19, 2017abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.88/298YCPV-ADBURYunknownASSIGNED PAFeb 15, 2016abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.112/2816TRACKRECORDGLOBAL-YORKunknownASSIGNED PADec 17, 2014abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.192/2732BYTEMARK-GLADSERVunknownASSIGNED PAJan 8, 2009abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.224/2816BYTEMARK-GLADSERVunknownASSIGNED PAJan 10, 2009abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.162.248/298YCPV-GREENPARTYunknownASSIGNED PANov 9, 2016abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.0/2732BYTEMARK-DOSTONEunknownASSIGNED PAFeb 7, 2007abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.96/298BYTEMARK-DHCP-VLANunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.104/298BYTEMARK-DHCP-VLANDHCP VlanASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.136/298YCPV-TOTALPOOLunknownASSIGNED PADec 12, 2017abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.144/298BYTEMARK-JUSTGOODCARSunknownASSIGNED PAApr 18, 2007abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.192/298YCPV-EVERGREENunknownASSIGNED PANov 1, 2016abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.208/298YCPV-NEWICONunknownASSIGNED PAJun 30, 2017abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.216/298YCPV-GREENPARTY2unknownASSIGNED PANov 11, 2016abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.224/2816BYTEMARK-BA2unknownASSIGNED PAMay 31, 2007abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER
└ 89.16.163.240/2816BYTEMARK-STOCKDALEunknownASSIGNED PAJun 1, 2007abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER

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 89.16.160.0/19

89.16.160.0/19

Routing history

Pattern
Stable
First seen
Sep 2006
Current origin since
Sep 2006 · 20 yr
Origin networks
1