asn.dev

Observed topology

AS6681 GIVEME-CLOUD

Hosting RIPE Content

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS6681: 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
AS1299Arelion Sweden ABTransitIPv4258
AS9002RETN LimitedUnclassifiedIPv4204
AS35320Eurotranstelecom LtdUnclassifiedIPv456
AS59711HZ Hosting LtdUnclassifiedIPv424
AS6939Hurricane Electric LLCTransitIPv421
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv43
AS4657StarHub LtdResidentialIPv43
AS6696VERIXI SAUnclassifiedIPv43
AS17639Converge ICT Solutions Inc.UnclassifiedIPv43
AS20485Joint Stock Company TransTeleComUnclassifiedIPv43

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59711HZ Hosting LtdUnclassifiedIPv4480
AS43896EVO CLOUD LLCHostingIPv454

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS59711HZ Hosting LtdUnclassifiedIPv4527
AS1299Arelion Sweden ABTransitIPv4459
AS9002RETN LimitedUnclassifiedIPv4403
AS35320Eurotranstelecom LtdUnclassifiedIPv4191
AS43896EVO CLOUD LLCHostingIPv454
AS6939Hurricane Electric LLCTransitIPv421
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv43
AS4657StarHub LtdResidentialIPv43
AS6696VERIXI SAUnclassifiedIPv43
AS17639Converge ICT Solutions Inc.UnclassifiedIPv43

All 16 adjacent →

Provenance

Where this comes from

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