Data as of Nov 20, 2026

217.26.5.128/28

No anonymizer space · no proxy exits in 30 days

PJSC Moscow city telephone network

Announcement
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
6.3% of its addresses · listed by providers
Providers
20
selling exits here

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • Infatica
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • Shifter

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.26.0.0/204,096RU-MGTS-20001016PJSC Moscow city telephone network (ORG-OMCT1-RIPE) · RUALLOCATED PA—abuse@spd-mgts.ru
└ 217.26.5.128/2816LEKHLEB-NETJSC Lyupan, JSC Se Si Bon, JSC Frantsuzskiy khlebASSIGNED PAFeb 27, 2009abuse@spd-mgts.ru
via RU-MGTS-20001016

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.26.0.0/20

217.26.0.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Nov 2019 · 7.0 yr
Origin networks
2
Last change of origin
Nov 2019
Recorded history

History

Handoffs
1