Data as of Nov 16, 2026

213.88.71.0/24

6 residential-proxy exits · 30 days

PJSC MegaFon

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
34
selling exits here
Oct 17, 2026 – Nov 14, 2026

Exits seen per day

112 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GhostConnect
  • HASDATA
  • HideProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.88.0.0/17
since Jun 2015
AS12714Mobile2,371
15 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.88.0.0/1732,768RU-MEGAFON-20100427PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PAApr 27, 2010abuse-mailbox@megafon.ru
└ 213.88.56.0 - 213.88.127.25518,432RU-CHEBNET-NETNet By Net Holding LLCASSIGNED PANov 17, 2010abuse-mailbox@megafon.ru
via RU-MEGAFON-20100427

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.88.64.0/20

Routing history

Pattern
Stable
First seen
Jan 2026
Current origin since
Jan 2026 · 9 mo
Origin networks
1