Data as of Nov 21, 2026

213.173.56.0/22

1 residential-proxy exit · 30 days

Nextpertise B.V.

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
3
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

7 observations

Proxy providers listing exits

  • Byteful
  • CliProxy
  • IPFly

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
213.173.56.0/221,024NL-IPV2-20181107Nextpertise B.V. (ORG-IA661-RIPE) · NLALLOCATED PANov 18, 2020abuse@nextpertise.nl
└ 213.173.56.0/24256qdata-1Q Data solutionsASSIGNED PAFeb 7, 2023abuse@nextpertise.nl
via NL-IPV2-20181107
└ 213.173.57.0/24256qdata-1Q Data solutionsASSIGNED PAFeb 7, 2023abuse@nextpertise.nl
via NL-IPV2-20181107
└ 213.173.58.0/24256qdata-1Q Data solutionsASSIGNED PAFeb 7, 2023abuse@nextpertise.nl
via NL-IPV2-20181107
└ 213.173.59.0/24256qdata-1Q Data solutionsASSIGNED PAFeb 7, 2023abuse@nextpertise.nl
via NL-IPV2-20181107

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
Feb 2019
Current origin since
Feb 2019 · 7.8 yr
Origin networks
1