Data as of Nov 10, 2026

83.166.0.0/21

3 residential-proxy exits · 30 days

Servanet AB

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

Residential-proxy exits

Proxy exits
3
0.15% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
22
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.166.6.0/2402
83.166.5.0/2401

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GloryCloud
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • Oxylabs
  • Proxiware
  • ProxyWing
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.166.0.0/19AS31507Residential9
1 always on
Servanet AB

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
83.166.0.0/198,192SE-SERVANET1-20040524Servanet AB (ORG-SA4988-RIPE) · SEALLOCATED PANov 23, 2022abuse@serva.net
└ 83.166.0.0/212,048SERVA-NETServaNets IP NetworkASSIGNED PAJun 9, 2004abuse@serva.net
via SE-SERVANET1-20040524

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
May 2005 · 22 yr
Origin networks
1