Data as of Nov 17, 2026

80.255.184.0/21

3 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
3
0.15% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
8
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

52 observations

Proxy providers listing exits

  • BottingTools
  • DataImpulse
  • IPFly
  • Infatica
  • KindProxy
  • PuraRoute
  • RainProxy
  • RapidProxy

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
80.255.176.0/204,096RU-MTU-20051216MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 16, 2005abuse@mtu.ru
└ 80.255.184.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20051216
└ 80.255.185.0/24256TENSORTELECOM-NETWORKHosting serversASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20051216
└ 80.255.186.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20051216
└ 80.255.187.0/24256TENSORTELECOM-NETWORKClient UplinksASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20051216
└ 80.255.188.0/23512TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20051216
└ 80.255.190.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20051216
└ 80.255.191.0/24256TENSORTELECOM-NETWORKClient UplinksASSIGNED PAJun 1, 2017abuse@mtu.ru
via RU-MTU-20051216

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
Oct 2019
Current origin since
Oct 2019 · 7.1 yr
Origin networks
1