asn.dev

Observed topology

AS267621 IFIBER TELECOM

Unclassified LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267621: 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
AS274685HS TELECOMUNICACAO E TECNOLOGIA LTDAUnclassifiedIPv4 IPv6239
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4233
AS267973G.V.R. TELECOMUNICACOES E SERVICOS LTDA - MEUnclassifiedIPv4218
AS1031PEER 1031 LLCUnclassifiedIPv431
AS24482SG.GSHostingIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS262286ALAN MARCELO DA SILVA LTDAResidentialIPv4 IPv623
AS52821Torres e Anselmi LtdaUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS274685HS TELECOMUNICACAO E TECNOLOGIA LTDAUnclassifiedIPv4 IPv6239
AS271253LINK BRASIL TELECOMUNICACOES LTDAUnclassifiedIPv4237
AS267973G.V.R. TELECOMUNICACOES E SERVICOS LTDA - MEUnclassifiedIPv4218
AS1031PEER 1031 LLCUnclassifiedIPv431
AS262286ALAN MARCELO DA SILVA LTDAResidentialIPv4 IPv624
AS6939Hurricane Electric LLCTransitIPv416
AS24482SG.GSHostingIPv4 IPv615
AS10429TELEFONICA BRASIL S.AResidentialIPv47
AS52821Torres e Anselmi LtdaUnclassifiedIPv46

Provenance

Where this comes from

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