asn.dev

Observed topology

AS557 UMAINE-SYS-AS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS557: 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 IPv6809
AS174Cogent Communications, LLCTransitIPv4 IPv6212
AS11537Internet2UnclassifiedIPv4 IPv687
AS13536FirstLight Fiber, Inc.ResidentialIPv476
AS11164Internet2EducationIPv4 IPv616

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS55032The Jackson LaboratoryUnclassifiedIPv4830
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv6103
AS17152Bates CollegeUnclassifiedIPv4 IPv6103
AS22847Bowdoin CollegeUnclassifiedIPv4 IPv673
AS6056Colby CollegeEducationIPv469

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,695
AS55032The Jackson LaboratoryUnclassifiedIPv4830
AS174Cogent Communications, LLCTransitIPv4 IPv6401
AS11537Internet2UnclassifiedIPv4 IPv6180
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv6103
AS17152Bates CollegeUnclassifiedIPv4 IPv6103
AS22847Bowdoin CollegeUnclassifiedIPv4 IPv681
AS13536FirstLight Fiber, Inc.ResidentialIPv476
AS6056Colby CollegeEducationIPv469
AS11164Internet2EducationIPv4 IPv634

Provenance

Where this comes from

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