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

85.158.48.0/22

1 residential-proxy exit · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
AS30881
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
2
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

11 observations

Proxy providers listing exits

  • IPFly
  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.158.48.0/21
since May 2005
AS30881Residential4MTS PJSC

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
85.158.48.0/212,048RU-MTU-20041214MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 14, 2004abuse@mtu.ru
└ 85.158.48.0/23512TENSORTELECOM-NETWORKTensorTelecomASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20041214
└ 85.158.50.0/24256TENSORTELECOM-NETWORKClient UplinksASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20041214
└ 85.158.51.0/24256TENSORTELECOM-NETWORKTensorTelecom VPDN poolASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20041214

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 historyWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 2019
Current origin since
Oct 2019 · 7.0 yr
Origin networks
1