AS721United States Department of Defense (DoD)
As of 26th September 2026, AS721 (United States Department of Defense…), a transit carrier registered in the United States with ARIN, originates 241 IPv4 prefixes covering 73.1M addresses and 2 IPv6 prefixes. By IPv4 address space that makes it the 6th-largest of the 79,480 networks we see originating IPv4, and the 5th-largest of 18,421 in the United States. It is seen behind 1 upstream network, most often AS3356 (Lumen (Level 3)), and in front of 3 downstream networks. None of its announcements have a valid RPKI ROA. 100% of its routes reach at least 90% of full-feed peers, and 1 prefix is also originated by another network.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS721 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS721 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
8
adjacent networks
- Upstreams
- 113%
- Peers
- 450%
- Downstreams
- 338%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS3356Lumen (Level 3) | Peer | 1,045,269 | 145 |
Prefixes
All 243The largest blocks AS721 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 55.0.0.0/8 | 16.8M | 80/81 |
| 214.0.0.0/8 | 16.8M | 80/81 |
| 215.0.0.0/9 | 8.4M | 80/81 |
| 132.0.0.0/10 | 4.2M | 80/81 |
| 131.32.0.0/11 | 2.1M | 80/81 |
| 132.96.0.0/11 | 2.1M | 80/81 |
| 205.64.0.0/11 | 2.1M | 80/81 |
| 132.80.0.0/12 | 1M | 79/81 |
| 132.128.0.0/12 | 1M | 79/81 |
| 138.144.0.0/12 | 1M | 79/81 |
Routing health
How AS721'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
- Valid0.0%0
- Invalid0.0%0
- No ROA100.0%243
Propagation
- Globally propagated90% of full-feed peers or more100.0%243
- Partially propagated40% to 90%0.0%0
- Seen by few peersUnder 40%0.0%0
Prefix sizes
IPv4 — 241 prefixes
- /816.8M addresses0.8%2
- /98.4M addresses0.4%1
- /104.2M addresses0.4%1
- /112.1M addresses1.2%3
- /121M addresses1.2%3
- /13524k addresses3.7%9
- /14262k addresses7.5%18
- /15131k addresses12.9%31
- /1665.5k addresses21.6%52
- /1732.8k addresses2.5%6
- /1816.4k addresses6.2%15
- /198.2k addresses1.7%4
- /204.1k addresses5.0%12
- /212k addresses7.5%18
- /221k addresses2.9%7
- /23512 addresses6.2%15
- /24256 addresses18.3%44
IPv6 — 2 prefixes
- /324.3B × /64100.0%2
Recent changes
Announcements that started or stopped since 27th Aug 2026.
- Announced192.42.41.0/2425th Sept 2026
- Announced139.244.1.0/2423rd Sept 2026
- Announced2608:120::/3223rd Sept 2026
- Withdrawn139.244.1.0/2422nd Sept 2026
- Withdrawn2608:120::/3222nd Sept 2026
- Announced139.244.1.0/2422nd Sept 2026
- Announced139.244.2.0/2422nd Sept 2026
- Announced139.244.4.0/2422nd Sept 2026
- Announced139.244.7.0/2422nd Sept 2026
- Announced199.252.48.0/2222nd Sept 2026
- Withdrawn140.1.0.0/1621st Sept 2026
- Withdrawn192.42.41.0/2421st Sept 2026
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.