Data as of Nov 13, 2026

80.91.223.0/24

22 residential-proxy exits · 30 days

Ferdinand Zink trading as Tube-Hosting

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
95 / 100 · Critical
Spamhaus DROP · Proxy exits nearby

Residential-proxy exits

Proxy exits
22
8.6% of its addresses · 30 days
Always-on exits
16
73% of its exits
Providers
60
selling exits here
Oct 14, 2026 – Nov 11, 2026

Exits seen per day

37K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PacketStream
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • 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
80.91.223.0/24256DE-FERDINANDZINK-20220125Ferdinand Zink trading as Tube-Hosting (ORG-FZTA2-RIPE) · DEALLOCATED PAFeb 24, 2025abuse@tube-hosting.de
└ 80.91.223.96/2732AlaricHostAlarichost (ORG-AA3323-RIPE)SUB-ALLOCATED PAJul 7, 2025abuse@tube-hosting.de
via DE-FERDINANDZINK-20220125
└ 80.91.223.160/298FastLayerFastLayer (ORG-FA1201-RIPE)SUB-ALLOCATED PAMay 22, 2022abuse@fastlayer.eu
└ 80.91.223.192/2664SkillHostSkyPass Solutions Sp. z.o.o. (ORG-SA4902-RIPE) · PLSUB-ALLOCATED PAFeb 21, 2022ripe@skypass.tech

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
Rotating
First seen
Jan 2022
Current origin since
Apr 2022 · 4.6 yr
Origin networks
2
Last change of origin
Apr 2022
Recorded history

History

Handoffs
1