Data as of Nov 12, 2026

216.158.96.0/20

38 residential-proxy exits · 30 days

Junet AB

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

Residential-proxy exits

Proxy exits
38
0.93% of its addresses · 30 days
Always-on exits
1
2.6% of its exits
Spread
15 of 16
/24s with at least one exit
Providers
59
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.0K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

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
216.158.96.0/204,096SE-JUNET-20020531Junet AB (ORG-JA160-RIPE) · SEALLOCATED PANov 16, 2016abuse@junet.se
└ 216.158.96.0/24256WN-DHCPunknownASSIGNED PAJan 26, 2017abuse@junet.se
via SE-JUNET-20020531
└ 216.158.97.0/24256WN-DHCPunknownASSIGNED PAJan 26, 2017abuse@junet.se
via SE-JUNET-20020531
└ 216.158.98.0/24256WN-DHCPunknownASSIGNED PAJan 26, 2017abuse@junet.se
via SE-JUNET-20020531
└ 216.158.99.0/24256WN-DHCPunknownASSIGNED PAJan 26, 2017abuse@junet.se
via SE-JUNET-20020531
└ 216.158.100.0/221,024TRAMAN-DHCP-BNGunknownASSIGNED PAMay 17, 2017abuse@junet.se
via SE-JUNET-20020531
└ 216.158.104.0/23512WN-DHCPunknownASSIGNED PAFeb 12, 2018abuse@junet.se
via SE-JUNET-20020531
└ 216.158.106.0/24256KUNGALV-DHCPunknownASSIGNED PAFeb 12, 2018abuse@junet.se
via SE-JUNET-20020531
└ 216.158.107.0/24256KUNGALV-DHCPunknownASSIGNED PAFeb 12, 2018abuse@junet.se
via SE-JUNET-20020531
└ 216.158.108.0/24256JUNET-FREEunknownASSIGNED PAJan 30, 2019abuse@junet.se
via SE-JUNET-20020531
└ 216.158.109.0/25128KUNGALV-DHCPunknownASSIGNED PAFeb 12, 2018abuse@junet.se
via SE-JUNET-20020531
└ 216.158.110.0/24256OPENBIT-DHCPunknownASSIGNED PAFeb 12, 2018abuse@junet.se
via SE-JUNET-20020531
└ 216.158.111.0/24256JUNET-FREEunknownASSIGNED PAApr 24, 2017abuse@junet.se
via SE-JUNET-20020531

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
May 2005
Current origin since
Nov 2016 · 10.0 yr
Origin networks
3
Last change of origin
Nov 2016
Recorded history

History

Handoffs
2