Observed topology

AS30257 GEMC - Gibson Electric Membership Corporation

Unclassified ARIN

Upstreams 4 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30257: 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	326
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	81
AS55140	Sho Me Technologies, LLC	Residential	IPv4	12
AS174	Cogent Communications, LLC	Transit	IPv6	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS401918	Humboldt Utilities Broadband	Unclassified	IPv4 IPv6	543
AS395712	Milan Public Utilities Authority	Unclassified	IPv4 IPv6	265
AS13986	ECSIS.NET	Unclassified	IPv4	128
AS397057	Forked Deer Electric Cooperative, Inc.	Unclassified	IPv4	126
AS400093	Direct Customer Solutions, LLC	Unclassified	IPv4	64

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	1,291
AS401918	Humboldt Utilities Broadband	Unclassified	IPv4 IPv6	543
AS395712	Milan Public Utilities Authority	Unclassified	IPv4 IPv6	265
AS6461	Zayo Bandwidth	Transit	IPv4 IPv6	172
AS13986	ECSIS.NET	Unclassified	IPv4	128
AS397057	Forked Deer Electric Cooperative, Inc.	Unclassified	IPv4	126
AS55140	Sho Me Technologies, LLC	Residential	IPv4	76
AS400093	Direct Customer Solutions, LLC	Unclassified	IPv4	64
AS174	Cogent Communications, LLC	Transit	IPv6	7

Provenance

Where this comes from

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