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

86.56.0.0/18

7 residential-proxy exits · 30 days

Tele Columbus AG

Announcement
86.56.0.0/17
RPKI valid
Announced by
AS20880
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
0.04% of its addresses · 30 days
Spread
4 of 64
/24s with at least one exit
Providers
22
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

209 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
86.56.4.0/2403
86.56.7.0/2402
86.56.22.0/2401
86.56.31.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • Byteful
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • Infatica
  • Kookey
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • ProxyEmpire
  • Proxyma
  • Shifter
  • TalorData
  • ThunderProxy
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.56.0.0/1732,768DE-TELECOLUMBUS-20050413Tele Columbus AG (ORG-BBG1-RIPE) · DEALLOCATED PAApr 13, 2005abuse@mip-platform.net
└ 86.56.0.0 - 86.56.35.2559,216TELECOLUMBUSTele Columbus AGASSIGNED PAApr 13, 2005abuse@mip-platform.net
via DE-TELECOLUMBUS-20050413
└ 86.56.36.0 - 86.56.51.2554,096TELECOLUMBUSTele Columbus AGASSIGNED PAApr 24, 2006abuse@mip-platform.net
via DE-TELECOLUMBUS-20050413
└ 86.56.52.0 - 86.56.69.2554,608TELECOLUMBUSTele Columbus AGASSIGNED PAAug 24, 2006abuse@mip-platform.net
via DE-TELECOLUMBUS-20050413

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 86.56.0.0/17

86.56.0.0/17

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Dec 2010 · 16 yr
Origin networks
2
Last change of origin
Dec 2010
Recorded history

History

Handoffs
1