asn.dev

Observed topology

AS13150 CATON CATO NETWORKS LTD

Unclassified RIPE

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

Transit

Upstream networks

All 112

Networks observed carrying traffic for AS13150: 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 ABTransitIPv44,697
AS6939Hurricane Electric LLCTransitIPv41,816
AS3356Level 3 Parent, LLCTransitIPv41,644
AS3257GTT Communications Inc.TransitIPv41,351
AS2914NTT America, Inc.TransitIPv41,235
AS6461Zayo BandwidthTransitIPv4395
AS9583Sify LimitedUnclassifiedIPv4280
AS2516KDDI CORPORATIONMobileIPv4212
AS8220COLT Technology Services Group LimitedHostingIPv4212
AS4826Vocus Connect International BackboneUnclassifiedIPv4194

All 112 upstreams →

Transit

Downstream networks

inferred

Networks for which AS13150 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 112

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv44,697
AS6939Hurricane Electric LLCTransitIPv41,816
AS3356Level 3 Parent, LLCTransitIPv41,644
AS3257GTT Communications Inc.TransitIPv41,351
AS2914NTT America, Inc.TransitIPv41,235
AS6461Zayo BandwidthTransitIPv4395
AS9583Sify LimitedUnclassifiedIPv4280
AS2516KDDI CORPORATIONMobileIPv4212
AS8220COLT Technology Services Group LimitedHostingIPv4212
AS4826Vocus Connect International BackboneUnclassifiedIPv4194

All 112 adjacent →

Provenance

Where this comes from

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