asn.dev

Observed topology

AS267549 NetCOMM FIBRA

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267549: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv685
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv681
AS21574Century Telecom LtdaUnclassifiedIPv4 IPv636
AS24482SG.GSHostingIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS35280F5 Networks SARLHostingIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS28133Provedor Eloinet LtdaResidentialIPv4406
AS262520Prefeitura Municipal de AlfenasUnclassifiedIPv4300
AS269432LINK3 TELECOMUnclassifiedIPv4120
AS273321AGRO TELECOMUnclassifiedIPv4 IPv694

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6891
AS28133Provedor Eloinet LtdaResidentialIPv4406
AS262520Prefeitura Municipal de AlfenasUnclassifiedIPv4300
AS6939Hurricane Electric LLCTransitIPv4 IPv6181
AS269432LINK3 TELECOMUnclassifiedIPv4120
AS273321AGRO TELECOMUnclassifiedIPv4 IPv694
AS21574Century Telecom LtdaUnclassifiedIPv4 IPv636
AS24482SG.GSHostingIPv4 IPv616
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS35280F5 Networks SARLHostingIPv44

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-19 10: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.