subnet.im

AS6621Hughes Network Systems, LLC

United StatesRegistryARINTypeEyeball

As of 11th November 2026, AS6621 (Hughes Network Systems, LLC), an access network registered in the United States with ARIN, originates 371 IPv4 prefixes covering 575k addresses and 242 IPv6 prefixes. By IPv4 address space that makes it the 660th-largest of the 80,743 networks we see originating IPv4, and the 158th-largest of 18,754 in the United States. It is seen behind 21 upstream networks, most often AS174 (Cogent Communications, LLC) and AS6461 (Zayo Bandwidth), and in front of 6 downstream networks. Over 99% of its announcements have a valid RPKI ROA, and none are RPKI-invalid. Over 99% of its routes reach at least 90% of full-feed peers, and 3 prefixes are also originated by another network.

At a glance

IPv4 prefixes

371

IPv6 prefixes

242

IPv4 addresses

575k

IPv6 /64s

2.5B

Upstream graph

The networks AS6621 is seen behind, one and two hops out, drawn from real AS paths.

AS6621Toward the internet core
Upstream graph for AS6621: 10 neighbouring networks observed beyond it across 2 levels. The same networks are listed in the tables below.AS6621Hughes Network Sy…This networkAS174Cogent Communicat…AS3356Lumen (Level 3)AS6461Zayo BandwidthAS7018AT&T Enterprises,…AS13765Nedelco Inc.AS151326DCConnect Communi…AS3549Lumen (fka. Globa…AS1299Arelion (fka. Tel…AS2914NTT America, Inc.AS32590Valve Corporation

Networks observed one and two hops upstream of AS6621 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.

Neighbouring networks

71

adjacent networks

Upstreams
2130%
Peers
4462%
Downstreams
68%

Networks carrying this one's traffic toward the rest of the internet.

Upstreams of AS6621
NetworkCountryRelationshipPathsVantage pts
AS174Cogent Communications, LLCUSPeer18,446133
AS6461Zayo BandwidthUSPeer17,034138
AS3356Lumen (Level 3)USPeer8,774138
AS13765Nedelco Inc.USPeer5,341138
AS7018AT&T Enterprises, LLCUSPeer1,43393
AS32098Flō Networks (Transtelco Inc.)USPeer1,218139
AS6939Hurricane Electric LLCUSPeer75415
AS8057Vision Net, Inc.USPeer68750
AS3549Lumen (fka. Global Crossing)USPeer37988
AS13999Mega Cable, S.A. de C.V.MXPeer31982

Prefixes

All 613

The largest blocks AS6621 originates, widest first.

Largest prefixes originated by AS6621
PrefixAddressesVisibility
66.82.0.0/198.2k76/76
66.82.32.0/198.2k76/76
66.82.64.0/198.2k76/76
66.82.160.0/198.2k76/76
66.82.192.0/198.2k76/76
67.45.160.0/198.2k76/76
67.46.192.0/198.2k76/76
67.47.32.0/198.2k76/76
67.142.0.0/198.2k76/76
67.142.160.0/198.2k76/76

Routing health

How AS6621's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.

RPKI origin validation

  • Valid99.7%611
  • Invalid0.0%0
  • No ROA0.3%2

Propagation

  • Globally propagated90% of full-feed peers or more99.5%610
  • Partially propagated40% to 90%0.2%1
  • Seen by few peersUnder 40%0.3%2

Prefix sizes

IPv4 — 371 prefixes

IPv6 — 242 prefixes

  • /37134M × /643.3%8
  • /3933.6M × /644.5%11
  • /4016.8M × /6421.9%53
  • /441M × /6463.6%154
  • /46262k × /640.4%1
  • /47131k × /640.4%1
  • /4865.5k × /645.8%14

Recent changes

Announcements that started or stopped since 12th Oct 2026.

  • Announced2001:5b0:8200::/3923rd Oct 2026
  • Withdrawn2001:5b0:8200::/4423rd Oct 2026
  • Withdrawn2001:5b0:8210::/4423rd Oct 2026
  • Withdrawn2001:5b0:8220::/4423rd Oct 2026
  • Withdrawn2001:5b0:8230::/4423rd Oct 2026
  • Withdrawn2001:5b0:8240::/4423rd Oct 2026
  • Announced2001:5b0:b200::/3922nd Oct 2026
  • Withdrawn2001:5b0:b200::/4422nd Oct 2026
  • Withdrawn2001:5b0:b210::/4422nd Oct 2026
  • Withdrawn2001:5b0:b220::/4422nd Oct 2026
  • Withdrawn2001:5b0:b230::/4422nd Oct 2026
  • Withdrawn2001:5b0:b240::/4422nd Oct 2026

2 announced and 27 withdrawn in all; the most recent are shown.

Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.