Data as of Nov 13, 2026

216.77.41.0/24

2 residential-proxy exits · 30 days

WakeMed · space held by AT&T Enterprises, LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
31
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • ColaProxy
  • DataImpulse
  • EZProxies
  • Evomi
  • FlexyProxies
  • Geonode
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LudaxProxy
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • RolaProxy
  • Thordata
  • ThunderProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
216.76.0.0/14AS6389Residential495
4 always on
AT&T Enterprises, 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
216.76.0.0/14262,144BELLSNET-BLK5AT&T Enterprises, LLC (AEL-360) · USDirect AllocationSep 15, 1998abuse@att.net
└ 216.77.41.0/24256BLS-216-77-41-0-24-1005273332WakeMed - RDU (C02508228) · USReassignedMay 27, 2010abuse@att.net
via BELLSNET-BLK5

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Oct 2010 · 16 yr
Origin networks
3
Last change of origin
Oct 2010
Recorded history

History

Handoffs
2