Data as of Nov 12, 2026

80.255.176.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

0.10% of its addresses · 30 days

Spread

1 of 4

/24s with at least one exit

Providers

selling exits here

Oct 13, 2026 – Nov 11, 2026

95 observations

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
80.255.176.0/20	4,096	RU-MTU-20051216	MTS PJSC (ORG-ZM1-RIPE) · RU	ALLOCATED PA	Dec 16, 2005	abuse@mtu.ru
└ 80.255.176.0/24	256	TENSORTELECOM-NETWORK	PPPoE and PPTP clients	ASSIGNED PA	Jun 1, 2017	abuse@mtu.ru via RU-MTU-20051216
└ 80.255.177.0 - 80.255.178.255	512	TENSORTELECOM-NETWORK	PPPoE and PPTP clients	ASSIGNED PA	Jun 1, 2017	abuse@mtu.ru via RU-MTU-20051216
└ 80.255.179.0/24	256	TENSORTELECOM-NETWORK	Client Uplinks	ASSIGNED PA	Jun 1, 2017	abuse@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.

Routing timeline

Summary