Data as of Nov 14, 2026

206.84.80.0/23

384 residential-proxy exits · 30 days

Somos Networks Colombia S.A.S. BIC · space held by Cogent Communications, LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
384
75% of its addresses · 30 days
Always-on exits
384
100% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
35
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.5M observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
206.84.81.0/24256256
206.84.80.0/24128128

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • Maskify
  • NSocks
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
206.84.0.0/15
since Jun 2005
AS174Internet provider9,219
1,261 always on
Cogent Communications, LLC
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
206.84.80.0/24
since Sep 2022
AS271957Residential128
128 always on
Cogent Communications, LLC
206.84.81.0/24
since Feb 2023
AS271957Residential256
256 always on
Cogent Communications, 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
206.84.0.0/15131,072COGENT-206-84-15Cogent Communications, LLC (COGC) · USDirect AllocationAug 10, 1995abuse@cogentco.com
└ 206.84.80.0/23512SOMOS-CGNT-NET-1Somos Networks Colombia S.A.S. BIC (C08844101) · COReassignedAug 26, 2022abuse@cogentco.com
via COGENT-206-84-15

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
Sep 2022
Current origin since
Sep 2022 · 4.2 yr
Origin networks
1