asn.dev

Observed topology

AS23700 Fastnet-AS-ID - Linknet-Fastnet ASN

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23700: 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
AS7632Linknet-Exchange ASNUnclassifiedIPv4 IPv68,904
AS24482SG.GSHostingIPv4 IPv6147
AS7717OpenIXP ASNUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS54994Meteverse Limited.UnclassifiedIPv4 IPv6143
AS9905Linknet ASNUnclassifiedIPv480
AS139341ACEHostingIPv460
AS142184PT Lintaslink Media TeknologiUnclassifiedIPv459
AS150923PT Sistem Interkoneksi DataResidentialIPv440

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7632Linknet-Exchange ASNUnclassifiedIPv4 IPv69,205
AS24482SG.GSHostingIPv4 IPv6228
AS54994Meteverse Limited.UnclassifiedIPv4 IPv6143
AS9905Linknet ASNUnclassifiedIPv480
AS139341ACEHostingIPv460
AS142184PT Lintaslink Media TeknologiUnclassifiedIPv459
AS150923PT Sistem Interkoneksi DataResidentialIPv440
AS7717OpenIXP ASNUnclassifiedIPv47
AS138077PT Abhinawa Sumberdaya AsiaHostingIPv45

Provenance

Where this comes from

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