Data as of Nov 14, 2026

31.13.192.0/24

27 residential-proxy exits · 30 days

SKAT POPOVO Ltd. · space held by Neterra Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
27
11% of its addresses · 30 days
Always-on exits
3
11% of its exits
Providers
76
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

4.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

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.192.0/24256BG-NETERRAIP-20110419Neterra Ltd. (ORG-NL38-RIPE) · BGALLOCATED PAAug 27, 2025abuse@neterra.net
└ 31.13.192.0 - 31.13.192.254255NETERRA-SKATOMURTAG-NETIP networks for SKAT-OmurtagASSIGNED PASep 1, 2025abuse@neterra.net
via BG-NETERRAIP-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

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2011
Current origin since
Oct 2013 · 13 yr
Origin networks
2
Last change of origin
Oct 2013
Recorded history

History

Handoffs
1