AS396313 MOCTEL - MocTel
π¨π¦ARINassigned
Announced Prefixes (BGP)
5total
5 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)4.9Γ10Β²β·
Announced (BGP)0
Routing hygiene
Score 4/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
3
diversity 56/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 5 announced prefixes, updated daily (2026-10-24). How the score works Β· RPKI explained
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARIN | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | - | 2026-10-26 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 23.171.128.0/24 | π¨π¦ CA | ARIN | allocated |
| 199.250.60.0/22 | π¨π¦ CA | ARIN | allocated |
| 2602:fef2::/36 | π¨π¦ CA | ARIN | allocated |
All 5 announced prefixes of AS396313 β
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS396313 hands its own prefixes to: transit providers, or peers at an exchange.
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/396313Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/396313" | jq