Data as of Nov 10, 2026

79.98.78.0/25

2 residential-proxy exits · 30 days

Sys-DataCom s.r.o.

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
1.6% of its addresses · 30 days
Providers
26
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

223 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FlashProxy
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.98.72.0/21
since Aug 2016
AS44002Residential88
11 always on
Sys-DataCom s.r.o.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
79.98.72.0/212,048CZ-SYS-DATACOM-20071029Sys-DataCom s.r.o. (ORG-SS84-RIPE) · CZALLOCATED PAOct 29, 2007ripe-abuse@sys-data.com
└ 79.98.78.0/25128INFRASTRUCTURE_TTC_NAT_CUSTClients TTC 1-8 2011ASSIGNED PAMay 7, 2012ripe-abuse@sys-data.com
via CZ-SYS-DATACOM-20071029

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

79.98.78.0/24

Routing history

Pattern
Stable
First seen
Dec 2016
Current origin since
Dec 2016 · 9.9 yr
Origin networks
1