asn.dev

Observed topology

AS56971 AS56971 CGI GLOBAL LIMITED

Hosting RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS56971: 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
AS9002RETN LimitedUnclassifiedIPv42,936
AS8285SIAHostingIPv4 IPv61,963
AS49434FBW NETWORKS SASUnclassifiedIPv4 IPv61,673
AS3257GTT Communications Inc.TransitIPv4 IPv61,160
AS6939Hurricane Electric LLCTransitIPv4 IPv61,088
AS32097WholeSale Internet, Inc.HostingIPv4 IPv6673
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6522
AS135330ADCDATA.COMHostingIPv4 IPv6432
AS40676Psychz NetworksHostingIPv4180
AS24482SG.GSHostingIPv4 IPv617

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56594CGI GLOBAL LIMITEDUnclassifiedIPv4739

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv43,090
AS8285SIAHostingIPv4 IPv61,990
AS49434FBW NETWORKS SASUnclassifiedIPv4 IPv61,673
AS3257GTT Communications Inc.TransitIPv4 IPv61,391
AS6939Hurricane Electric LLCTransitIPv4 IPv61,088
AS50673Serverius Holding B.V.UnclassifiedIPv4 IPv6849
AS56594CGI GLOBAL LIMITEDUnclassifiedIPv4739
AS32097WholeSale Internet, Inc.HostingIPv4 IPv6673
AS135330ADCDATA.COMHostingIPv4 IPv6432
AS40676Psychz NetworksHostingIPv4180

All 16 adjacent →

Provenance

Where this comes from

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