Data as of Nov 17, 2026

5.104.168.0/23

7 residential-proxy exits · 30 days

Telehouse AD · space held by Lir.bg EOOD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Unknown
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
1.4% of its addresses · 30 days
Always-on exits
1
14% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
42
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.104.168.0/2415
5.104.169.0/2402

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • GeekProxy
  • GloryCloud
  • IPRoyal
  • Kookey
  • LAMAPROXY
  • LudaxProxy
  • NSTPROXY_LITE
  • NSTPROXY_PRIME
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PSBProxy
  • PrivateByte
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Q2IP
  • RH7Proxy
  • RapidProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • 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
5.104.160.0/198,192BG-LIR-20120629Lir.bg EOOD (ORG-LE44-RIPE) · BGALLOCATED PAJun 3, 2016abuse@lir.bg
└ 5.104.168.0/23512SisleyBuildSisleyBuild Ltd.ASSIGNED PAMar 6, 2013abuse@lir.bg
via BG-LIR-20120629

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
Mar 2013
Current origin since
Sep 2016 · 10 yr
Origin networks
2
Last change of origin
May 2013
Recorded history

History

Handoffs
1