Data as of Nov 13, 2026

96.9.130.0/24

12 residential-proxy exits · 30 days

Awaser Oman LLC

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
42
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AnyIP
  • B2Proxy
  • BlurPath
  • BottingTools
  • BuyingProxy
  • Byteful
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • Maskify
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • Webshare
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
96.9.128.0/19
since Mar 2016
AS204170Residential1,407
201 always on
Awaser Oman LLC

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
96.9.128.0/198,192OM-AWASER-20150504Awaser Oman LLC (ORG-AOL7-RIPE) · OMALLOCATED PAFeb 29, 2016abuse@awasr.com
└ 96.9.130.0/24256OM-AWASERunknownASSIGNED PAAug 8, 2017abuse@awasr.com
via OM-AWASER-20150504

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

Summary

Routing history

Pattern
Stable
First seen
Jul 2015
Current origin since
Sep 2016 · 10 yr
Origin networks
2
Last change of origin
Sep 2016
Recorded history

History

Handoffs
1