Data as of Nov 10, 2026

178.67.206.0/24

5 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
2
40% of its exits
Providers
22
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

3.4K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Thordata

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.67.192.0/18
since Sep 2018
AS12389Residential2,756
65 always on
PJSC Rostelecom
178.67.0.0/16
since Sep 2018
AS12389Residential9,537
318 always on
PJSC Rostelecom
178.64.0.0/13
since Oct 2018
AS12389Residential68,006
3,842 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.64.0.0/13524,288RU-RTK-20100105PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 5, 2010abuse@rt.ru
└ 178.67.192.0/204,096RU-AVANGARD-DSLPJSC "Rostelecom" North-West RegionSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-20100105
└ 178.67.206.0/23512TumenunknownSUB-ALLOCATED PAJul 31, 2026abuse@rt.ru
via RU-AVANGARD-DSL

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

178.67.192.0/19

Routing history

Pattern
Stable
First seen
Nov 2014
Current origin since
Apr 2017 · 9.5 yr
Origin networks
2
Last change of origin
Apr 2017
Recorded history

History

Handoffs
1