Data as of Nov 12, 2026

64.223.232.0/23

5 residential-proxy exits · 30 days

Fidium

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

Residential-proxy exits

Proxy exits
5
0.98% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
33
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
64.223.233.0/2403
64.223.232.0/2402

Proxy providers listing exits

  • 2Captcha
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • DataImpulse
  • FastProxy
  • GSocks
  • GeekProxy
  • GonzoProxy
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PSBProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • VitalProxy

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
64.223.192.0/1816,384VZGNI-PUB-5Fidium (CC-4441) · USDirect AllocationMar 1, 2000abuse@consolidated.net
└ 64.223.224.0 - 64.223.241.04,353FIDIUM-NNE-5Verizon (C00783885) · USReassignedMar 12, 2004abuse@consolidated.net
via VZGNI-PUB-5

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