AS53904 CANARIE-INC - CANARIE Inc
🇨🇦ARINassigned
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 6/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 44/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 3 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRR | 2026-10-25 | |
| Valid | Other IRR | 2026-10-25 | |
| Valid | Other IRR | 2026-10-25 |
All 3 announced prefixes of AS53904 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS53904 hands its own prefixes to: transit providers, or peers at an exchange.
Other adjacent networks (1)
Adjacent to AS53904 in the transit part of AS paths: peers, providers or customers.
- AS6327Shaw Communications1
ASPA
No ASPA
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS53904 should publish an ASPA object
- IPv4 transfers in the ARIN regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/53904Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/53904" | jq