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

217.18.138.0/24

1 residential-proxy exit · 30 days

PJSC Rostelecom

Announcement
217.18.128.0/19
RPKI valid
Announced by
AS12389
Type
Business
56% of it
Recent change
New origin Jul 2026
from AS41440 PJSC Rostelecom, after 14.6 years unannounced

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
5
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

71 observations

Proxy providers listing exits

  • EnigmaProxy
  • NovaProxy
  • Proxiware
  • ProxyEmpire
  • VantageProxies

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.18.128.0/198,192RU-RTK-20000919PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 4, 2003abuse@rt.ru
└ 217.18.138.0/25128TOMSKNETTomsktelecom, ISP in Tomsk, Russia and Tomsk regionASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.138.128/2816BOBI-NETHome network of Baboshko Y.AASSIGNED PADec 29, 2001abuse@rt.ru
via RU-RTK-20000919
└ 217.18.138.192 - 217.18.140.31352TOMSKNETTomsktelecom, ISP in Tomsk, Russia and Tomsk regionASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business14456%2
Residential11244%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 217.18.128.0/19

217.18.128.0/19

Routing history

Pattern
Reactivated
First seen
May 2005
Current origin since
Jul 2026 · 4 mo
Origin networks
3
Last change of origin
Jul 2026
Recorded history

History

Handoffs
2