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

46.43.48.0/20

No anonymizer space · no proxy exits in 30 days

Iomart Managed Services Limited

Announcement
46.43.0.0/18
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
46.43.0.0/1816,384UK-RAPIDSWITCH-20100810Iomart Managed Services Limited (ORG-RL20-RIPE) · GBALLOCATED PAApr 15, 2021abuse@rapidswitch.com
└ 46.43.48.0/204,096BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8unknownLIR-PARTITIONED PASep 2, 2010abuse@rapidswitch.com
via UK-RAPIDSWITCH-20100810
└ 46.43.48.160/2816BYTEMARK-IDEAWORKSunknownASSIGNED PASep 27, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.48.216/298BYTEMARK-CAFFECaffe SSLASSIGNED PANov 10, 2010abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.48.240/2816BYTEMARK-DMCDMC VlanASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.50.32/2816BYTEMARK-BOTICCABoticca VlanASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.50.128/2816BYTEMARK-TB1GNSTB1GNS SSLASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.50.160/298BYTEMARK-1-2-MOBILE1-2-Mobile VlanASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.50.168/298BYTEMARK-ABECEDERAbeceder SSLASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.50.224/2816BYTEMARK-KOLLIDEKollide SSLASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.51.104/298BYTEMARK-BAMBABamba SSLASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.51.128/2732BYTEMARK-BETELGEUSEBetelgeuse SSLASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.52.64/2816BYTEMARK-PLACIDPlacid SSLASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.52.160/2816BYTEMARK-CAPRICACaprica SSLASSIGNED PAFeb 2, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.52.176/2816BYTEMARK-DMC-VLANunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.53.224/2816BYTEMARK-SURETEC-VLANunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.53.240/2816BYTEMARK-DLISTER-VLANunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.55.32/2816BYTEMARK-BIGIRON3-SSLunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.55.72/298BYTEMARK-CLOUDY-SSLunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.55.96/2732BYTEMARK-EXACTMOBILE-SERVICESunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.55.208/2816BYTEMARK-VORARI-YRKunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.55.224/298BYTEMARK-BRSTOLANGLING-SSLunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.56.16/298BYTEMARK-SHILLING-SSLunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.56.24/298BYTEMARK-ODIN-SSLunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.56.192/2732BYTEMARK-PTFS-YRKunknownASSIGNED PAFeb 24, 2012abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.57.0/24256BYTEMARK-INDIVIDUALIndividual Additional IPsASSIGNED PAJan 20, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8
└ 46.43.58.0/24256BYTEMARK-STAGINGunknownASSIGNED PAJan 12, 2011abuse@rapidswitch.com
via BYTEMARK-CUSTOMERBLOCKS-MANCHESTER8

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 46.43.0.0/18

46.43.0.0/18

Routing history

Pattern
Stable
First seen
Aug 2010
Current origin since
Aug 2010 · 16 yr
Origin networks
1