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

213.231.0.0/18

5,665 residential-proxy exits · 30 days

TOV TRK 'Briz'

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

Residential-proxy exits

Proxy exits
5,665
35% of its addresses · 30 days
Always-on exits
43
0.76% of its exits
Spread
63 of 64
/24s with at least one exit
Providers
143
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

436K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
213.231.5.0/24629
213.231.4.0/24524
213.231.7.0/24429
213.231.2.0/24425
213.231.6.0/24320
213.231.60.0/24299
213.231.56.0/24298
213.231.3.0/24238
213.231.1.0/24232
213.231.8.0/24223
213.231.61.0/241111
213.231.57.0/241109
213.231.15.0/241105
213.231.29.0/241101
213.231.44.0/24199
213.231.59.0/24196
213.231.54.0/24195
213.231.51.0/24193
213.231.58.0/24188
213.231.45.0/24180
213.231.9.0/24113
213.231.33.0/240118
213.231.52.0/240115
213.231.19.0/240112

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FROXY
  • FastProxy
  • FlashProxy
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HELODATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • JoyProxy
  • KindProxy
  • KocerRoxy
  • Kookey
  • LOKIPROXY
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYFALL
  • PROXYLANE
  • PROXYON
  • PROXYSALE
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PROXY_CC
  • PSBProxy
  • PYPROXY
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • QUANTICDATA
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • 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
213.231.0.0/1816,384UA-BRIZ-20080207TOV TRK "Briz" (ORG-TT21-RIPE) · UAALLOCATED PAFeb 7, 2008abuse@breezein.net
└ 213.231.0.0/198,192BRIZTOV TRK "Briz"ASSIGNED PAFeb 8, 2008abuse@breezein.net
via UA-BRIZ-20080207
└ 213.231.32.0/221,024BRIZTOV TRK "Briz"ASSIGNED PAFeb 5, 2009abuse@breezein.net
via UA-BRIZ-20080207
└ 213.231.36.0/221,024BRIZTOV TRK "Briz"ASSIGNED PAFeb 5, 2009abuse@breezein.net
via UA-BRIZ-20080207
└ 213.231.40.0/221,024BRIZTOV TRK "Briz"ASSIGNED PAFeb 5, 2009abuse@breezein.net
via UA-BRIZ-20080207
└ 213.231.44.0/221,024BRIZTOV TRK "Briz"ASSIGNED PAFeb 11, 2010abuse@breezein.net
via UA-BRIZ-20080207
└ 213.231.48.0/204,096BRIZTOV TRK "Briz"ASSIGNED PAFeb 11, 2010abuse@breezein.net
via UA-BRIZ-20080207

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
Feb 2008
Current origin since
Feb 2008 · 19 yr
Origin networks
1