Data as of Nov 11, 2026

185.22.4.0/24

1 residential-proxy exit · 30 days

MLL Telecom Ltd.

Announcement
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
2
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

5 observations

Proxy providers listing exits

  • RainProxy
  • Shifter

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.22.4.0/221,024UK-MLLTELECOM-20180219MLL Telecom Ltd. (ORG-MTL37-RIPE) · GBALLOCATED PAApr 9, 2020Security.alerts@mlltelecom.com
└ 185.22.4.0/298MLL-CUST-BCP-185_22_4_0-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.8/304MLL-CUST-SCC-185_22_4_8-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.12/304MLL-CUST-SCC-185_22_4_12-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.16/304MLL-CUST-NUTH-185_22_4_16-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.20/304MLL-CUST-NUTH-185_22_4_20-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.24/298MLL-CUST-Notts-185_22_4_24-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.32/2816MLL-INFRA-185_22_4_32-28unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.48/2816MLL-INFRA-185_22_4_48-28unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.64/304MLL-CUST-WSC-185_22_4_64-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.68/304MLL-CUST-WSC-185_22_4_68-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.72/304MLL-CUST-WSC-185_22_4_72-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.76/304MLL-CUST-WSC-185_22_4_76-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.80/304MLL-CUST-SCC-185_22_4_80-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.84/304MLL-CUST-SCC-185_22_4_84-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.88/304MLL-CUST-SCC-185_22_4_88-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.92/304MLL-CUST-SCC-185_22_4_92-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.96/304MLL-CUST-SCC-185_22_4_96-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.100/304MLL-CUST--185_22_4_100-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.104/298MLL-CUST-NHSPS-185_22_4_104-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.112/298MLL-CUST-SCC-185_22_4_112-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.120/298MLL-CUST-NHSPS-185_22_4_120-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.128/298MLL-CUST-NHSPS-185_22_4_128-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.136/304MLL-CUST-SCC-185_22_4_136-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.140/304MLL-CUST--185_22_4_140-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.144/304MLL-CUST-SCC-185_22_4_144-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.148/304MLL-CUST-SCC-185_22_4_148-30unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.152/298MLL-CUST-LinCoin-185_22_4_152-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.160/298MLL-CUST-NHSPS-185_22_4_160-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.168/298MLL-CUST-NHSPS-185_22_4_168-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.176/298MLL-CUST-NHSPS-185_22_4_176-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.184/298MLL-CUST-NHSPS-185_22_4_184-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.192/298MLL-CUST-TKAT-185_22_4_192-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.200/298MLL-CUST-TKAT-185_22_4_200-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.208/298MLL-CUST-TKAT-185_22_4_208-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.216/298MLL-INFRA-185_22_4_216-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.224/298MLL-INFRA-185_22_4_224-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.232/298MLL-CUST-NHSPS-185_22_4_232-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.240/298MLL-CUST-NHSPS-185_22_4_240-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219
└ 185.22.4.248/298MLL-CUST-NHSPS-185_22_4_248-29unknownASSIGNED PAMar 16, 2021Security.alerts@mlltelecom.com
via UK-MLLTELECOM-20180219

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 185.22.4.0/22

185.22.4.0/22

Routing history

Pattern
Stable
First seen
Apr 2013
Current origin since
Apr 2020 · 6.6 yr
Origin networks
4
Last change of origin
Apr 2020
Recorded history

History

Handoffs
3