asn.dev

Observed topology

AS30962 COMTRANCE-AS comtrance service GmbH

Hosting APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30962: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6445
AS3356Level 3 Parent, LLCTransitIPv4 IPv6403
AS41692OpenCarrier eGUnclassifiedIPv4 IPv6327
AS3320Deutsche Telekom AGMobileIPv4 IPv6133

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41108comtrance service GmbHHostingIPv4 IPv6922
AS44335nocyo GmbHUnclassifiedIPv4 IPv6268
AS34568ConnectingBytes GmbHHostingIPv4 IPv679
AS196922Hofmeir Media GmbHUnclassifiedIPv422

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS41108comtrance service GmbHHostingIPv4 IPv61,466
AS1299Arelion Sweden ABTransitIPv4 IPv61,045
AS3356Level 3 Parent, LLCTransitIPv4 IPv6957
AS41692OpenCarrier eGUnclassifiedIPv4 IPv6853
AS3320Deutsche Telekom AGMobileIPv4 IPv6292
AS44335nocyo GmbHUnclassifiedIPv4 IPv6268
AS34568ConnectingBytes GmbHHostingIPv4 IPv679
AS196922Hofmeir Media GmbHUnclassifiedIPv422

Provenance

Where this comes from

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