Data as of Nov 13, 2026

136.29.128.0/18

23 residential-proxy exits · 30 days

Webpass Inc.

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

Residential-proxy exits

Proxy exits
23
0.14% of its addresses · 30 days
Always-on exits
2
8.7% of its exits
Spread
11 of 64
/24s with at least one exit
Providers
56
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

5.4K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

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
136.24.0.0/13524,288WEBPAWebpass Inc. (WEBPA) · USDirect AllocationOct 31, 2016abuse@googlefiber.net
└ 136.29.128.0/1816,384NASHVILLE-1Webpass Inc. (C07430017) · USReassignedSep 19, 2019abuse@googlefiber.net
via WEBPA

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