AS201456 AVESTA-KOMMUN-ASN Avesta Kommun
🇸🇪Org handle: ORG-AVES1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 48/100 · Medium riskRPKI ROA coverage
0%
no RPKI invalid prefixes
IRR route objects
50%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (2 of 2) have no valid ROA
- Only one upstream seen in the AS paths of its routes
- 50% of announced prefixes (1 of 2) have no IRR route object for this ASN
Based on 2 announced prefixes, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-12 | |
| No ROA | RIPE | 2026-10-12 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.234.150.0/24 | 🇸🇪 SE | RIPE | assigned |
| 2001:67c:1754::/48 | 🇸🇪 SE | RIPENCC | assigned |
All 2 announced prefixes of AS201456 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201456 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 AS201456 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/201456Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201456" | jq