LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

46.45.4.0/22

160 residential-proxy exits · 30 days

Vega-Service, LLC

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

Residential-proxy exits

Proxy exits
160
16% of its addresses · 30 days
Always-on exits
5
3.1% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
68
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

9.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.45.7.0/24238
46.45.6.0/24234
46.45.5.0/24138
46.45.4.0/24049

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_LITE

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
46.45.0.0/1816,384RU-VEGASERVICE-20100902Vega-Service, LLC (ORG-VL75-RIPE) · RUALLOCATED PASep 2, 2010koprsnz@gmail.com
└ 46.45.0.0/198,192VEGA-NETVega Service, LLCASSIGNED PAMar 30, 2011koprsnz@gmail.com
via RU-VEGASERVICE-20100902

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2012
Current origin since
Jan 2012 · 15 yr
Origin networks
1