LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

85.92.96.0/22

2 residential-proxy exits · 30 days

Netcore services s.r.o.

Announcement
this exact prefix
RPKI valid
Announced by
AS209810
Type
Business

Residential-proxy exits

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

Exits seen per day

52 observations

Proxy providers listing exits

  • BlurPath
  • IPFly
  • RainProxy
  • Shifter

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
85.92.96.0/221,024CZ-NETCORESERVICES-20181008Netcore services s.r.o. (ORG-NSS37-RIPE) · CZALLOCATED PAJan 21, 2022abuse@netcore.services
└ 85.92.96.0/24256CZ-NETCORESERVICES-B2B-customers-IXunknownASSIGNED PAJul 1, 2022abuse@netcore.services
via CZ-NETCORESERVICES-20181008
└ 85.92.97.0/24256CZ-NETCORESERVICES-B2B-customers-XunknownASSIGNED PAJul 1, 2022abuse@netcore.services
via CZ-NETCORESERVICES-20181008
└ 85.92.98.0/24256CZ-NETCORESERVICES-B2B-customers-XIunknownASSIGNED PAJul 1, 2022abuse@netcore.services
via CZ-NETCORESERVICES-20181008
└ 85.92.99.0/24256CZ-NETCORESERVICES-B2B-customers-XIIunknownASSIGNED PAJul 1, 2022abuse@netcore.services
via CZ-NETCORESERVICES-20181008

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Oct 2019
Current origin since
Oct 2019 · 7.1 yr
Origin networks
1