asn.dev

Observed topology

AS268518 AS268518 - FRANCISCO L SILVA DE ARAUJO

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268518: 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
AS266353REDE BJNET TELECOMUNICACOES LTDA-MEResidentialIPv4 IPv6185
AS6939Hurricane Electric LLCTransitIPv4 IPv694
AS24482SG.GSHostingIPv4 IPv67
AS35280F5 Networks SARLHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265983F J S LESSA - MEResidentialIPv4 IPv6248
AS22689SERCOMTEL S/A TELECOMUNICACOESUnclassifiedIPv458
AS271315Netfusion Internet LTDAUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS266353REDE BJNET TELECOMUNICACOES LTDA-MEResidentialIPv4 IPv6412
AS265983F J S LESSA - MEResidentialIPv4 IPv6248
AS6939Hurricane Electric LLCTransitIPv4 IPv6166
AS22689SERCOMTEL S/A TELECOMUNICACOESUnclassifiedIPv458
AS24482SG.GSHostingIPv4 IPv613
AS35280F5 Networks SARLHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS271315Netfusion Internet LTDAUnclassifiedIPv41

Provenance

Where this comes from

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