asn.dev

Observed topology

AS18897 MONTANA-SKY-NETWORKS-INC - Montana Sky Networks, Inc.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18897: 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
AS20055Wholesail networks LLCResidentialIPv4 IPv6493
AS20119Arrow Group Inc.UnclassifiedIPv4 IPv6284
AS6653Vero BroadbandResidentialIPv4140

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS33402Bullitt CommunicationsUnclassifiedIPv4 IPv693
AS395786Nomad Global Communications Solutions, Inc.UnclassifiedIPv458
AS399455IP Routing LLCUnclassifiedIPv457

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS20055Wholesail networks LLCResidentialIPv4 IPv6610
AS20119Arrow Group Inc.UnclassifiedIPv4 IPv6340
AS6653Vero BroadbandResidentialIPv4205
AS33402Bullitt CommunicationsUnclassifiedIPv4 IPv693
AS395786Nomad Global Communications Solutions, Inc.UnclassifiedIPv458
AS399455IP Routing LLCUnclassifiedIPv457

Provenance

Where this comes from

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