asn.dev

Observed topology

AS267513 AS267513 - Seanet Telecom Carazinho Eireli

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267513: 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
AS267469W8 Telecom Ltda - MEUnclassifiedIPv4818
AS28283Adylnet TelecomResidentialIPv4 IPv6148
AS6939Hurricane Electric LLCTransitIPv4 IPv664
AS24482SG.GSHostingIPv4 IPv619
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS273521MULTISERVICE COMUNICACAO E SERVICOS LTDAUnclassifiedIPv463

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267469W8 Telecom Ltda - MEUnclassifiedIPv4818
AS28283Adylnet TelecomResidentialIPv4 IPv6211
AS6939Hurricane Electric LLCTransitIPv4 IPv664
AS273521MULTISERVICE COMUNICACAO E SERVICOS LTDAUnclassifiedIPv463
AS24482SG.GSHostingIPv4 IPv619
AS35280F5 Networks SARLHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44

Provenance

Where this comes from

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