asn.dev

Observed topology

AS13631 CIG-AS

Unclassified ARIN

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS13631: 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
AS13335Cloudflare, Inc.HostingIPv4 IPv6227
AS6939Hurricane Electric LLCTransitIPv4156
AS3356Level 3 Parent, LLCTransitIPv4124
AS174Cogent Communications, LLCTransitIPv4111
AS23764CTGNetUnclassifiedIPv457
AS8220COLT Technology Services Group LimitedHostingIPv452
AS1299Arelion Sweden ABTransitIPv437
AS6461Zayo BandwidthTransitIPv434
AS24482SG.GSHostingIPv47
AS21859Zenlayer IncHostingIPv46

All 27 upstreams →

Transit

Downstream networks

inferred

Networks for which AS13631 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 27

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4 IPv6227
AS6939Hurricane Electric LLCTransitIPv4156
AS3356Level 3 Parent, LLCTransitIPv4124
AS174Cogent Communications, LLCTransitIPv4111
AS23764CTGNetUnclassifiedIPv457
AS8220COLT Technology Services Group LimitedHostingIPv452
AS1299Arelion Sweden ABTransitIPv437
AS6461Zayo BandwidthTransitIPv434
AS24482SG.GSHostingIPv47
AS21859Zenlayer IncHostingIPv46

All 27 adjacent →

Provenance

Where this comes from

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