Data as of Nov 10, 2026

77.64.201.0/24

6 residential-proxy exits · 30 days

Tele Columbus AG

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin May 2026
its first announcement on record

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
29
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

481 observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • BirdProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • IPPeak
  • Infatica
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.64.192.0/19
since Apr 2024
AS16202Residential148
13 always on
Tele Columbus AG
77.64.128.0/17
since Feb 2007
AS16202Residential1,414
92 always on
Tele Columbus AG

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.64.128.0/1732,768DE-TELECOLUMBUS-20060116Tele Columbus AG (ORG-BBG1-RIPE) · DEALLOCATED PAJan 16, 2007abuse@mip-platform.net
└ 77.64.177.0 - 77.64.208.2558,192PRIMACOM-HEADENDS-2009-01Primacom Berlin GmbHASSIGNED PAJan 12, 2009abuse@mip-platform.net
via DE-TELECOLUMBUS-20060116

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

77.64.200.0/23

Routing history

Pattern
Stable
First seen
May 2026
Current origin since
May 2026 · 5 mo
Origin networks
1