asn.dev

Observed topology

AS34624 MEGASPACE-AS

Hosting RIPE Content

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS34624: 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
AS13335Cloudflare, Inc.HostingIPv4130
AS6461Zayo BandwidthTransitIPv4 IPv657
AS9002RETN LimitedUnclassifiedIPv4 IPv640
AS3356Level 3 Parent, LLCTransitIPv4 IPv639
AS13237euNetworks GmbHUnclassifiedIPv435
AS174Cogent Communications, LLCTransitIPv4 IPv634
AS6939Hurricane Electric LLCTransitIPv430
AS2914NTT America, Inc.TransitIPv4 IPv626
AS34549meerfarbig GmbH & Co. KGHostingIPv415
AS3320Deutsche Telekom AGMobileIPv4 IPv611

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215547Megaspace Internet Services GmbHUnclassifiedIPv4 IPv632

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4130
AS6461Zayo BandwidthTransitIPv4 IPv662
AS9002RETN LimitedUnclassifiedIPv4 IPv649
AS174Cogent Communications, LLCTransitIPv4 IPv640
AS3356Level 3 Parent, LLCTransitIPv4 IPv639
AS13237euNetworks GmbHUnclassifiedIPv435
AS2914NTT America, Inc.TransitIPv4 IPv634
AS215547Megaspace Internet Services GmbHUnclassifiedIPv4 IPv632
AS6939Hurricane Electric LLCTransitIPv430
AS29551Aixit GmbHHostingIPv4 IPv615

All 20 adjacent →

Provenance

Where this comes from

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