Data as of Nov 11, 2026

91.183.80.0/22

13 residential-proxy exits · 30 days

Proximus NV

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

Residential-proxy exits

Proxy exits
13
1.3% of its addresses · 30 days
Always-on exits
2
15% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
35
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.8K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EnigmaProxy
  • Evomi
  • FROXY
  • FlexyProxies
  • FloppyData
  • GSocks
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • StrikeProxy
  • Thordata
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.180.0.0/14
since Sep 2006
AS5432Residential5,681
284 always on
Proximus NV

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
91.176.0.0/13524,288BE-BELGACOM-20060904Proximus NV (ORG-BA4-RIPE) · BEALLOCATED PASep 4, 2006abuse@proximus.com
└ 91.183.80.0/221,024BE-SKYNET-20011108Pro BrusselASSIGNED PAOct 11, 2010abuse@proximus.com
via BE-BELGACOM-20060904

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

91.183.0.0/16

Routing history

Pattern
Stable
First seen
Oct 2022
Current origin since
Oct 2022 · 4.0 yr
Origin networks
1