asn.dev

Observed topology

AS264023 AS264023 - SE77E TELECOM EIRELI ME

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264023: 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
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6268
AS6939Hurricane Electric LLCTransitIPv4 IPv6217
AS28329SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv669
AS24482SG.GSHostingIPv4 IPv616
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS35280F5 Networks SARLHostingIPv4 IPv68
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267303CENTRO OESTE PROVEDORUnclassifiedIPv4 IPv661

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS16735ALGAR TELECOM S/AUnclassifiedIPv4 IPv6268
AS6939Hurricane Electric LLCTransitIPv4 IPv6258
AS28329SAMM TECNOLOGIA E TELECOMUNICACOES S.AUnclassifiedIPv4 IPv670
AS267303CENTRO OESTE PROVEDORUnclassifiedIPv4 IPv661
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv615
AS262473SAMISSA TELECOMUnclassifiedIPv613
AS35280F5 Networks SARLHostingIPv4 IPv69
AS52863UPX TECNOLOGIA LTDAUnclassifiedIPv41

Provenance

Where this comes from

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