asn.dev

Observed topology

AS142046 M1033-INFO-AS-TW - 1033 Network Information Co.

Unclassified APNIC

Upstreams 7 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 4
Adjacent (IPv6) 7
Upstream graph Who carries AS142046, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS142046 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142046: 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
AS6939Hurricane Electric LLCTransitIPv668
AS150766CoCoDigit LtdUnclassifiedIPv458
AS205329Kai-Jung ChenUnclassifiedIPv439
AS32595Liberally Network, LLCResidentialIPv422
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv64
AS174Cogent Communications, LLCTransitIPv62
AS24482SG.GSHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215993LIU AN LUNUnclassifiedIPv674
AS1316311033 Network Information LTD.UnclassifiedIPv636
AS199203CHEN ZHI-HANUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6163
AS215993LIU AN LUNUnclassifiedIPv674
AS150766CoCoDigit LtdUnclassifiedIPv458
AS205329Kai-Jung ChenUnclassifiedIPv439
AS1316311033 Network Information LTD.UnclassifiedIPv636
AS32595Liberally Network, LLCResidentialIPv422
AS174Cogent Communications, LLCTransitIPv612
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv67
AS24482SG.GSHostingIPv65
AS199203CHEN ZHI-HANUnclassifiedIPv61

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.