LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

217.79.84.0/23

504 residential-proxy exits · 30 days

Unics EOOD

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

Residential-proxy exits

Proxy exits
504
98% of its addresses · 30 days
Always-on exits
4
0.79% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
61
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

14K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.79.84.0/242252
217.79.85.0/242252

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CROXY
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PacketStream
  • PrivateByte
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
217.79.84.0/23512BG-UNICS-20030121Unics EOOD (ORG-UE5-RIPE) · BGALLOCATED PAJul 24, 2025admin@globcom.net
└ 217.79.84.0/24256BG-UNICSunknownASSIGNED PAJul 24, 2025admin@globcom.net
via BG-UNICS-20030121
└ 217.79.85.0/24256BG-UNICSunknownASSIGNED PAJul 24, 2025admin@globcom.net
via BG-UNICS-20030121

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
Jan 2013
Current origin since
Jul 2025 · 1.3 yr
Origin networks
2
Last change of origin
Jul 2025
Recorded history

History

Handoffs
1