Data as of Nov 13, 2026

81.18.232.0/22

28 residential-proxy exits · 30 days

P/F Telefonverkid

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

Residential-proxy exits

Proxy exits
28
2.7% of its addresses · 30 days
Always-on exits
1
3.6% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
44
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.6K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 9Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonLabs
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.18.224.0/204,096FO-FOTELECOM-20020121P/F Telefonverkid (ORG-FT1-RIPE) · FOALLOCATED PAApr 10, 2002abuse@internet.fo
└ 81.18.232.0/221,024DHCP-Broadband-networkunknownASSIGNED PAJun 15, 2021abuse@internet.fo
via FO-FOTELECOM-20020121

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 81.18.224.0/20

81.18.224.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Nov 2014 · 12 yr
Origin networks
2
Last change of origin
Nov 2014
Recorded history

History

Handoffs
1