Data as of Nov 22, 2026

213.154.160.0/24

3 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
30
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlexyProxies
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.154.160.0/19
since Mar 2020
AS31133Mobile4
1 always on
PJSC MegaFon

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.154.160.0/198,192RU-MEGAFON-20010411PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PASep 25, 2002abuse-mailbox@megafon.ru
└ 213.154.160.0/221,024INAR-VOL-NETInternet ArkhangelskASSIGNED PA—abuse-mailbox@megafon.ru
via RU-MEGAFON-20010411

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

213.154.160.0/21

Routing history

Pattern
Rotating
First seen
Jan 2006
Current origin since
Nov 2023 · 3.0 yr
Origin networks
2
Last change of origin
Nov 2023
Recorded history

History

Handoffs
1