asn.dev

Observed topology

AS12198 JSMSR-LLC

Unclassified ARIN NSP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS12198: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv6235
AS216211CYBERVERSE LLCHostingIPv6215
AS18450WebNX, Inc.HostingIPv4 IPv6139
AS983Akari Networks LLCHostingIPv4105
AS44324MoeDove LLCResidentialIPv666
AS38074SDCC Japan-West AreaUnclassifiedIPv665
AS6939Hurricane Electric LLCTransitIPv635
AS27523Kawaii Networks LLCUnclassifiedIPv632
AS206628Tianyu-ZhuUnclassifiedIPv632
AS37989DCS1 Pte. Ltd.HostingIPv614

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS401009JSMSR NetworkResidentialIPv6103
AS403098skimitUnclassifiedIPv636

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS216211CYBERVERSE LLCHostingIPv6256
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv6235
AS18450WebNX, Inc.HostingIPv4 IPv6139
AS983Akari Networks LLCHostingIPv4105
AS401009JSMSR NetworkResidentialIPv6103
AS206628Tianyu-ZhuUnclassifiedIPv680
AS6939Hurricane Electric LLCTransitIPv671
AS44324MoeDove LLCResidentialIPv666
AS38074SDCC Japan-West AreaUnclassifiedIPv665
AS403098skimitUnclassifiedIPv636

All 17 adjacent →

Provenance

Where this comes from

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