Data as of Nov 11, 2026

46.28.68.0/24

5 residential-proxy exits · 30 days

Route 95 LLC

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
43
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • Maskify
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VibeProxies
  • VitalExclusive

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.28.64.0/212,048US-R95-20100721Route 95 LLC (ORG-RL646-RIPE) · USALLOCATED PAAug 11, 2026abuse@route95.net
└ 46.28.68.0/24256GF-MXP-NETunknownASSIGNED PAAug 9, 2025abuse@route95.net
via US-R95-20100721

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