asn.dev

Observed topology

AS62167 TISMI

Unclassified RIPE NSP

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

Transit

Upstream networks

All 37

Networks observed carrying traffic for AS62167: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6294
AS174Cogent Communications, LLCTransitIPv4 IPv6144
AS1299Arelion Sweden ABTransitIPv4 IPv6122
AS3257GTT Communications Inc.TransitIPv4 IPv6103
AS3356Level 3 Parent, LLCTransitIPv4 IPv687
AS24785Broadband Hosting B.V.HostingIPv4 IPv643
AS20562Broadband Hosting B.V.HostingIPv4 IPv636
AS12552GlobalConnect ABUnclassifiedIPv430
AS24482SG.GSHostingIPv4 IPv618
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv615

Transit

Downstream networks

inferred

Networks for which AS62167 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 37

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6294
AS174Cogent Communications, LLCTransitIPv4 IPv6144
AS1299Arelion Sweden ABTransitIPv4 IPv6122
AS3257GTT Communications Inc.TransitIPv4 IPv6103
AS3356Level 3 Parent, LLCTransitIPv4 IPv687
AS24785Broadband Hosting B.V.HostingIPv4 IPv643
AS20562Broadband Hosting B.V.HostingIPv4 IPv636
AS12552GlobalConnect ABUnclassifiedIPv430
AS24482SG.GSHostingIPv4 IPv618
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv615

Provenance

Where this comes from

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