AS42013 ASPA Check - Together Communication Together Communication

Published

Together-Communication-LTD Together Communication LTD🇵🇸 - ASPA check for AS42013: the upstream transit providers AS42013 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS42013 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 AS42013 in an AS-path. If AS42013 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

AS42013 peering topology: 2 upstream providers and 0 downstream customersUpstreams: AS1680, AS8551. No downstreams.AS42013 - Together-Communication-LTD Together Communication LTDAS42013Together-Communicatio…AS1680NV-ASN CELLCOM ltd.AS1680 - NV-ASN CELLCOM ltd.AS8551BEZEQ-INTERNATIONAL-A…AS8551 - BEZEQ-INTERNATIONAL-AS Bezeq International Ltd.UPSTREAMSDOWNSTREAMS

Upstream Providers(2)

AS42013 authorizes these ASNs as upstream transit providers.

ASNName
AS1680🇮🇱NV-ASN CELLCOM ltd.
AS8551🇮🇱BEZEQ-INTERNATIONAL-AS Bezeq International Ltd.

ASPA object expires: 2026-10-29

Related Tools and Guides

← Back to AS42013