Data as of Nov 12, 2026

141.136.124.0/24

1 residential-proxy exit · 30 days

IP Visie Networking B.V.

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
2
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1 observation

Proxy providers listing exits

  • 711Proxy
  • IPFly

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
141.136.120.0/21
since Mar 2012
AS198089Business2IP Visie Networking B.V.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
141.136.120.0/212,048NL-IPVISIE-20110630IP Visie Networking B.V. (ORG-IVNB1-RIPE) · NLALLOCATED PAJun 30, 2011abuse@ipvisie.com
└ 141.136.124.0/298GAVKOBV-NET1-NETunknownASSIGNED PAMar 6, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.16/298ROBIJNSB-NET1-NETunknownASSIGNED PAApr 2, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.24/304HABEMID-NET1-NETunknownASSIGNED PAApr 9, 2018abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.32/298GRAFISCH-NET1-NETunknownASSIGNED PAMay 6, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.48/298SPECIALF-NET1-NETunknownASSIGNED PAJun 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.56/298PIUSXCOL-NET1-NETunknownASSIGNED PAJun 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.64/298MERKSTEC-NET1-NETunknownASSIGNED PAAug 2, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.72/298TREHAZEL-NET1-NETunknownASSIGNED PAAug 2, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.92/304VSATECHN-NET1-NETunknownASSIGNED PAApr 2, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.120/304WARMTEBE-NET1-NETunknownASSIGNED PAJun 27, 2017abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.128/304VINCOTTE-NET1-NETunknownASSIGNED PASep 22, 2017abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.132/304HAASNOOT-NET2-NETunknownASSIGNED PASep 22, 2017abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.136/304EFECTISN-NET1-NETunknownASSIGNED PAApr 2, 2021abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.140/304FMHMEDIC-NET1-NETunknownASSIGNED PAOct 18, 2017abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.168/304KRINKELS-NET1-LNKunknownASSIGNED PAJun 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.172/304KRINKELS-NET1-NETunknownASSIGNED PAJun 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.176/304SPECIALF-NET1-LNKunknownASSIGNED PAJun 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.184/304STICHTIN-NET1-LNKunknownASSIGNED PASep 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.188/304HAZERASE-NET1-NETunknownASSIGNED PAJun 15, 2017abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.192/304DEISSBV-NET1-NETunknownASSIGNED PAJun 15, 2017abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.196/304PIUSXCOL-NET1-LNKunknownASSIGNED PAJun 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.200/304TREHAZEL-NET1-LNKunknownASSIGNED PAJun 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.204/304STICHTIN-NET1-NETunknownASSIGNED PASep 18, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.216/304STICHTIN-NET1-NETunknownASSIGNED PAOct 30, 2018abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.220/304NSSTATIO-NET1-NETunknownASSIGNED PAJun 27, 2017abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.240/304CCOICTDI-NET1-NETunknownASSIGNED PADec 2, 2021abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.244/304OMSSOLUT-NET1-NETunknownASSIGNED PAJul 14, 2013abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.248/304BMEGROEP-NET1-NETunknownASSIGNED PAAug 16, 2018abuse@ipvisie.com
via NL-IPVISIE-20110630
└ 141.136.124.252/304MTCMoerd-NET1-NETMTCMoerd-NET1-NETASSIGNED PANov 17, 2021abuse@ipvisie.com
via NL-IPVISIE-20110630

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

Covering aggregate above, the prefix's own history below

141.136.124.0/22

Routing history

Pattern
Stable
First seen
Sep 2018
Current origin since
Sep 2018 · 8.2 yr
Origin networks
1