Observed topology
AS38880 M21-AS-AP Micron21 Datacentre Pty Ltd
Hosting APNIC Content
Transit
Upstream networks
Networks observed carrying traffic for AS38880: 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 | IPv4 IPv6 | 584 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 472 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 446 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 293 |
| AS2764 | AAPT Limited | Unclassified | IPv4 IPv6 | 211 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 195 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 122 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 116 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 97 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 73 |
Transit
Downstream networks
Networks for which AS38880 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS55359 | Fluccs Australia Australian Cloud Provider | Hosting | IPv4 | 778 |
| AS58940 | Dedicated Servers Australia | Unclassified | IPv4 | 408 |
| AS133104 | Instra Corporation Pty Ltd | Unclassified | IPv4 IPv6 | 254 |
| AS45426 | Web Hosting Oranisation | Unclassified | IPv4 | 180 |
| AS58915 | Arktisma Pty Ltd | Unclassified | IPv4 IPv6 | 157 |
| AS136577 | Siptalk Pty Ltd | Unclassified | IPv4 | 155 |
| AS132533 | Vibe Group Pty Ltd | Unclassified | IPv4 | 16 |
| AS20144 | ICANN | Unclassified | IPv4 IPv6 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS38880 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS55359 | Fluccs Australia Australian Cloud Provider | Hosting | IPv4 | 778 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 711 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 702 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 647 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 470 |
| AS2764 | AAPT Limited | Unclassified | IPv4 IPv6 | 412 |
| AS58940 | Dedicated Servers Australia | Unclassified | IPv4 | 408 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 315 |
| AS133104 | Instra Corporation Pty Ltd | Unclassified | IPv4 IPv6 | 254 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 200 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.