AS401322NetO Corp
As of 26th September 2026, AS401322 (NetO Corp), a network registered in the United States with ARIN, originates 28 IPv4 prefixes covering 7.4k addresses and 1 IPv6 prefix. By IPv4 address space that makes it the 12,885th-largest of the 79,516 networks we see originating IPv4, and the 3,764th-largest of 18,424 in the United States. It is seen behind 20 upstream networks, most often AS4229 (Zenlayer Inc) and AS174 (Cogent Communications, LLC), and in front of 6 downstream networks. 83% of its announcements have a valid RPKI ROA, and none are RPKI-invalid. 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 AS401322 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS401322 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
77
adjacent networks
- Upstreams
- 2026%
- Peers
- 5166%
- Downstreams
- 68%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS4229Zenlayer Inc | Peer | 4,803 | 81 | |
| AS174Cogent Communications, LLC | Peer | 1,891 | 80 | |
| AS21859Zenlayer Inc | Peer | 832 | 41 | |
| AS3257GTT Communications Inc. | Peer | 182 | 81 | |
| AS154324AltusCloud Pte. Ltd. | Peer | 63 | 63 | |
| AS6939Hurricane Electric LLC | Peer | 20 | 4 | |
| AS38880Micron21 Datacentre Pty Ltd | Peer | 10 | 2 | |
| AS16552Tiggee LLC | Peer | 5 | 1 | |
| AS151326DCConnect Communication Pte. Ltd. | Peer | 5 | 1 | |
| AS215859Hetzner Cloud - Singapore | Peer | 5 | 1 |
Prefixes
All 29The largest blocks AS401322 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 206.109.66.0/23 | 512 | 81/81 |
| 37.230.53.0/24 | 256 | 81/81 |
| 38.134.104.0/24 | 256 | 81/81 |
| 38.134.105.0/24 | 256 | 81/81 |
| 66.17.143.0/24 | 256 | 78/81 |
| 66.93.5.0/24 | 256 | 80/81 |
| 66.253.70.0/24 | 256 | 80/81 |
| 66.253.84.0/24 | 256 | 80/81 |
| 66.253.86.0/24 | 256 | 80/81 |
| 77.107.82.0/24 | 256 | 80/81 |
Routing health
How AS401322'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
- Valid82.8%24
- Invalid0.0%0
- No ROA17.2%5
Propagation
- Globally propagated90% of full-feed peers or more100.0%29
- Partially propagated40% to 90%0.0%0
- Seen by few peersUnder 40%0.0%0
Prefix sizes
IPv4 — 28 prefixes
IPv6 — 1 prefixes
- /4865.5k × /64100.0%1
Recent changes
Announcements that started or stopped since 28th Aug 2026.
- Withdrawn109.176.134.0/2421st Sept 2026
- Withdrawn147.90.33.0/2421st Sept 2026
- Withdrawn178.93.76.0/2421st Sept 2026
- Withdrawn38.123.174.0/2421st Sept 2026
- Withdrawn66.117.159.0/2421st Sept 2026
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.