asn.dev

Observed topology

AS199073 IMPLETECHLIMITED-AS-AP - IMPLETECH LIMITED

Unclassified APNIC

Upstreams 8 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 6
Upstream graph Who carries AS199073, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS199073 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS199073: 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.

ASNetworkTypeFamiliesPaths seen
AS138997Eons Data Communications LimitedUnclassifiedIPv4 IPv6146
AS955LSHIY LLCUnclassifiedIPv492
AS53667FranTech SolutionsHostingIPv671
AS6939Hurricane Electric LLCTransitIPv668
AS18041Taiwan Digital Streaming Co.HostingIPv463
AS26042FiberState, LLCHostingIPv4 IPv636
AS24482SG.GSHostingIPv4 IPv63
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv63

Transit

Downstream networks

inferred

Networks for which AS199073 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS199073 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS138997Eons Data Communications LimitedUnclassifiedIPv4 IPv6146
AS955LSHIY LLCUnclassifiedIPv492
AS53667FranTech SolutionsHostingIPv671
AS6939Hurricane Electric LLCTransitIPv668
AS18041Taiwan Digital Streaming Co.HostingIPv463
AS26042FiberState, LLCHostingIPv4 IPv636
AS24482SG.GSHostingIPv4 IPv63
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv63

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.