asn.dev

Observed topology

AS267428 LEX TELECOM LTDA ME

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS267428: 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
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6270
AS6939Hurricane Electric LLCTransitIPv4 IPv682
AS24482SG.GSHostingIPv4 IPv67
AS266428R L A World Net LTDAResidentialIPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270669ATTENTO NET TELECOMUnclassifiedIPv4409
AS266453Acesso Net ServicosUnclassifiedIPv4 IPv6213

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS52468UFINET PANAMA S.A.UnclassifiedIPv4 IPv6602
AS270669ATTENTO NET TELECOMUnclassifiedIPv4409
AS266453Acesso Net ServicosUnclassifiedIPv4 IPv6213
AS266428R L A World Net LTDAResidentialIPv4 IPv6210
AS6939Hurricane Electric LLCTransitIPv4 IPv6200
AS266953ITMINDS CONSULTORIA EM TECNOLOGIA DA INFORMACAOUnclassifiedIPv442
AS24482SG.GSHostingIPv4 IPv615
AS35280F5 Networks SARLHostingIPv43

Provenance

Where this comes from

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