asn.dev

Observed topology

AS264014 AS264014 - Led Internet Eireli

Residential LACNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS264014: 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
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv689
AS6939Hurricane Electric LLCTransitIPv63
AS52468UFINET PANAMA S.A.UnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS265131GP4 SERVICOS E TECNOLOGIA LTDAUnclassifiedIPv4 IPv6213
AS263508SIMNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv692
AS52549NET PREMIUM LTDA - MEUnclassifiedIPv460
AS265359gotcha net internet providerUnclassifiedIPv460
AS271413E O L CASTRO TELECOMUNICACOES EIRELIUnclassifiedIPv460
AS271418freynet telecomUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267613ELETRONET S.A.UnclassifiedIPv4 IPv6535
AS265131GP4 SERVICOS E TECNOLOGIA LTDAUnclassifiedIPv4 IPv6213
AS52468UFINET PANAMA S.A.UnclassifiedIPv4100
AS263508SIMNET TELECOMUNICACOES LTDAUnclassifiedIPv4 IPv692
AS52549NET PREMIUM LTDA - MEUnclassifiedIPv460
AS265359gotcha net internet providerUnclassifiedIPv460
AS271413E O L CASTRO TELECOMUNICACOES EIRELIUnclassifiedIPv460
AS271418freynet telecomUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv64

Provenance

Where this comes from

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