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

217.68.161.0/24

1 residential-proxy exit · 30 days

Tele Columbus AG

Announcement
217.68.160.0/19
RPKI valid
Announced by
AS16202
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
3
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

6 observations

Proxy providers listing exits

  • FastProxy
  • KocerRoxy
  • LemonBright

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.68.160.0/198,192DE-TELECOLUMBUS-20001115Tele Columbus AG (ORG-BBG1-RIPE) · DEALLOCATED PADec 10, 2001abuse@mip-platform.net
└ 217.68.161.0/2816PRIMACOM-3bPrimacom AGASSIGNED PAApr 13, 2006abuse@mip-platform.net
via DE-TELECOLUMBUS-20001115
└ 217.68.161.16/2816PRIMACOM-4Primacom AGASSIGNED PAMay 3, 2006abuse@mip-platform.net
via DE-TELECOLUMBUS-20001115
└ 217.68.161.32 - 217.68.161.11180PRIMACOM-6Primacom AGASSIGNED PASep 9, 2008abuse@mip-platform.net
via DE-TELECOLUMBUS-20001115
└ 217.68.161.112/2816PRIMACOM-5Primacom AGASSIGNED PADec 14, 2006abuse@mip-platform.net
via DE-TELECOLUMBUS-20001115
└ 217.68.161.128/2664PRIMACOM-2Primacom Berlin GmbHASSIGNED PAMar 3, 2003abuse@mip-platform.net
via DE-TELECOLUMBUS-20001115
└ 217.68.161.192/2664PRIMACOM-SERVERHOUSINGPrimacom Berlin GmbHASSIGNED PAMay 15, 2003abuse@mip-platform.net
via DE-TELECOLUMBUS-20001115

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 217.68.160.0/19

217.68.160.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1