Data as of Nov 20, 2026

5.144.99.0/24

9 residential-proxy exits · 30 days

MTS PJSC

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
41
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

6.0K observations

Proxy providers listing exits

  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GEEKPROXY_TURBO
  • Geonode
  • GhostConnect
  • HPROXY
  • HideProxy
  • IP2WORLD
  • IPFly
  • IPPeak
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYSAVER
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • VantageProxies
  • ZENPROXY_LITE

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.144.96.0/198,192RU-MTU-20120711MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJul 11, 2012abuse@mtu.ru
└ 5.144.96.0/212,048MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20120711

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 5.144.96.0/19

5.144.96.0/19

Routing history

Pattern
Stable
First seen
Feb 2014
Current origin since
Feb 2014 · 13 yr
Origin networks
1