asn.dev

Observed topology

AS11031 ORBIS-INVESTMENTS - Orbis Investments (Canada) Limited

Unclassified ARIN

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS11031: 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
AS6461Zayo BandwidthTransitIPv4227
AS9304HGC Global Communications LimitedHostingIPv4108
AS10143Exetel Pty LtdResidentialIPv497
AS577Bell CanadaMobileIPv454
AS2856British Telecommunications LimitedResidentialIPv449
AS3855Logic Communications LtdResidentialIPv444
AS2764AAPT LimitedUnclassifiedIPv418
AS32020Transact Ltd.UnclassifiedIPv414
AS25160Vorboss LimitedResidentialIPv410
AS4515PCCW IMS Ltd (PCCW Business Internet Access)UnclassifiedIPv48

Transit

Downstream networks

inferred

Networks for which AS11031 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 13

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4227
AS9304HGC Global Communications LimitedHostingIPv4108
AS10143Exetel Pty LtdResidentialIPv497
AS577Bell CanadaMobileIPv454
AS2856British Telecommunications LimitedResidentialIPv449
AS3855Logic Communications LtdResidentialIPv444
AS2764AAPT LimitedUnclassifiedIPv418
AS32020Transact Ltd.UnclassifiedIPv414
AS25160Vorboss LimitedResidentialIPv410
AS4515PCCW IMS Ltd (PCCW Business Internet Access)UnclassifiedIPv48

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.