asn.dev

Observed topology

AS266475 AS266475 - SEM FRONTEIRAS TELECOMUNICACOES LTDA

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS266475: 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
AS4230CLARO S.A.ResidentialIPv4 IPv61,638
AS6939Hurricane Electric LLCTransitIPv4 IPv6315
AS24482SG.GSHostingIPv4 IPv630
AS1031PEER 1031 LLCUnclassifiedIPv412
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv412
AS52468UFINET PANAMA S.A.UnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267432D. S. da CostaUnclassifiedIPv4 IPv6455
AS267997DS TELECOMUnclassifiedIPv4 IPv6445
AS271555SDMNET INFORMATICA LTDA - MEUnclassifiedIPv4 IPv6391
AS274840A. S. DANTASUnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4230CLARO S.A.ResidentialIPv4 IPv62,961
AS267432D. S. da CostaUnclassifiedIPv4 IPv6455
AS267997DS TELECOMUnclassifiedIPv4 IPv6445
AS271555SDMNET INFORMATICA LTDA - MEUnclassifiedIPv4 IPv6391
AS6939Hurricane Electric LLCTransitIPv4 IPv6315
AS274840A. S. DANTASUnclassifiedIPv632
AS24482SG.GSHostingIPv4 IPv630
AS1031PEER 1031 LLCUnclassifiedIPv412
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv412
AS52468UFINET PANAMA S.A.UnclassifiedIPv41

Provenance

Where this comes from

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