Data as of Nov 12, 2026

212.46.0.0/23

3 residential-proxy exits · 30 days

AO 'Asvt'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
26
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.46.0.0/2411
212.46.1.0/2402

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.46.0.0/19
since Aug 2016
AS8752Residential89
9 always on
AO "Asvt"

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
212.46.0.0/198,192RU-ISKRA-980307AO "Asvt" (ORG-ZA2-RIPE) · RUALLOCATED PA—abuse@asvt.ru
└ 212.46.0.0/24256ASVTunknownASSIGNED PA—abuse@asvt.ru
via RU-ISKRA-980307
└ 212.46.1.0/24256ASVTunknownASSIGNED PA—abuse@asvt.ru
via RU-ISKRA-980307

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
Stable
First seen
Aug 2025
Current origin since
Aug 2025 · 1.2 yr
Origin networks
1