asn.dev

Observed topology

AS267409 AS267409 - SARTOR INTERNET LTDA

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267409: 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
AS263629ALLREDE TELECOM MT / BRASIL TECPARUnclassifiedIPv4 IPv6404
AS6939Hurricane Electric LLCTransitIPv4 IPv676
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS35280F5 Networks SARLHostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS264158E QUARESMA NETO PROVEDORES EIRELI - MEUnclassifiedIPv460
AS272767IMPACTO NETWORK INTERNET LTDAUnclassifiedIPv414

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS263629ALLREDE TELECOM MT / BRASIL TECPARUnclassifiedIPv4 IPv6497
AS6939Hurricane Electric LLCTransitIPv4 IPv6110
AS53062GGNET TELECOMUNICACOES LTDAUnclassifiedIPv460
AS264158E QUARESMA NETO PROVEDORES EIRELI - MEUnclassifiedIPv460
AS270563INVINET PROVEDOR LTDA - MEUnclassifiedIPv460
AS272767IMPACTO NETWORK INTERNET LTDAUnclassifiedIPv414
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS35280F5 Networks SARLHostingIPv62

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.