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

77.76.16.0/20

15 residential-proxy exits · 30 days

Netguard LLC

Announcement
this exact prefix
RPKI valid
Announced by
AS39251
Type
Residential

Residential-proxy exits

Proxy exits
15
0.37% of its addresses · 30 days
Always-on exits
2
13% of its exits
Spread
3 of 16
/24s with at least one exit
Providers
55
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
77.76.17.0/2418
77.76.16.0/2415
77.76.18.0/2402

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
77.76.16.0/24
since Sep 2024
AS39251Residential5
1 always on
Netguard LLC

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
77.76.16.0/204,096BG-NETGUARD-20070209Netguard LLC (ORG-NL288-RIPE) · BGALLOCATED PAMay 28, 2024abuse@netguard.bg
└ 77.76.16.0/23512BG-NETGUARD-20070209unknownASSIGNED PASep 25, 2025abuse@netguard.bg
via BG-NETGUARD-20070209
└ 77.76.24.0/212,048BG-NETGUARD-20070209unknownASSIGNED PASep 25, 2025abuse@netguard.bg
via BG-NETGUARD-20070209

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
Rotating
First seen
Jul 2018
Current origin since
May 2024 · 2.5 yr
Origin networks
2
Last change of origin
May 2024
Recorded history

History

Handoffs
1