Data as of Nov 16, 2026

82.118.1.0/24

3 residential-proxy exits · 30 days

MISS.NET d.o.o.

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
38
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.118.0.0/20
since Sep 2015
AS57869Residential116
5 always on
MISS.NET d.o.o.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.118.0.0/204,096BA-MISSNET-20110826MISS.NET d.o.o. (ORG-MD31-RIPE) · BAALLOCATED PAAug 26, 2011abuse@miss.net.ba
└ 82.118.1.0/24256MISSNETMissnet d.o.o BihacASSIGNED PANov 30, 2012abuse@miss.net.ba
via BA-MISSNET-20110826

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

82.118.0.0/22

Routing history

Pattern
Stable
First seen
Nov 2011
Current origin since
Dec 2012 · 14 yr
Origin networks
2
Last change of origin
Dec 2012
Recorded history

History

Handoffs
1