asn.dev

Observed topology

AS141013 RISE-AS-AP - Responsible Internet Sustainability Effort

Hosting APNIC Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141013: 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
AS63927RISEResidentialIPv4 IPv6224
AS24482SG.GSHostingIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20940Akamai International B.V.HostingIPv4 IPv696
AS63293Facebook, Inc.HostingIPv4 IPv696
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv694
AS55821RADIUS TELECOMS, INC.UnclassifiedIPv4 IPv630
AS141109PT Omni Cloud IndonesiaHostingIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS63927RISEResidentialIPv4 IPv6506
AS20940Akamai International B.V.HostingIPv4 IPv696
AS63293Facebook, Inc.HostingIPv4 IPv696
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv694
AS24482SG.GSHostingIPv4 IPv634
AS55821RADIUS TELECOMS, INC.UnclassifiedIPv4 IPv630
AS17639Converge ICT Solutions Inc.UnclassifiedIPv46
AS141109PT Omni Cloud IndonesiaHostingIPv41

Provenance

Where this comes from

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