AS32277 ASPA Check - TBayTel
PublishedTBAYTEL - TBayTel🇨🇦 - ASPA check for AS32277: the upstream transit providers AS32277 has authorized in its RPKI Autonomous System Provider Authorization (ASPA) object, and the networks that list AS32277 as their provider. Routers that validate ASPA use these records to detect route leaks in BGP paths.
How to read this ASPA check
The 13 providers below are the only networks allowed to appear directly above AS32277 in an AS-path. If AS32277 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
Upstream Providers(13)
AS32277 authorizes these ASNs as upstream transit providers.
| ASN | Name |
|---|---|
| AS812 | 🇨🇦ROGERS-COMMUNICATIONS - Rogers Communications Canada Inc. |
| AS3257 | 🇺🇸GTT-BACKBONE GTT Communications Inc. |
| AS5645 | 🇨🇦TEKSAVVY - TekSavvy Solutions, Inc. |
| AS5690 | 🇨🇦VIANET INC 5690 - Vianet Inc. |
| AS6461 | 🇺🇸ZAYO-6461 - Zayo Bandwidth |
| AS11342 | 🇨🇦PATHWAY - Pathway Communications |
| AS11666 | 🇨🇦NEXICOM-CA - Nexicom Inc. |
| AS11814 | 🇨🇦DISTRIBUTEL-AS11814 - Distributel Communications Limited |
| AS14116 | 🇨🇦INFB-AS - Internet Names For Business Inc. |
| AS15169 | 🇺🇸GOOGLE - Google LLC |
ASPA object expires: 2026-10-27
Related Tools and Guides
- How to run an ASPA check - read and verify an ASPA record step by step
- ASPA explained - how provider authorization stops route leaks
- ASPA Check tool - check the ASPA record of any other ASN
- RPKI & ROA Lookup - validate prefixes and check ASPA records for any ASN
- Global ASPA Adoption Statistics - transit-free ASNs, top upstream providers, adoption trends
- AS32277 Overview - prefixes, BGP routes, peers, and RPKI status