Observed topology
AS9484 MOBINET-AS-MN Mobinet LLC. AS Mobinet Internet Service Provider
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS9484: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS55805 | MobiCom Corporation | Unclassified | IPv4 IPv6 | 558 |
Transit
Downstream networks
Networks for which AS9484 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS133851 | Xacbank | Unclassified | IPv4 | 104 |
| AS152299 | Statebank of Mongolia | Unclassified | IPv4 | 92 |
| AS134074 | Golomt Bank | Unclassified | IPv4 | 86 |
| AS151637 | Erdenet Mining Corporation | Unclassified | IPv4 | 58 |
| AS138907 | KHAN BANK LLC | Unclassified | IPv4 | 55 |
| AS10076 | ERDEMNET Mongolian National Research and Education Network | Education | IPv4 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9484 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS55805 | MobiCom Corporation | Unclassified | IPv4 IPv6 | 967 |
| AS133851 | Xacbank | Unclassified | IPv4 | 104 |
| AS152299 | Statebank of Mongolia | Unclassified | IPv4 | 92 |
| AS134074 | Golomt Bank | Unclassified | IPv4 | 86 |
| AS151637 | Erdenet Mining Corporation | Unclassified | IPv4 | 58 |
| AS138907 | KHAN BANK LLC | Unclassified | IPv4 | 55 |
| AS10076 | ERDEMNET Mongolian National Research and Education Network | Education | IPv4 | 14 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.