LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

199.30.248.0/21

21 residential-proxy exits · 30 days

Salish Networks, Inc.

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

Residential-proxy exits

Proxy exits
21
1.0% of its addresses · 30 days
Always-on exits
4
19% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
53
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

15K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
199.30.251.0/2422
199.30.254.0/2416
199.30.248.0/2412
199.30.250.0/2404
199.30.249.0/2402
199.30.255.0/2402
199.30.252.0/2401
199.30.253.0/2401

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • Byteful
  • CliProxy
  • ColaProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GloryCloud
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_PREMIUM

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
199.30.248.0/212,048SALISHNET-01Salish Networks, Inc. (SN-326) · USDirect AllocationSep 20, 2010salishnetadmin@salishnetworks.com
└ 199.30.248.0/212,048TULALIP-BROADBANDTulalip Broadband (C06774980) · USReassignedOct 27, 2017salishnetadmin@salishnetworks.com
via SALISHNET-01

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Oct 2010
Current origin since
Oct 2010 · 16 yr
Origin networks
1