Data as of Nov 14, 2026

92.36.224.0/22

19 residential-proxy exits · 30 days

BH Telecom d.d. Sarajevo

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

Residential-proxy exits

Proxy exits
19
1.9% of its addresses · 30 days
Always-on exits
1
5.3% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
24
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

855 observations

/24s with the most always-on exits

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • Bright Data
  • Byteful
  • Decodo
  • FastProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy302
  • ProxyRack
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.36.224.0/19
since Jan 2011
AS9146Residential1,034
10 always on
BH Telecom d.d. Sarajevo
92.36.128.0/17
since Jun 2015
AS9146Residential7,296
13 always on
BH Telecom d.d. Sarajevo

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
92.36.128.0/1732,768BA-BIHNET-20080110BH Telecom d.d. Sarajevo (ORG-PEOP1-RIPE) · BAALLOCATED PAJan 10, 2008abuse@bhtelecom.ba
└ 92.36.224.0/221,024BHTELECOM-CUSTOMERS-STATICBH Telecom Customers with Static IPASSIGNED PAMay 21, 2008abuse@bhtelecom.ba
via BA-BIHNET-20080110

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

Covering aggregate above, the prefix's own history below

92.36.224.0/20

Routing history

Pattern
Stable
First seen
Jun 2008
Current origin since
Jun 2008 · 18 yr
Origin networks
1