Data as of Nov 13, 2026

77.64.168.0/24

7 residential-proxy exits · 30 days

Tele Columbus AG

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
28
selling exits here
Oct 14, 2026 – Nov 11, 2026

Exits seen per day

98 observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • ASHBURNPROXIES
  • B2Proxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • GhostConnect
  • IPMUSK
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.64.128.0/18
since Apr 2024
AS16202Residential1,175
51 always on
Tele Columbus AG
77.64.128.0/17
since Feb 2007
AS16202Residential1,416
69 always on
Tele Columbus AG

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
77.64.128.0/1732,768DE-TELECOLUMBUS-20060116Tele Columbus AG (ORG-BBG1-RIPE) · DEALLOCATED PAJan 16, 2007abuse@mip-platform.net
└ 77.64.128.0 - 77.64.176.25512,544PRIMACOM-HEADENDS-2007-1Broadband Customer NetworkASSIGNED PAJan 26, 2007abuse@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

Summary

Routing history

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