Data as of Nov 14, 2026

212.86.176.0/22

1 residential-proxy exit · 30 days

NetCom BW GmbH

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

Residential-proxy exits

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

Exits seen per day

9 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • Novada
  • PuraRoute

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
212.86.176.0/221,024DE-ODR-TKG-990719NetCom BW GmbH (ORG-OTG1-RIPE) · DEALLOCATED PAOct 11, 2016abuse@netcom-bw.de
└ 212.86.176.0/23512NeckarCom1Lk Sigmaringen Ravensburg Vlan 814ASSIGNED PADec 20, 2013abuse@netcom-bw.de
via DE-ODR-TKG-990719
└ 212.86.178.0/23512NeckarCom1Lk Sigmaringen Ravensburg Vlan 814ASSIGNED PADec 20, 2013abuse@netcom-bw.de
via DE-ODR-TKG-990719

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
Jun 2013
Current origin since
Jun 2013 · 13 yr
Origin networks
1