Data as of Nov 11, 2026

79.98.74.0/24

3 residential-proxy exits · 30 days

Sys-DataCom s.r.o.

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
28
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

303 observations

Proxy providers listing exits

  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

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

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
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.74.0/25128SYS-DATACOM_CUKRAKSys-datacom, s.r.o.ASSIGNED PASep 26, 2012ripe-abuse@sys-data.com
via CZ-SYS-DATACOM-20071029
└ 79.98.74.128/25128SYS-DATACOM_INFRASTRUCTUREClients TTCASSIGNED PASep 6, 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

Summary

Routing history

Pattern
Stable
First seen
Jun 2010
Current origin since
Jun 2010 · 16 yr
Origin networks
1