Data as of Nov 11, 2026

77.64.199.0/24

8 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
8
3.1% of its addresses · 30 days
Providers
33
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

535 observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.64.192.0/19
since Apr 2024
AS16202Residential145
10 always on
Tele Columbus AG
77.64.128.0/17
since Feb 2007
AS16202Residential1,413
70 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.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

Summary

Routing history

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