Data as of Nov 20, 2026

213.148.18.0/23

1 residential-proxy exit · 30 days

'Servercore CIS' FE LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
19
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

88 observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • FlashProxy
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • Kookey
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
213.148.18.0/24
since Jul 2024
AS43647Hosting"Servercore CIS" FE LLC
via Servercore UZ Network
213.148.19.0/24
since Jul 2024
AS43647Hosting1"Servercore CIS" FE LLC
via Servercore UZ Network

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.16.0/212,048UZ-SERVERCORE-19991210"Servercore CIS" FE LLC (ORG-CFL8-RIPE) · UZALLOCATED PAJul 25, 2025abuse@servercore.com
└ 213.148.18.0/23512UZ-SERVERCORE-NETServercore UZ NetworkSUB-ALLOCATED PASep 28, 2023abuse@servercore.com
via UZ-SERVERCORE-19991210
└ 213.148.18.0/24256SERVERCORE-NETServercore UZ NetworkASSIGNED PAAug 22, 2023abuse@servercore.com
via UZ-SERVERCORE-NET
└ 213.148.19.0/24256SERVERCORE-NETServercore UZ NetworkASSIGNED PAAug 22, 2023abuse@servercore.com
via UZ-SERVERCORE-NET

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
Aug 2023
Current origin since
Aug 2023 · 3.3 yr
Origin networks
1