asn.dev

Observed topology

AS30870 TRANS-IX-AS Trans-iX Autonomous System

Hosting RIPE NSP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS30870: 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
AS49127Asimo Networks B.V.HostingIPv4 IPv6910
AS6939Hurricane Electric LLCTransitIPv4 IPv6216
AS20495We Dare B.V.UnclassifiedIPv4145
AS8455atom86 BVHostingIPv4105
AS24482SG.GSHostingIPv4 IPv628
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv628
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv627
AS48185team.blue NVUnclassifiedIPv4 IPv627
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv627
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv627

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS42585Metaregistrar B.V.HostingIPv4 IPv6306
AS205839SIOC B.V.UnclassifiedIPv459

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS49127Asimo Networks B.V.HostingIPv4 IPv61,154
AS42585Metaregistrar B.V.HostingIPv4 IPv6306
AS6939Hurricane Electric LLCTransitIPv4 IPv6256
AS20495We Dare B.V.UnclassifiedIPv4173
AS8455atom86 BVHostingIPv4 IPv6127
AS205839SIOC B.V.UnclassifiedIPv459
AS24482SG.GSHostingIPv4 IPv635
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv635
AS20766Association "Gitoyen"UnclassifiedIPv428
AS34927iFog GmbHHostingIPv428

Provenance

Where this comes from

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