asn.dev

Observed topology

AS141389 GOIP-AS-AP - GOIP Telecom (Asia Pacific) Pte. Ltd.

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141389: 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
AS4229Zenlayer IncHostingIPv4 IPv6223
AS45904Banglalion Communications LtdUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv4 IPv655
AS174Cogent Communications, LLCTransitIPv425
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv66
AS38001NewMedia Express Pte LtdHostingIPv4 IPv66
AS61292Blix Group ASUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS142631Metro LightspeedResidentialIPv439

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4229Zenlayer IncHostingIPv4 IPv6232
AS45904Banglalion Communications LtdUnclassifiedIPv460
AS174Cogent Communications, LLCTransitIPv455
AS6939Hurricane Electric LLCTransitIPv4 IPv655
AS142631Metro LightspeedResidentialIPv439
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv66
AS38001NewMedia Express Pte LtdHostingIPv4 IPv66
AS61292Blix Group ASUnclassifiedIPv61

Provenance

Where this comes from

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