Data as of Nov 18, 2026

212.121.96.0/19

12 residential-proxy exits · 30 days

Routit BV

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
81% of it

Residential-proxy exits

Proxy exits
12
0.15% of its addresses · 30 days
Spread
11 of 32
/24s with at least one exit
Providers
18
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

565 observations
  • Residential
  • Internet provider

Proxy providers listing exits

  • AnyIP
  • BottingTools
  • Byteful
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • KocerRoxy
  • LemonBright
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy302
  • 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
212.121.96.0/198,192NL-ROUTIT-20090928Routit BV (ORG-RB1-RIPE) · NLALLOCATED PASep 28, 2009abuse@kpn.com
└ 212.121.96.0/24256ROUTIT-FWSMFWSM RoutIT BVASSIGNED PAJul 29, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.97.0/24256ROUTIT-WAP-EunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.98.0/24256ROUTIT-xDSLROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.99.0/24256ROUTIT-WAP-EunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.100.0/24256ROUTIT-EE-FIBERROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.101.0/24256ROUTIT-CUST-LEVIXROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.102.0/24256ROUTIT-WAP-EunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.103.0/24256ROUTIT-WAP-EunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.104.0/24256ROUTIT-EE-FIBERROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.105.0/24256ROUTIT-WAP-EunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.106.0/24256ROUTIT-FWSMFWSM RoutIT BVASSIGNED PAJul 29, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.107.0/24256ROUTIT-FWSMROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.108.0/24256ROUTIT-xDSLROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.109.0/24256ROUTIT-WAP-EunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.110.0/24256ROUTIT-EE-FIBERROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.111.0/24256ROUTIT-WAP-EunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.112.0/24256ROUTIT-FWSMFWSM RoutIT BVASSIGNED PAJul 29, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.113.0/24256ROUTIT-KLIKSAFEunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.114.0/24256ROUTIT-WAP-EunknownASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.115.0/24256ROUTIT-EE-FIBERROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.116.0/24256ROUTIT-xDSLROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.117.0 - 212.121.119.255768CUST-ROUTIT-DHCPROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.120.0/24256ROUTITunknownASSIGNED PAMay 24, 2011abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.121.0/24256ROUTIT-LAB-BBROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.122.0/25128RIA-IASOROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.122.128/25128FWSM-PoolROUTITASSIGNED PAAug 13, 2010abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.123.0/24256FWSM-poolROUTITASSIGNED PANov 23, 2011abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.124.0/23512ROUTIT-KLIKSAFEROUTITASSIGNED PANov 23, 2011abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.126.0/24256ROUTIT-XDSLROUTITASSIGNED PANov 23, 2011abuse@kpn.com
via NL-ROUTIT-20090928
└ 212.121.127.0/24256ROUTIT-EE-FIBERROUTITASSIGNED PANov 23, 2011abuse@kpn.com
via NL-ROUTIT-20090928

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

8,192 addresses
TypeAddressesShareRanges
Internet provider6,65681%6
Residential1,28016%5
Business2563.1%2

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2007
Current origin since
Oct 2009 · 17 yr
Origin networks
2
Last change of origin
Oct 2009
Recorded history

History

Handoffs
1