AS61316 iPROsrv WEB3 Leaders INC
🇨🇦Org handle: ORG-WLI2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.10.208.0/22 | 🇨🇦 CA | RIPENCC | allocated |
| 193.33.212.0/23 | 🇨🇦 CA | RIPENCC | assigned |
| 2a03:6540::/32 | 🇨🇦 CA | RIPENCC | allocated |
All 3 announced prefixes of AS61316 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS61316 hands its own prefixes to: transit providers, or peers at an exchange.
- AS24700Paritetweb WEB3 Leaders3
ASPA
No ASPA
Abuse Contact
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 AS61316 should publish an ASPA object
- IPv4 transfers in the RIPE NCC 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/61316Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/61316" | jq