Data as of Nov 16, 2026

188.74.48.0/20

131 residential-proxy exits · 30 days

FELKATEC Software GmbH & Co. KG

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

Residential-proxy exits

Proxy exits
131
3.2% of its addresses · 30 days
Spread
9 of 16
/24s with at least one exit
Providers
53
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

3.8K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9HTTP
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GhostConnect
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LOKIPROXY
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

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
188.74.48.0/204,096DE-FELKATEC-20110106FELKATEC Software GmbH & Co. KG (ORG-FSGC1-RIPE) · DEALLOCATED PASep 16, 2015abuse@felkatec.de
└ 188.74.48.0/24256felkatec-1unknownASSIGNED PAOct 28, 2022abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.49.0/24256felkatec-2unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.50.0/24256felkatec-3unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.51.0/24256felkatec-4unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.52.0/24256felkatec-5unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.53.0/24256felkatec-6unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.54.0/23512felkatec-7unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.56.0/23512felkatec-8unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.58.0/24256felkatec-9unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.59.0/24256felkatec-10unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.60.0/24256felkatec-11unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.61.0/24256felkatec-12unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.62.0/24256felkatec-13unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106
└ 188.74.63.0/24256felkatec-14unknownASSIGNED PAAug 23, 2024abuse@felkatec.de
via DE-FELKATEC-20110106

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2017
Current origin since
Dec 2017 · 8.9 yr
Origin networks
1