Data as of Nov 14, 2026

128.0.16.0/21

9 residential-proxy exits · 30 days

VEV Romerike AS

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

Residential-proxy exits

Proxy exits
9
0.44% of its addresses · 30 days
Spread
3 of 8
/24s with at least one exit
Providers
28
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

447 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
128.0.19.0/2405
128.0.20.0/2403
128.0.18.0/2401

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • AnyIP
  • BottingTools
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • SPYDERPROXY_PREMIUM
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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
128.0.16.0/212,048NO-ROMERIKEBB-20100611VEV Romerike AS (ORG-RBA3-RIPE) · NOALLOCATED PASep 14, 2012abuse@vevromerike.no
└ 128.0.16.0/24256RBB_CUSTOMERSRbb customer networkASSIGNED PAOct 15, 2014abuse@vevromerike.no
via NO-ROMERIKEBB-20100611
└ 128.0.17.0/24256RBB_CUSTOMERSRbb customer networkASSIGNED PAOct 15, 2014abuse@vevromerike.no
via NO-ROMERIKEBB-20100611
└ 128.0.18.0/24256RBB_CUSTOMERSRbb customer networkASSIGNED PAOct 15, 2014abuse@vevromerike.no
via NO-ROMERIKEBB-20100611
└ 128.0.19.0/24256RBB_CUSTOMERSRbb customer networkASSIGNED PAOct 15, 2014abuse@vevromerike.no
via NO-ROMERIKEBB-20100611
└ 128.0.20.0/24256GREPPERUD_NETAHB nettASSIGNED PAMay 24, 2013abuse@vevromerike.no
via NO-ROMERIKEBB-20100611
└ 128.0.21.0/24256RBB_CUSTOMERSRbb customer networkASSIGNED PAOct 15, 2014abuse@vevromerike.no
via NO-ROMERIKEBB-20100611
└ 128.0.22.0/24256RBB_CUSTOMERSRbb customer networkASSIGNED PAOct 15, 2014abuse@vevromerike.no
via NO-ROMERIKEBB-20100611
└ 128.0.23.0/24256InnovasjonAS_peeringInnovasjonPIASSIGNED PADec 19, 2012abuse@vevromerike.no
via NO-ROMERIKEBB-20100611

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
Feb 2013
Current origin since
Feb 2019 · 7.8 yr
Origin networks
1