Data as of Nov 13, 2026

37.9.61.0/24

No anonymizer space · no proxy exits in 30 days

UK Dedicated Servers Limited

Announcement
RPKI valid
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
37.9.56.0/212,048UK-UKSERVERS-20111214UK Dedicated Servers Limited (ORG-UDSL2-RIPE) · GBALLOCATED PAJul 23, 2013abuse@ukservers.com
└ 37.9.61.0/298BUK001BUK001ASSIGNED PAJul 11, 2023abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.8/298MUR006MUR006ASSIGNED PAJun 30, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.16/304NuWeb-Solutions-LTDNuWeb Solutions LTDASSIGNED PAJun 7, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.20/304UKDSL-INFAunknownASSIGNED PASep 4, 2018abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.24/304SPE005SPE005ASSIGNED PAJun 10, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.28/304FRA002FRA002ASSIGNED PAMay 25, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.32/298HOW002-DHCPunknownASSIGNED PAMay 5, 2021abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.40/304BAR018BAR018ASSIGNED PAMar 18, 2025abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.44/304MIN006MIN006ASSIGNED PAMar 19, 2025abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.48/298SMI002SMI002ASSIGNED PADec 5, 2014abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.56/298GIB001GIB001ASSIGNED PAMay 26, 2016abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.64/2732STA005STA005ASSIGNED PAAug 7, 2019abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.96/304HOW002HOW002ASSIGNED PAMar 19, 2023abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.100/304FAW001FAW001ASSIGNED PAMar 21, 2023abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.104/298PINGPIPEPINGPIPEASSIGNED PAMar 21, 2023abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.128/298WEA001WEA001ASSIGNED PAMay 11, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.136/298SEP001SEP001ASSIGNED PANov 16, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.144/2816POR005POR005ASSIGNED PAJan 26, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.160/298DIP001DIP001ASSIGNED PAJul 3, 2020abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.168/304GRE010GRE010ASSIGNED PASep 25, 2024abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.172/304SHA015SHA015ASSIGNED PADec 28, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.176/304THO009THO009ASSIGNED PASep 26, 2018abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.180/304STA012STA012ASSIGNED PAAug 9, 2024abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.184/304SUM002SUM002ASSIGNED PADec 14, 2022abuse@ukservers.com
via UK-UKSERVERS-20111214
└ 37.9.61.188/304MAS004MAS004ASSIGNED PAJun 11, 2019abuse@ukservers.com
via UK-UKSERVERS-20111214

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 37.9.56.0/21

37.9.56.0/21

Routing history

Pattern
Stable
First seen
Jul 2013
Current origin since
Jul 2013 · 13 yr
Origin networks
1