Observed topology
AS44324 MOEDOVE-AS MoeDove LLC
Residential RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS44324: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 297 |
| AS34927 | iFog GmbH | Hosting | IPv6 | 136 |
| AS140227 | Hong Kong Communications International Co., Limited | Unclassified | IPv4 IPv6 | 136 |
| AS18423 | RAID Networks Co., Ltd. | Hosting | IPv4 IPv6 | 117 |
| AS53667 | FranTech Solutions | Hosting | IPv6 | 67 |
| AS207841 | Inferno Communications Ltd | Unclassified | IPv6 | 58 |
| AS8849 | Melbikomas UAB | Hosting | IPv6 | 55 |
| AS7720 | Skywolf Technology LLC | Unclassified | IPv6 | 48 |
| AS206216 | Advin Services LLC | Hosting | IPv6 | 42 |
| AS216211 | CYBERVERSE LLC | Hosting | IPv6 | 41 |
Transit
Downstream networks
Networks for which AS44324 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS218643 | MENGMENG NETWORK LLC | Unclassified | IPv6 | 868 |
| AS212532 | XIAO YANG WEN RUI | Unclassified | IPv4 IPv6 | 538 |
| AS139317 | Ningbo Dahuamao Information Technology Co Ltd | Education | IPv6 | 490 |
| AS208223 | SHU-HAO TUNG | Unclassified | IPv4 IPv6 | 275 |
| AS53808 | MoeDove | Unclassified | IPv4 IPv6 | 245 |
| AS13696 | NetFuture Technology LLC | Unclassified | IPv6 | 211 |
| AS202939 | Chimon Technology Ltd | Residential | IPv4 IPv6 | 210 |
| AS203314 | HATS NETWORK INC. | Residential | IPv6 | 204 |
| AS214955 | Weikang Zeng | Unclassified | IPv6 | 192 |
| AS215786 | Peng Wang | Unclassified | IPv4 IPv6 | 189 |
Adjacency
Adjacent networks
Every AS seen directly next to AS44324 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS140227 | Hong Kong Communications International Co., Limited | Unclassified | IPv4 IPv6 | 5,309 |
| AS216211 | CYBERVERSE LLC | Hosting | IPv4 IPv6 | 1,232 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,106 |
| AS218643 | MENGMENG NETWORK LLC | Unclassified | IPv6 | 868 |
| AS214454 | PoloNetwork Limited | Unclassified | IPv6 | 771 |
| AS9515 | Compute Global Limited | Unclassified | IPv4 IPv6 | 595 |
| AS18423 | RAID Networks Co., Ltd. | Hosting | IPv4 IPv6 | 544 |
| AS212532 | XIAO YANG WEN RUI | Unclassified | IPv4 IPv6 | 538 |
| AS139317 | Ningbo Dahuamao Information Technology Co Ltd | Education | IPv6 | 532 |
| AS198304 | MoeDove | Residential | IPv4 IPv6 | 357 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-03 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.45M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.