asn.dev

Observed topology

AS204582 TCI-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204582: 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
AS8985Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv61,514
AS6939Hurricane Electric LLCTransitIPv4 IPv6406
AS24482SG.GSHostingIPv4 IPv639
AS49673Truenetwork LLCUnclassifiedIPv428

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61992Internet Identification Center Limited Liability CompanyUnclassifiedIPv4 IPv6215

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8985Join-stock company "Internet Exchange"MSK-IX"UnclassifiedIPv4 IPv61,659
AS6939Hurricane Electric LLCTransitIPv4 IPv6469
AS61992Internet Identification Center Limited Liability CompanyUnclassifiedIPv4 IPv6215
AS24482SG.GSHostingIPv4 IPv644
AS49673Truenetwork LLCUnclassifiedIPv430

Provenance

Where this comes from

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