asn.dev

Observed topology

AS215540 GCS-AS GLOBAL CONNECTIVITY SOLUTIONS LLP

Hosting Spamhaus ASN-DROP RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS215540: 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
AS48014Albanian Hosting SH.P.K.HostingIPv4 IPv67,613
AS63023GTHostHostingIPv4 IPv64,013
AS51765Oy Crea Nova Hosting Solution LtdHostingIPv4 IPv61,186
AS30823aurologic GmbHHostingIPv4 IPv6504
AS135330ADCDATA.COMHostingIPv4 IPv6389
AS60798Servereasy SrlHostingIPv4 IPv6320
AS39900SIA GOODUnclassifiedIPv4 IPv6264
AS44222Nuno FelgueirasUnclassifiedIPv4 IPv6258
AS62563GLOBALTELEHOST Corp.HostingIPv4 IPv6230
AS56655Gigahost ASUnclassifiedIPv4 IPv6228

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26383Baxet Group Inc.UnclassifiedIPv4 IPv6144
AS218341Domains Registration LLPUnclassifiedIPv457

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS48014Albanian Hosting SH.P.K.HostingIPv4 IPv67,670
AS63023GTHostHostingIPv4 IPv64,013
AS51765Oy Crea Nova Hosting Solution LtdHostingIPv4 IPv61,186
AS30823aurologic GmbHHostingIPv4 IPv6504
AS44222Nuno FelgueirasUnclassifiedIPv4 IPv6402
AS135330ADCDATA.COMHostingIPv4 IPv6389
AS60798Servereasy SrlHostingIPv4 IPv6320
AS39900SIA GOODUnclassifiedIPv4 IPv6264
AS62563GLOBALTELEHOST Corp.HostingIPv4 IPv6230
AS56655Gigahost ASUnclassifiedIPv4 IPv6228

Provenance

Where this comes from

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