AS153169 ASPA Check - BengalCloud

Published

BENGALCLOUD-AS-AP - BengalCloud🇧🇩 - ASPA check for AS153169: the upstream transit providers AS153169 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS153169 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 AS153169 in an AS-path. If AS153169 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

AS153169 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS17644, AS29802. No downstreams.AS153169 - BENGALCLOUD-AS-AP - BengalCloudAS153169BENGALCLOUD-AS-AP - B…AS17644IOT-AS-AP - IoT Techs…AS17644 - IOT-AS-AP - IoT Techsmart Pte. Ltd.AS29802HVC-AS - HIVELOCITY, …AS29802 - HVC-AS - HIVELOCITY, Inc.UPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS153169 authorizes these ASNs as upstream transit providers.

ASNName
AS17644🇧🇩IOT-AS-AP - IoT Techsmart Pte. Ltd.
AS29802🇺🇸HVC-AS - HIVELOCITY, Inc.

ASPA object expires: 2026-11-11

Related Tools and Guides

← Back to AS153169