asn.dev

Observed topology

AS150774 EXABYTELTD2-AS-AP - EXABYTE LTD

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS150774: 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
AS150178EXABYTE LTDUnclassifiedIPv4 IPv61,666
AS136014SS OnlineUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136010SEBA ITUnclassifiedIPv4252
AS136156MD Rehanur Rahman t/a M/S FNF OnlineUnclassifiedIPv4149
AS150718Pioneer Services LimitedUnclassifiedIPv459
AS135308unnamedUnclassifiedIPv42
AS135341Orange CommunicationUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS150178EXABYTE LTDUnclassifiedIPv4 IPv62,129
AS136010SEBA ITUnclassifiedIPv4252
AS136156MD Rehanur Rahman t/a M/S FNF OnlineUnclassifiedIPv4149
AS150718Pioneer Services LimitedUnclassifiedIPv459
AS135308unnamedUnclassifiedIPv42
AS135341Orange CommunicationUnclassifiedIPv41
AS136014SS OnlineUnclassifiedIPv41

Provenance

Where this comes from

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