Data as of Nov 11, 2026

178.20.22.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
19
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

63 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • Datarama
  • EZProxies
  • Evomi
  • Geonode
  • HideProxy
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • ProxyGeo
  • Proxyma
  • ResiProxies
  • Shifter
  • Thordata

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.20.16.0/21
since Jul 2017
AS204170Residential354
54 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
178.20.16.0/212,048OM-AWASER-20100216Awaser Oman LLC (ORG-AOL7-RIPE) · OMALLOCATED PAJul 10, 2017abuse@awasr.com
└ 178.20.22.0/24256OM-AWASERunknownASSIGNED PAAug 8, 2017abuse@awasr.com
via OM-AWASER-20100216

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
Oct 2017
Current origin since
Oct 2017 · 9.1 yr
Origin networks
1