LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

217.66.136.0/21

2 residential-proxy exits · 30 days

NetCom BW GmbH

Announcement
this exact prefix
RPKI valid
Announced by
AS41998
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
2
0.10% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
8
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

42 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.66.140.0/2401
217.66.141.0/2401

Proxy providers listing exits

  • EnigmaProxy
  • FloppyData
  • LemonBright
  • NovaProxy
  • ProxyEmpire
  • ProxyRack
  • ThunderProxy
  • VantageProxies

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
217.66.136.0/212,048DE-ODR-TKG-20001106NetCom BW GmbH (ORG-OTG1-RIPE) · DEALLOCATED PASep 27, 2018abuse@netcom-bw.de
└ 217.66.136.0/25128IPv4_Range_for_NT_Systems_over_NetCom_BWunknownASSIGNED PAMar 18, 2019abuse@netcom-bw.de
via DE-ODR-TKG-20001106
└ 217.66.136.144/298IPv4_Range_for_Kraftwerk_Living_Technologies_over_NetCom_BWunknownASSIGNED PAAug 9, 2022abuse@netcom-bw.de
via DE-ODR-TKG-20001106
└ 217.66.137.32/2816Speedtest_Server_at_NetCom_BWunknownASSIGNED PAOct 16, 2025abuse@netcom-bw.de
via DE-ODR-TKG-20001106

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Residential2,032>99%2
Hosting160.78%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2018
Current origin since
Dec 2018 · 7.9 yr
Origin networks
1