AS31389 ATOMIDATA-AS Atomidata Oy
🇫🇮Org handle: ORG-AO136-RIPE
Atomidata Oy
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)3,328
Announced (BGP)2,560
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.61.92.0/24 | 🇫🇮 FI | RIPENCC | allocated |
| 45.14.201.0/24 | 🇫🇮 FI | RIPENCC | allocated |
| 78.108.118.0/24 | 🇫🇮 FI | RIPENCC | allocated |
| 164.5.224.0/21 | 🇫🇮 FI | RIPENCC | assigned |
| 164.5.232.0/23 | 🇫🇮 FI | RIPENCC | assigned |
| 2a13:82c0::/29 | 🇫🇮 FI | RIPENCC | allocated |
All 4 announced prefixes of AS31389 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS31389 hands its own prefixes to: transit providers, or peers at an exchange.
- AS204779LOCALNETFI Local Loop Oy4
Transfer History
Registry transfers of AS31389 between organisations.
- AS31389Transfer ·
- AS31389M&A ·
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 AS31389 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/31389Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/31389" | jq