Data as of Nov 16, 2026

85.14.14.0/23

1 residential-proxy exit · 30 days

Evolink EAD

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

Residential-proxy exits

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

Exits seen per day

30 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYWING_BASIC
  • Proxyma
  • RainProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.14.0.0/1816,384BG-EVOLINK-20050406Evolink EAD (ORG-NAL1-RIPE) · BGALLOCATED PAApr 6, 2005abuse@evolink.com
└ 85.14.14.0/24256PLD-EVOLINKPlovdiv ClientsASSIGNED PAAug 30, 2007abuse@evolink.com
via BG-EVOLINK-20050406
└ 85.14.15.0/24256PLD-EVOLINKPlovdiv ClientsASSIGNED PAAug 3, 2006abuse@evolink.com
via BG-EVOLINK-20050406

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 85.14.0.0/18

85.14.0.0/18

Routing history

Pattern
Stable
First seen
Sep 2005
Current origin since
Sep 2005 · 21 yr
Origin networks
1