Observed topology
AS45204 GEMNET-MN GEMNET LLC
Unclassified APNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS45204: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 533 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 194 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 58 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 48 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 25 |
| AS17676 | SoftBank Corp. | Mobile | IPv4 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 13 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 | 12 |
Transit
Downstream networks
Networks for which AS45204 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17882 | UNIVISION LLC | Unclassified | IPv4 IPv6 | 8,154 |
| AS10219 | Skymedia Corporation | Residential | IPv4 IPv6 | 2,410 |
| AS141681 | ONDO LLC | Hosting | IPv4 IPv6 | 1,776 |
| AS56301 | National Data Center building | Unclassified | IPv4 IPv6 | 786 |
| AS9934 | Mongolia Telecom | Residential | IPv4 | 696 |
| AS45237 | Magicnet LLC | Unclassified | IPv4 | 580 |
| AS10109 | Topica LLC, Internet Service Provider,Ulaanbaatar, Mongolia | Unclassified | IPv4 IPv6 | 496 |
| AS24496 | GNET Co.,Ltd Internet Service Provider Mongolia | Residential | IPv4 | 464 |
| AS24320 | Railcom - Commercial Center, | Unclassified | IPv4 | 406 |
| AS38818 | YOKOZUNANET LLC | Unclassified | IPv4 | 232 |
Adjacency
Adjacent networks
Every AS seen directly next to AS45204 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 9,362 |
| AS17882 | UNIVISION LLC | Unclassified | IPv4 IPv6 | 8,919 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 5,660 |
| AS10219 | Skymedia Corporation | Residential | IPv4 IPv6 | 2,456 |
| AS141681 | ONDO LLC | Hosting | IPv4 IPv6 | 1,776 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 1,353 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 1,174 |
| AS56301 | National Data Center building | Unclassified | IPv4 IPv6 | 844 |
| AS9934 | Mongolia Telecom | Residential | IPv4 | 696 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 658 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.