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

5.227.124.0/22

6 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
12
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

49 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.227.125.0/2404
5.227.124.0/2402

Proxy providers listing exits

  • 711Proxy
  • BottingTools
  • EZProxies
  • FlashProxy
  • IPFly
  • IPPeak
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • RoamProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.227.0.0/17
since Jan 2024
AS8359Mobile6,706
820 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
5.227.0.0/1665,536RU-MTU-20120907MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PASep 7, 2012abuse@mtu.ru
└ 5.227.124.0/221,024MTS-IZHEVSK-5MTS PJSC, Izhevsk brunchASSIGNED PAFeb 6, 2018abuse@mtu.ru
via RU-MTU-20120907

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2014
Current origin since
Nov 2014 · 12 yr
Origin networks
1