Observed topology

AS26271 CMSINTERNET

Residential ARIN

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 3

Upstream graph Who carries AS26271, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS26271 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26271: 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
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	744
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	162
AS20205	Amplex Electric, Inc.	Residential	IPv4	13

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS33583	Isabella Bank Corporation	Unclassified	IPv4	183
AS62968	Central Michigan Communication, Co.	Unclassified	IPv4	120
AS14691	Great Lakes Adventist Academy	Unclassified	IPv4 IPv6	102

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	1,098
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	213
AS33583	Isabella Bank Corporation	Unclassified	IPv4	183
AS62968	Central Michigan Communication, Co.	Unclassified	IPv4	120
AS14691	Great Lakes Adventist Academy	Unclassified	IPv4 IPv6	102
AS20205	Amplex Electric, Inc.	Residential	IPv4	13

Provenance

Where this comes from

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