LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

83.166.24.0/21

6 residential-proxy exits · 30 days

Servanet AB

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

Residential-proxy exits

Proxy exits
6
0.29% of its addresses · 30 days
Always-on exits
1
17% of its exits
Spread
4 of 8
/24s with at least one exit
Providers
23
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.166.27.0/2412
83.166.24.0/2402
83.166.26.0/2401
83.166.29.0/2401

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BottingTools
  • BuyingProxy
  • Byteful
  • Datarama
  • Evomi
  • FastProxy
  • GloryCloud
  • IPCola
  • IPFly
  • IPPeak
  • IPRoyal
  • InfiniteProxies
  • LemonBright
  • NovaProxy
  • Novada
  • Oxylabs
  • ProxyRack
  • RapidProxy
  • SwiftProxy
  • Thordata
  • VitalExclusive

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.24.0/212,048SERVA-NET-2ServaNets IP Network 2ASSIGNED PAMay 9, 2006abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2006
Current origin since
Jun 2006 · 20 yr
Origin networks
1