AS31605 ALLOY-NETWORKS Titanium OU
🇪🇪Org handle: ORG-TO320-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.139.107.0/24 | 🇪🇪 EE | RIPENCC | allocated |
| 46.29.35.0/24 | 🇪🇪 EE | RIPENCC | allocated |
| 2a13:cec0::/29 | 🇪🇪 EE | RIPENCC | allocated |
All 3 announced prefixes of AS31605 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS31605 hands its own prefixes to: transit providers, or peers at an exchange.
- AS3249ESTPAK Telia Eesti3
Transfer History
Registry transfers of AS31605 between organisations.
- AS31605Transfer ·
- AS31605Transfer ·
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 AS31605 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/31605Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/31605" | jq