Data as of Nov 16, 2026

217.18.134.0/24

2 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business
Recent change
New origin Jul 2026
from AS41440 PJSC Rostelecom, after 14.6 years unannounced

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
4
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

12 observations

Proxy providers listing exits

  • BottingTools
  • CliProxy
  • IPFly
  • PuraRoute

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.134.0/2732VASYUGAN-SERVISIZZAO Vasyugan-ServisizASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.32/2816TN-NVKOAO "Tomskneft" VNKASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.48/2816STRJ-SCScool in StrezhevoyASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.64/2816TOMSKNETTomsktelecom, ISP in Tomsk, Russia and Tomsk regionASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.80/298SOC-SEVInsurance CompanyASSIGNED PAFeb 8, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.88/298TOMSKNETTomsktelecom, ISP in Tomsk, Russia and Tomsk regionASSIGNED PAFeb 8, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.96/2816ICAF-KARGPublic network in KargasokASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.112/2816TOMSKNETTomsktelecom, ISP in Tomsk, Russia and Tomsk regionASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.128/2816STRJ-AVIAZAO "StrezhAvia"ASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.144/2816TOMSKNETTomsktelecom, ISP in Tomsk, Russia and Tomsk regionASSIGNED PAFeb 5, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.160/2732TOMSKNIPINEFTJSC "TomskNIPIneft VNC"ASSIGNED PADec 18, 2001abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.192/2732NAKHALKAHome network with webservers and remote accessASSIGNED PAFeb 1, 2002abuse@rt.ru
via RU-RTK-20000919
└ 217.18.134.224 - 217.18.135.3164TOMSKNETTomsktelecom, 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.

Network & registry

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