asn.dev

Observed topology

AS270358 AS270358 - FUSION TELECOM

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS270358: 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
AS52872Voafibra ComunicacaoUnclassifiedIPv4 IPv6431
AS6939Hurricane Electric LLCTransitIPv631
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv62
AS35280F5 Networks SARLHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270316NET NOVO TEMPOUnclassifiedIPv4 IPv6455
AS269304BAHIAWEB TECNOLOGIA LTDAUnclassifiedIPv4 IPv6124
AS270444ZBL TelecomUnclassifiedIPv4 IPv666
AS264403CMTECH Com.e Serv.de Informatica LtdaUnclassifiedIPv429
AS264863New Help Telecomunicacoes Ltda-MeUnclassifiedIPv418

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS52872Voafibra ComunicacaoUnclassifiedIPv4 IPv61,186
AS270316NET NOVO TEMPOUnclassifiedIPv4 IPv6499
AS269304BAHIAWEB TECNOLOGIA LTDAUnclassifiedIPv4 IPv6124
AS270444ZBL TelecomUnclassifiedIPv4 IPv666
AS6939Hurricane Electric LLCTransitIPv663
AS269719GN TELECOMUnclassifiedIPv630
AS264403CMTECH Com.e Serv.de Informatica LtdaUnclassifiedIPv429
AS264863New Help Telecomunicacoes Ltda-MeUnclassifiedIPv418
AS268199Rios NetworkUnclassifiedIPv614
AS52554S. A. da Silva JuniorUnclassifiedIPv612

All 13 adjacent →

Provenance

Where this comes from

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