asn.dev

Observed topology

AS25637 PRMTC - The Park Region Mutual Telephone Co

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS25637: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6219
AS15267702 CommunicationsResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS23036Northwest Minnesota Special Access, LLCUnclassifiedIPv462
AS398022Otter Tail Power CompanyUnclassifiedIPv447

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6326
AS23036Northwest Minnesota Special Access, LLCUnclassifiedIPv462
AS398022Otter Tail Power CompanyUnclassifiedIPv447
AS15267702 CommunicationsResidentialIPv45

Provenance

Where this comes from

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