asn.dev

Observed topology

AS268551 AS268551 - DMC TELECOM

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS268551: 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 IPv695
AS3356Level 3 Parent, LLCTransitIPv4 IPv675
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv660
AS24482SG.GSHostingIPv4 IPv620
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv620
AS35280F5 Networks SARLHostingIPv4 IPv617

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61784AltaNet Telecom e Inf. LTDA-MEResidentialIPv469
AS267397SKYNET ARUJA TELECOM LTDAResidentialIPv4 IPv654
AS273478Sage NetworksUnclassifiedIPv619

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6127
AS6939Hurricane Electric LLCTransitIPv4 IPv6111
AS61784AltaNet Telecom e Inf. LTDA-MEResidentialIPv469
AS262807Redfox Telecomunicacoes Ltda.UnclassifiedIPv469
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv660
AS267397SKYNET ARUJA TELECOM LTDAResidentialIPv4 IPv654
AS24482SG.GSHostingIPv4 IPv622
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv622
AS273478Sage NetworksUnclassifiedIPv619
AS35280F5 Networks SARLHostingIPv4 IPv618

Provenance

Where this comes from

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