asn.dev

Observed topology

AS10991 CAPGE-HOSTING-MRO

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10991: 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
AS174Cogent Communications, LLCTransitIPv4879
AS5511Orange S.A.TransitIPv4732
AS6461Zayo BandwidthTransitIPv4501
AS3356Level 3 Parent, LLCTransitIPv4151
AS1299Arelion Sweden ABTransitIPv479
AS1273IDDQD-ASBusinessIPv457

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60297Capgemini UK plcUnclassifiedIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4879
AS5511Orange S.A.TransitIPv4738
AS6461Zayo BandwidthTransitIPv4501
AS3356Level 3 Parent, LLCTransitIPv4151
AS1299Arelion Sweden ABTransitIPv479
AS1273IDDQD-ASBusinessIPv457
AS60297Capgemini UK plcUnclassifiedIPv46

Provenance

Where this comes from

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