Data as of Nov 18, 2026

212.85.128.0/20

2 residential-proxy exits · 30 days

Neuronnexion SCOP

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
2
0.05% of its addresses · 30 days
Spread
1 of 16
/24s with at least one exit
Providers
6
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

36 observations

Proxy providers listing exits

  • FLEETPROXY
  • KocerRoxy
  • NovaProxy
  • Proxiware
  • 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.85.128.0/204,096FR-NEURONNEXION-981214Neuronnexion SCOP (ORG-NA22-RIPE) · FRALLOCATED PAApr 28, 2020abuse@nnx.com
└ 212.85.128.0/23512NEURONNEXIONNeuronnexion Infrastructure - AmiensASSIGNED PA—abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.130.0/24256NEURONNEXIONNeuronnexion AmiensASSIGNED PAMay 4, 2005abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.131.0 - 212.85.134.2551,024NEURONNEXIONPPP DialUp accessASSIGNED PAMay 4, 2005abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.135.0/24256NEURONNEXIONNeuronnexionASSIGNED PAMay 4, 2005abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.136.0/24256NEURONNEXIONNeuronnexion Infrastructure - CourbevoieASSIGNED PA—abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.137.0 - 212.85.138.255512NEURONNEXION-SERVERHOSTNeuronnexion Infrastructure - AubervilliersASSIGNED PAMar 11, 2005abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.139.0/24256NEURONNEXION-PDCNeuronnexion-62ASSIGNED PAMay 23, 2014abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.140.0/23512FTTH-AMI1FTTH AmiensASSIGNED PAApr 24, 2015abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.142.0/24256FTTH-ABB1FTTH AbbevilleASSIGNED PAApr 24, 2015abuse@nnx.com
via FR-NEURONNEXION-981214
└ 212.85.143.0/24256FTTH-BVS1FTTH BeauvaisASSIGNED PAApr 24, 2015abuse@nnx.com
via FR-NEURONNEXION-981214

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
May 2005
Current origin since
Aug 2016 · 10 yr
Origin networks
1