Data as of Nov 16, 2026

89.251.151.0/24

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.39% of its addresses · 30 days
Providers
16
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.9K observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • DataImpulse
  • FloppyData
  • IPFly
  • Novada
  • Proxmint
  • Proxy4U
  • ProxyWing
  • Proxying
  • PuraRoute
  • Q2IP
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.251.144.0/21
since Sep 2010
AS29194Residential21
2 always on
MTS 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
89.251.144.0/204,096RU-MTU-20060911MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PANov 10, 2014abuse@mtu.ru
└ 89.251.150.0/23512INTELSET_OJSC_NET3"MTS" OJSCASSIGNED PAMay 23, 2011abuse@mtu.ru
via RU-MTU-20060911

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2022
Current origin since
Feb 2022 · 4.8 yr
Origin networks
1