Data as of Nov 14, 2026

185.43.20.0/22

5 residential-proxy exits · 30 days

X2com BV

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
13
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.43.22.0/2413
185.43.21.0/2402

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • EnigmaProxy
  • FLEETPROXY
  • FloppyData
  • NovaProxy
  • PacketStream
  • PrivateByte
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • RainProxy
  • 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
185.43.20.0/221,024NL-X2COM-20131216X2com BV (ORG-XB7-RIPE) · NLALLOCATED PADec 16, 2013abuse@x2com.nl
└ 185.43.20.0/23512X2COM-INFRA-CUSTOMERS-FIBERunknownASSIGNED PANov 28, 2016abuse@x2com.nl
via NL-X2COM-20131216
└ 185.43.22.0/24256X2COM-BROADBAND-IP-RESERVEDunknownASSIGNED PAJun 26, 2017abuse@x2com.nl
via NL-X2COM-20131216
└ 185.43.23.0/24256X2COM-BROADBAND-IP-RESERVEDunknownASSIGNED PAJun 26, 2017abuse@x2com.nl
via NL-X2COM-20131216

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
Jan 2014
Current origin since
Sep 2017 · 9.1 yr
Origin networks
2
Last change of origin
Sep 2017
Recorded history

History

Handoffs
2