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

31.13.148.0/22

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
AS16345
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
22
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

28 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
31.13.148.0/2401
31.13.149.0/2401
31.13.151.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • GSocks
  • GonzoProxy
  • HydraProxy
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

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
31.13.144.0/212,048RU-BEE3G-20110419PJSC "Vimpelcom" (ORG-JA8-RIPE) · RUALLOCATED PAApr 19, 2011Internet.abuse@beeline.ru
└ 31.13.148.0/221,024BEE_STATICAPN static.beeline.ruASSIGNED PAJul 22, 2011Internet.abuse@beeline.ru
via RU-BEE3G-20110419

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
Stable
First seen
Aug 2011
Current origin since
Aug 2011 · 15 yr
Origin networks
1