AS399187 ASPA Check - City Of Bloomington

Published

COB-MN-US - City of Bloomington🇺🇸 - ASPA check for AS399187: the upstream transit providers AS399187 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS399187 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.

ASPA Status
Published
Upstream Providers
2
Downstream Customers
0

How to read this ASPA check

The 2 providers below are the only networks allowed to appear directly above AS399187 in an AS-path. If AS399187 uses a transit provider that is missing from this list, routers that enforce ASPA treat its routes through that provider as invalid, so the list should include every current and backup transit provider. Peers do not belong in it.

Step-by-step ASPA check guide - including how to validate an AS-path hop by hop.

Peering Topology

AS399187 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS174, AS209. No downstreams.AS399187 - COB-MN-US - City of BloomingtonAS399187COB-MN-US - City of B…AS174COGENT-174 - Cogent C…AS174 - COGENT-174 - Cogent Communications, LLCAS209CENTURYLINK-US-LEGACY…AS209 - CENTURYLINK-US-LEGACY-QWEST - CenturyLink Communications, LLCUPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS399187 authorizes these ASNs as upstream transit providers.

ASNName
AS174🇺🇸COGENT-174 - Cogent Communications, LLC
AS209🇺🇸CENTURYLINK-US-LEGACY-QWEST - CenturyLink Communications, LLC

ASPA object expires: 2026-10-28

Related Tools and Guides

← Back to AS399187