asn.dev

Observed topology

AS35916 MULTA-ASN1 - MULTACOM CORPORATION

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35916: 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
AS5508124 SHELLSHostingIPv44,176
AS2914NTT America, Inc.TransitIPv4 IPv62,086
AS639565G NETWORK OPERATIONS PTY LTDUnclassifiedIPv4776
AS6939Hurricane Electric LLCTransitIPv4 IPv6699
AS174Cogent Communications, LLCTransitIPv4 IPv6195
AS24482SG.GSHostingIPv4 IPv668
AS7575Australian Academic and Research Network (AARNet)EducationIPv464
AS17639Converge ICT Solutions Inc.UnclassifiedIPv464
AS134176Cloudie LimitedUnclassifiedIPv459
AS7393CYBERCON, INC.HostingIPv458

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9678HostingInside LTDHostingIPv462
AS17561LARUS LimitedUnclassifiedIPv424

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS5508124 SHELLSHostingIPv44,176
AS2914NTT America, Inc.TransitIPv4 IPv62,152
AS639565G NETWORK OPERATIONS PTY LTDUnclassifiedIPv4785
AS6939Hurricane Electric LLCTransitIPv4 IPv6707
AS174Cogent Communications, LLCTransitIPv4 IPv6195
AS24482SG.GSHostingIPv4 IPv669
AS7575Australian Academic and Research Network (AARNet)EducationIPv465
AS17639Converge ICT Solutions Inc.UnclassifiedIPv465
AS9678HostingInside LTDHostingIPv462
AS134176Cloudie LimitedUnclassifiedIPv459

All 12 adjacent →

Provenance

Where this comes from

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