Observed topology
AS139057 ELD-AS-AP - Edgenext Legend Dynasty Pte. Ltd.
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS139057: 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 |
|---|---|---|---|---|
| AS21859 | Zenlayer Inc | Hosting | IPv4 IPv6 | 1,871 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 739 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 693 |
| AS23764 | CTGNet | Unclassified | IPv4 IPv6 | 605 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 418 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 391 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 390 |
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 IPv6 | 335 |
| AS17497 | Liasail Global Hongkong Limited | Unclassified | IPv4 IPv6 | 329 |
| AS58717 | Summit Communications Ltd | Unclassified | IPv4 IPv6 | 304 |
Transit
Downstream networks
Networks for which AS139057 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213736 | Zantan GmbH | Unclassified | IPv4 IPv6 | 1,411 |
| AS149981 | Edgenext Legend Dynasty Pte. Ltd. | Hosting | IPv4 | 462 |
| AS984 | OCTOPUS WEB SOLUTION INC | Hosting | IPv4 | 60 |
| AS62610 | Zenlayer Inc | Unclassified | IPv4 | 60 |
| AS17497 | Liasail Global Hongkong Limited | Unclassified | IPv4 | 7 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS139057 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS21859 | Zenlayer Inc | Hosting | IPv4 IPv6 | 1,972 |
| AS213736 | Zantan GmbH | Unclassified | IPv4 IPv6 | 1,411 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,289 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 786 |
| AS23764 | CTGNet | Unclassified | IPv4 IPv6 | 668 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 629 |
| AS149981 | Edgenext Legend Dynasty Pte. Ltd. | Hosting | IPv4 IPv6 | 495 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 488 |
| AS39386 | Saudi Telecom Company JSC | Unclassified | IPv4 IPv6 | 454 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 441 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.