Data as of Nov 20, 2026

213.148.23.0/24

2 residential-proxy exits · 30 days

'Servercore CIS' FE LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
21
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

120 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • Byteful
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GSocks
  • HELODATA
  • Infatica
  • KindProxy
  • MangoProxy
  • NSTPROXY_LITE
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.148.20.0/22
since Aug 2023
AS43647Hosting3"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.20.0/221,024UZ-SERVERCORE-NETServercore UZ NetworkSUB-ALLOCATED PASep 28, 2023abuse@servercore.com
via UZ-SERVERCORE-19991210
└ 213.148.23.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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Reactivated
First seen
Oct 2017
Current origin since
Aug 2024 · 2.2 yr
Origin networks
2
Last change of origin
Aug 2024
Recorded history

History

Handoffs
1