asn.dev

Observed topology

AS8918 CARRIER1-AS Coolwave Communications Limited

Unclassified RIPE

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS8918: 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
AS31655Gamma Telecom Holdings LtdUnclassifiedIPv473
AS3257GTT Communications Inc.TransitIPv452
AS20562Broadband Hosting B.V.HostingIPv430
AS6939Hurricane Electric LLCTransitIPv421
AS24785Broadband Hosting B.V.HostingIPv416
AS6696VERIXI SAUnclassifiedIPv43
AS12552GlobalConnect ABUnclassifiedIPv43
AS12779IT.Gate S.p.A.UnclassifiedIPv43
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43
AS24482SG.GSHostingIPv43

Transit

Downstream networks

inferred

Networks for which AS8918 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 20

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

ASNetworkTypeFamiliesPaths seen
AS31655Gamma Telecom Holdings LtdUnclassifiedIPv473
AS3257GTT Communications Inc.TransitIPv452
AS20562Broadband Hosting B.V.HostingIPv430
AS6939Hurricane Electric LLCTransitIPv421
AS24785Broadband Hosting B.V.HostingIPv416
AS6696VERIXI SAUnclassifiedIPv43
AS12552GlobalConnect ABUnclassifiedIPv43
AS12779IT.Gate S.p.A.UnclassifiedIPv43
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43
AS24482SG.GSHostingIPv43

Provenance

Where this comes from

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