asn.dev

Observed topology

AS265334 MULTIGLOBAL EIRELI

Unclassified LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS265334: 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
AS267614SIGAON SERVICOS TELECOMUNICACOES EIRELEResidentialIPv4 IPv6283
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6136
AS52873Softdados TelecomunicacoesUnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS267503RCM BRASIL MULTIMIDIA LTDAUnclassifiedIPv4116
AS271373UPVC INTERNETUnclassifiedIPv431

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS267614SIGAON SERVICOS TELECOMUNICACOES EIRELEResidentialIPv4 IPv6286
AS14840BR.Digital TelecomUnclassifiedIPv4 IPv6249
AS267503RCM BRASIL MULTIMIDIA LTDAUnclassifiedIPv4116
AS52873Softdados TelecomunicacoesUnclassifiedIPv436
AS271373UPVC INTERNETUnclassifiedIPv431

Provenance

Where this comes from

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