Data as of Nov 11, 2026

77.71.55.0/24

9 residential-proxy exits · 30 days

Geodim Ltd.

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
51
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Evomi
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.71.0.0/1732,768BG-BGWAN-20070302Geodim Ltd. (ORG-GL32-RIPE) · BGALLOCATED PAMar 2, 2007support@bgwan.com
└ 77.71.48.0/212,048BG-VLCOM-001BGWAN NetworksASSIGNED PADec 6, 2011support@bgwan.com
via BG-BGWAN-20070302

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 77.71.48.0/21

77.71.48.0/21

Routing history

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

History

Handoffs
1