asn.dev

Observed topology

AS204104 GSC Giti Secure Cloud LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204104: 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
AS211421Asiatech Data Transmission companyUnclassifiedIPv4 IPv61,131
AS62403PletX GmbHUnclassifiedIPv4480
AS42337Respina Networks & Beyond PJSCUnclassifiedIPv4 IPv6217
AS43754Asiatech Data Transmission companyUnclassifiedIPv4 IPv6126

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214078AMIR MOHAMMAD ZARIFIUnclassifiedIPv4181

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS211421Asiatech Data Transmission companyUnclassifiedIPv4 IPv61,312
AS62403PletX GmbHUnclassifiedIPv4480
AS42337Respina Networks & Beyond PJSCUnclassifiedIPv4 IPv6217
AS214078AMIR MOHAMMAD ZARIFIUnclassifiedIPv4181
AS43754Asiatech Data Transmission companyUnclassifiedIPv4 IPv6126

Provenance

Where this comes from

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