asn.dev

Observed topology

AS151412 Gmax

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS151412: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS134749SPEED TECH ONLINEUnclassifiedIPv411
AS138383Moustafa FerdousUnclassifiedIPv44
AS141386Ka Kha ComputerUnclassifiedIPv44
AS137553GLOBAL COMMUNICATIONResidentialIPv43
AS151076XennetUnclassifiedIPv43
AS138482Skyview Online LtdResidentialIPv41
AS151629Aalok IT LimitedUnclassifiedIPv41
AS153307Bangladesh Online ServiceUnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS17494Telecom Operator & Internet Service Provider as wellUnclassifiedIPv430
AS134749SPEED TECH ONLINEUnclassifiedIPv411
AS138383Moustafa FerdousUnclassifiedIPv44
AS141386Ka Kha ComputerUnclassifiedIPv44
AS137553GLOBAL COMMUNICATIONResidentialIPv43
AS151076XennetUnclassifiedIPv43
AS138482Skyview Online LtdResidentialIPv41
AS149649Speed Touch Network and TechnologyUnclassifiedIPv41
AS150731Skyview Online LtdUnclassifiedIPv41
AS151629Aalok IT LimitedUnclassifiedIPv41

Provenance

Where this comes from

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