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

217.77.56.0/21

12 residential-proxy exits · 30 days

Limited Company Svyazservice

Announcement
this exact prefix
RPKI invalid (length)
Announced by
AS42387
Type
Residential

Residential-proxy exits

Proxy exits
12
0.59% of its addresses · 30 days
Spread
6 of 8
/24s with at least one exit
Providers
21
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

294 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.77.61.0/2407
217.77.56.0/2401
217.77.57.0/2401
217.77.58.0/2401
217.77.59.0/2401
217.77.60.0/2401

Proxy providers listing exits

  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • Geonode
  • HideProxy
  • IPFly
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • Oxylabs
  • ProxyGeo
  • PuraRoute
  • Shifter
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.77.48.0/20
since Mar 2007
AS42387Residential163Limited Company Svyazservice

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
217.77.48.0/204,096RU-SSERV-20070213Limited Company Svyazservice (ORG-LCS4-RIPE) · RUALLOCATED PAFeb 13, 2007abuse@sampo.ru
└ 217.77.56.0/24256SSERV-NET-2Svyazservice LTD ISPASSIGNED PAOct 30, 2007abuse@sampo.ru
via RU-SSERV-20070213
└ 217.77.57.0/24256SSERV-NET-3Svyazservice LTD ISPASSIGNED PAFeb 14, 2008abuse@sampo.ru
via RU-SSERV-20070213
└ 217.77.58.0/23512SSERV-NET-4Svyazservice LTD ISPASSIGNED PAJun 17, 2008abuse@sampo.ru
via RU-SSERV-20070213
└ 217.77.60.0/23512SSERV-NET-5Svyazservice LTD ISP broadband usersASSIGNED PADec 15, 2008abuse@sampo.ru
via RU-SSERV-20070213
└ 217.77.62.0/23512SSERV-NET-6Svyazservice LTD ISP broadband usersASSIGNED PAAug 4, 2009abuse@sampo.ru
via RU-SSERV-20070213

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

First seen
Before our records
Origin networks
1