Data as of Nov 11, 2026

206.0.3.0/24

30 residential-proxy exits · 30 days

Bindnet RJ · space held by Cogent Communications, LLC

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
30
12% of its addresses · 30 days
Always-on exits
2
6.7% of its exits
Providers
69
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

8.0K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPCola
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LemonLabs
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
206.0.0.0/15
since Jan 2011
AS174Internet provider18,556
940 always on
Cogent Communications, LLC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
206.0.0.0 - 206.2.255.255196,608COGENT-206-0-1-2-16Cogent Communications, LLC (COGC) · USDirect AllocationMay 8, 1995abuse@cogentco.com
└ 206.0.0.0/221,024INFORMATICA-CGNT-NET-1F. L. Cahue de Oliveira - Informatica (C08367121) · BRReassignedMay 5, 2022abuse@cogentco.com
via COGENT-206-0-1-2-16

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

206.0.0.0/22

Routing history

Pattern
Stable
First seen
May 2022
Current origin since
May 2022 · 4.5 yr
Origin networks
1