Data as of Nov 19, 2026

46.20.188.0/24

2 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
12
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

81 observations

Proxy providers listing exits

  • Evomi
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • InfiniteProxies
  • LudaxProxy
  • PROXYFALL
  • PrivateProxy
  • PuraRoute
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.20.176.0/20
since Sep 24, 2026
AS8359Residential178
1 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
46.20.176.0/204,096RU-MTU-20101005MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAOct 5, 2010abuse@mtu.ru
└ 46.20.184.0/212,048LLC-ZHANR-NETCJSC ZHANR LIR Infrastructure (9-th dynamic PPP pool)SUB-ALLOCATED PAMay 19, 2022abuse@mtu.ru
via RU-MTU-20101005
└ 46.20.188.0/24256b2bhub-vladimir-1unknownSUB-ALLOCATED PAMay 19, 2022abuse@mtu.ru
via LLC-ZHANR-NET

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
Reactivated
First seen
Mar 2019
Current origin since
May 2022 · 4.5 yr
Origin networks
2
Last change of origin
May 2022
Recorded history

History

Handoffs
1