AS64449 DATAKON1 Datakonsult Magnus Sandberg
πΈπͺOrg handle: ORG-MEM3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)2.4Γ10Β²β΄
Announced (BGP)1.2Γ10Β²β΄
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
πΈπͺ SERIR
RIPE NCCStatus
allocated
Allocated
2016-08-19
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 2001:678:1d4::/48 | πΈπͺ SE | RIPENCC | assigned |
| 2001:67c:d08::/48 | πΈπͺ SE | RIPENCC | assigned |
All 2 announced prefixes of AS64449 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS64449 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8473BAHNHOF AB2
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 AS64449 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/64449Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/64449" | jq