LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

91.185.83.0/24

2 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
RPKI valid
Announced by
AS209024
Type
Hosting
Risk
50 / 100 · Medium
Recently moved
Recent change
New origin Jul 2026
from AS60490 MTS PJSC, after 3.6 years unannounced

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
24
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

26 observations

Proxy providers listing exits

  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • KindProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive

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
91.185.64.0/198,192RU-MTU-20080910MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PASep 10, 2008abuse@mtu.ru
└ 91.185.80.0/204,096CloudMTS-80MTS CloudASSIGNED PADec 3, 2010abuse@mtu.ru
via RU-MTU-20080910

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
Oct 2021
Current origin since
Jul 2026 · 4 mo
Origin networks
2
Last change of origin
Jul 2026
Recorded history

History

Handoffs
1