Data as of Nov 20, 2026

212.110.176.0/22

No anonymizer space · no proxy exits in 30 days

Iomart Managed Services Limited

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
212.110.160.0/198,192UK-RAPIDSWITCH-20081008Iomart Managed Services Limited (ORG-RL20-RIPE) · GBALLOCATED PAApr 15, 2021abuse@rapidswitch.com
└ 212.110.176.0/221,024BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7unknownLIR-PARTITIONED PAOct 30, 2009abuse@rapidswitch.com
via UK-RAPIDSWITCH-20081008
└ 212.110.176.192/2664LEENIXLeenix & Tonic Fusion hostingASSIGNED PAMar 1, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.177.16/2816BYTEMARK-INBOUTIQUEInboutiqse SSLASSIGNED PAMar 22, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.177.40/298BYTEMARK-VPS1EVERunknownASSIGNED PAMay 4, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.177.72/298BYTEMARK-SPOTONunknownASSIGNED PAMar 31, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.178.88/298BYTEMARK-FIRETOMCOMunknownASSIGNED PAJun 10, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.178.128/2816BYTEMARK-QBYTEDNS2qbyte2 SSLASSIGNED PAFeb 8, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.178.144/2816BYTEMARK-STEFFAN-WOODSteffan Wood IPsASSIGNED PAJun 1, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.178.192/2816JOOBILI-VMSVirtual machines for JoobiliASSIGNED PAJun 4, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.178.208/2816BYTEMARK-VERONEunknownASSIGNED PAJun 15, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7
└ 212.110.179.0/298YCPV-INNOVETRAInnovetra Ltd.ASSIGNED PAApr 13, 2017abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER7

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

212.110.160.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Oct 2008 · 18 yr
Origin networks
2
Last change of origin
Oct 2008
Recorded history

History

Handoffs
1