asn.dev

Observed topology

AS6424 EDGOO EDGOO NETWORKS UNIPESSOAL LDA

Hosting RIPE

Upstreams 42 carry this network
Downstreams 83 this network carries
Adjacent (IPv4) 124
Adjacent (IPv6) 51
Upstream graph Who carries AS6424, and who carries them, drawn as a map up to the transit-free core. 20 exchanges Where AS6424 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 42

Networks observed carrying traffic for AS6424: 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
AS6461Zayo BandwidthTransitIPv4 IPv6474
AS6939Hurricane Electric LLCTransitIPv4 IPv6395
AS2914NTT America, Inc.TransitIPv4 IPv6363
AS1299Arelion Sweden ABTransitIPv4 IPv6327
AS174Cogent Communications, LLCTransitIPv4 IPv6226
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6102
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv668
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv640
AS24482SG.GSHostingIPv4 IPv632
AS141193EDGOO NETWORKS, UNIPESSOAL LDAUnclassifiedIPv632

All 42 upstreams →

Transit

Downstream networks

All 83

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

ASNetworkTypeFamiliesPaths seen
AS203020HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv677,443
AS207990HostRoyale Technologies Pvt LtdHostingIPv4 IPv654,720
AS209043IPRoyal Services FZE LLCUnclassifiedIPv46,543
AS16509Amazon.com, Inc.HostingIPv42,816
AS133499HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv62,512
AS13335Cloudflare, Inc.HostingIPv41,744
AS174Cogent Communications, LLCTransitIPv41,733
AS2914NTT America, Inc.TransitIPv41,631
AS39486HostRoyale Technologies Pvt LtdHostingIPv41,236
AS37645Sociedade de Investimento e Participacoes S.A - Finstar - Sociedade de Investimento e Participacoes S.AResidentialIPv4 IPv61,018

All 83 downstreams →

Adjacency

Adjacent networks

All 134

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

ASNetworkTypeFamiliesPaths seen
AS53356Free Range Cloud Hosting Inc.HostingIPv4 IPv6202,103
AS6461Zayo BandwidthTransitIPv4 IPv6116,926
AS1299Arelion Sweden ABTransitIPv4 IPv691,616
AS2914NTT America, Inc.TransitIPv4 IPv686,913
AS203020HostRoyale Technologies Pvt LtdUnclassifiedIPv4 IPv677,802
AS207990HostRoyale Technologies Pvt LtdHostingIPv4 IPv654,720
AS174Cogent Communications, LLCTransitIPv4 IPv630,519
AS47787EDGOO NETWORKS UNIPESSOAL LDAUnclassifiedIPv4 IPv621,773
AS6939Hurricane Electric LLCTransitIPv4 IPv613,445
AS44592SkyLink Data Center BVHostingIPv4 IPv67,834

All 134 adjacent →

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.