Data as of Nov 13, 2026

77.220.56.0/22

1 residential-proxy exit · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
3
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

25 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • PuraRoute

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
77.220.32.0/198,192RU-MTU-20070319MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMar 19, 2007abuse@mtu.ru
└ 77.220.56.0/24256TENSORTELECOM-NETWORKClient UplinksASSIGNED PAMay 30, 2017abuse@mtu.ru
via RU-MTU-20070319
└ 77.220.57.0/24256TENSORTELECOM-NETWORKClient UplinksASSIGNED PAMay 30, 2017abuse@mtu.ru
via RU-MTU-20070319
└ 77.220.58.0/23512Eldin-Plant-NetworkEldin Plant Network AllocationASSIGNED PAMay 30, 2017abuse@mtu.ru
via RU-MTU-20070319

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2021
Current origin since
Jan 2021 · 5.8 yr
Origin networks
1