Observed topology

AS58793 NIFCLOUD-NET FUJITSU LIMITED

Unclassified ARIN Enterprise

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 5

Upstream graph Who carries AS58793, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS58793 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58793: 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.

AS	Network	Type	Families	Paths seen
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4 IPv6	569
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	147
AS17676	SoftBank Corp.	Mobile	IPv4 IPv6	54
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4 IPv6	15
AS24482	SG.GS	Hosting	IPv4 IPv6	15
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	12

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS2497	Internet Initiative Japan Inc.	Unclassified	IPv4 IPv6	569
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	147
AS17676	SoftBank Corp.	Mobile	IPv4 IPv6	54
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4 IPv6	15
AS24482	SG.GS	Hosting	IPv4 IPv6	15
AS20485	Joint Stock Company TransTeleCom	Unclassified	IPv4	12

Provenance

Where this comes from

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