Observed topology
AS134176 CLOUDIE-AS-AP - Cloudie Limited
Unclassified Spamhaus ASN-DROP APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS134176: 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 |
|---|---|---|---|---|
| AS38047 | Taiwan Telecom | Hosting | IPv4 | 814 |
| AS60068 | Datacamp Limited | Hosting | IPv4 | 464 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 75 |
| AS40065 | CNSERVERS LLC | Hosting | IPv4 | 26 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 8 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 6 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 5 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 4 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 4 |
| AS52025 | ParadoxNetworks Limited | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS134176 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS134176 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 1,194 |
| AS38047 | Taiwan Telecom | Hosting | IPv4 | 873 |
| AS976 | CoreNET Inc. | Residential | IPv4 IPv6 | 418 |
| AS13875 | MxFiber LLC | Unclassified | IPv4 | 397 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 204 |
| AS35916 | MULTACOM CORPORATION | Hosting | IPv4 | 59 |
| AS53616 | ASYMPTOTE NETWORK, LLC | Unclassified | IPv4 | 58 |
| AS40065 | CNSERVERS LLC | Hosting | IPv4 | 26 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 12 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 8 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.