Observed topology
AS151412 Gmax
Unclassified APNIC
Transit
Upstream networks
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
Networks for which AS151412 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS134749 | SPEED TECH ONLINE | Unclassified | IPv4 | 11 |
| AS138383 | Moustafa Ferdous | Unclassified | IPv4 | 4 |
| AS141386 | Ka Kha Computer | Unclassified | IPv4 | 4 |
| AS137553 | GLOBAL COMMUNICATION | Residential | IPv4 | 3 |
| AS151076 | Xennet | Unclassified | IPv4 | 3 |
| AS138482 | Skyview Online Ltd | Residential | IPv4 | 1 |
| AS151629 | Aalok IT Limited | Unclassified | IPv4 | 1 |
| AS153307 | Bangladesh Online Service | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS151412 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17494 | Telecom Operator & Internet Service Provider as well | Unclassified | IPv4 | 30 |
| AS134749 | SPEED TECH ONLINE | Unclassified | IPv4 | 11 |
| AS138383 | Moustafa Ferdous | Unclassified | IPv4 | 4 |
| AS141386 | Ka Kha Computer | Unclassified | IPv4 | 4 |
| AS137553 | GLOBAL COMMUNICATION | Residential | IPv4 | 3 |
| AS151076 | Xennet | Unclassified | IPv4 | 3 |
| AS138482 | Skyview Online Ltd | Residential | IPv4 | 1 |
| AS149649 | Speed Touch Network and Technology | Unclassified | IPv4 | 1 |
| AS150731 | Skyview Online Ltd | Unclassified | IPv4 | 1 |
| AS151629 | Aalok IT Limited | Unclassified | IPv4 | 1 |
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.