Data as of Nov 16, 2026

212.7.23.0/24

2 residential-proxy exits · 30 days

AS Infonet

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
20
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

114 observations

Proxy providers listing exits

  • 2Extract
  • BirdProxies
  • BuyingProxy
  • ByteProxies
  • Byteful
  • Datarama
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • Shifter
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.7.0.0/198,192EE-INFONET-980316AS Infonet (ORG-AI2-RIPE) · EEALLOCATED PA—abuse@infonet.ee
└ 212.7.23.0/2664INFONET-CABLE-MODEM-POOL23-1AS InfonetASSIGNED PASep 19, 2002abuse@infonet.ee
via EE-INFONET-980316
└ 212.7.23.64/2664INFONET-CABLE-MODEM-POOL23-2AS InfonetASSIGNED PASep 19, 2002abuse@infonet.ee
via EE-INFONET-980316
└ 212.7.23.128/2664INFONET-CABLE-MODEM-POOL23-3AS InfonetASSIGNED PASep 19, 2002abuse@infonet.ee
via EE-INFONET-980316
└ 212.7.23.192/2664INFONET-CABLE-MODEM-POOL23-4AS InfonetASSIGNED PASep 19, 2002abuse@infonet.ee
via EE-INFONET-980316

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 212.7.0.0/19

212.7.0.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1