Data as of Nov 17, 2026

213.148.24.0/22

6 residential-proxy exits · 30 days

Modern Server Solutions LLP

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
23
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

99 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
213.148.26.0/2404
213.148.25.0/2401
213.148.27.0/2401

Proxy providers listing exits

  • 9HTTP
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • IPPeak
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
213.148.24.0/24
since Jul 2024
AS48988HostingModern Server Solutions LLP
213.148.25.0/24
since Jul 2024
AS48988Hosting1Modern Server Solutions LLP
213.148.26.0/24
since Jul 2024
AS48988Hosting4Modern Server Solutions LLP
213.148.27.0/24
since Jul 2024
AS48988Hosting1Modern Server Solutions LLP

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.148.24.0/221,024KZ-MSS-19991210Modern Server Solutions LLP (ORG-MSSL44-RIPE) · KZALLOCATED PAAug 13, 2025abuse@servercore.com
└ 213.148.24.0/24256KZ-SERVERCORE-NETServercore NetworkASSIGNED PADec 20, 2023abuse@servercore.com
via KZ-MSS-19991210
└ 213.148.25.0/24256KZ-SERVERCORE-NETServercore NetworkASSIGNED PADec 20, 2023abuse@servercore.com
via KZ-MSS-19991210
└ 213.148.26.0/24256KZ-SERVERCORE-NETServercore NetworkASSIGNED PADec 20, 2023abuse@servercore.com
via KZ-MSS-19991210
└ 213.148.27.0/24256KZ-SERVERCORE-NETServercore NetworkASSIGNED PADec 20, 2023abuse@servercore.com
via KZ-MSS-19991210

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2023
Current origin since
Dec 2023 · 2.9 yr
Origin networks
1