asn.dev

Observed topology

AS34300 SPACENET-AS Internet-Cosmos LLC

Hosting RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS34300: 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
AS20764CJSC RASCOMUnclassifiedIPv4356
AS1299Arelion Sweden ABTransitIPv473
AS25091IP-Max SAUnclassifiedIPv464
AS28917Fiord Networks, UABUnclassifiedIPv418
AS8595OOO WestCall Ltd.UnclassifiedIPv416
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv48
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS49673Truenetwork LLCUnclassifiedIPv48
AS50384iHome LLCUnclassifiedIPv48

All 13 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS20764CJSC RASCOMUnclassifiedIPv4356
AS1299Arelion Sweden ABTransitIPv473
AS25091IP-Max SAUnclassifiedIPv464
AS28917Fiord Networks, UABUnclassifiedIPv418
AS8595OOO WestCall Ltd.UnclassifiedIPv416
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv48
AS24482SG.GSHostingIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS49673Truenetwork LLCUnclassifiedIPv48
AS50384iHome LLCUnclassifiedIPv48

All 13 adjacent →

Provenance

Where this comes from

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