asn.dev

Observed topology

AS267507 SRX TECNOLOGIA DA INFORMACAO LTDA

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267507: 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
AS13786Seabras 1 USA, LLCUnclassifiedIPv4448
AS28283Adylnet TelecomResidentialIPv4 IPv6376
AS266220RFS Tecnologia LTDAUnclassifiedIPv4 IPv692

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267598W-COM InternetUnclassifiedIPv4189
AS267113CLICKCONNECT SOLUCOES EM INTERNET E TECNOLOGIAResidentialIPv4 IPv638
AS266220RFS Tecnologia LTDAUnclassifiedIPv67
AS266082PowerServ InternetResidentialIPv63

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS13786Seabras 1 USA, LLCUnclassifiedIPv4 IPv6602
AS28283Adylnet TelecomResidentialIPv4 IPv6459
AS267598W-COM InternetUnclassifiedIPv4189
AS266220RFS Tecnologia LTDAUnclassifiedIPv4 IPv6144
AS267113CLICKCONNECT SOLUCOES EM INTERNET E TECNOLOGIAResidentialIPv4 IPv679
AS266082PowerServ InternetResidentialIPv63

Provenance

Where this comes from

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