Data as of Nov 13, 2026

89.221.16.0/21

9 residential-proxy exits · 30 days

PJSC MegaFon

Announcement
RPKI valid
Announced by
Type
Mobile

Residential-proxy exits

Proxy exits
9
0.44% of its addresses · 30 days
Always-on exits
2
22% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
38
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.5K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.221.18.0/2411
89.221.22.0/2411
89.221.20.0/2407

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
89.221.21.0/24
since Jul 2017
AS12714MobilePJSC MegaFon

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
89.221.16.0/204,096RU-MEGAFON-20060922PJSC MegaFon (ORG-OM1-RIPE) · RUALLOCATED PASep 22, 2006abuse-mailbox@megafon.ru
└ 89.221.16.0/212,048RU-TI-20151116Net By Net Holding LLCASSIGNED PAJun 6, 2007abuse-mailbox@megafon.ru
via RU-MEGAFON-20060922

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

Who has announced 89.221.16.0/20

89.221.16.0/20

Routing history

Pattern
Stable
First seen
Apr 2014
Current origin since
Dec 2014 · 12 yr
Origin networks
2
Last change of origin
Dec 2014
Recorded history

History

Handoffs
1