asn.dev

Observed topology

AS7483 SKYCLOUD-NET Skycloud Computing co., Ltd.

Hosting APNIC Content

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS7483: 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
AS13335Cloudflare, Inc.HostingIPv4325
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6300
AS4229Zenlayer IncHostingIPv4 IPv6179
AS60068Datacamp LimitedHostingIPv4 IPv6167
AS21859Zenlayer IncHostingIPv4 IPv6132
AS59796StormWall s.r.o.UnclassifiedIPv4116
AS17676SoftBank Corp.MobileIPv4 IPv6110
AS2914NTT America, Inc.TransitIPv471
AS1299Arelion Sweden ABTransitIPv4 IPv666
AS174Cogent Communications, LLCTransitIPv4 IPv623

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150288METAGE TECHNOLOGY PTE. LTD.UnclassifiedIPv4195

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv6380
AS13335Cloudflare, Inc.HostingIPv4325
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6300
AS150288METAGE TECHNOLOGY PTE. LTD.UnclassifiedIPv4233
AS4229Zenlayer IncHostingIPv4 IPv6179
AS21859Zenlayer IncHostingIPv4 IPv6132
AS59796StormWall s.r.o.UnclassifiedIPv4116
AS17676SoftBank Corp.MobileIPv4 IPv6113
AS2914NTT America, Inc.TransitIPv471
AS1299Arelion Sweden ABTransitIPv4 IPv666

All 14 adjacent →

Provenance

Where this comes from

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