AS204511 NO-UPHEADS-INT Upheads AS
π³π΄Org handle: ORG-UA280-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
π³π΄ NORIR
RIPE NCCStatus
allocated
Allocated
2018-02-26
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.197.116.0/24 | π³π΄ NO | RIPE | assigned |
| 185.197.118.0/24 | πΈπͺ SE | RIPE | assigned |
All 1 announced prefix of AS204511 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS204511 hands its own prefixes to: transit providers, or peers at an exchange.
- AS29518BREDBAND2 AB1
Transfer History
Registry transfers of AS204511 between organisations.
- AS204511M&A Β·
- AS204511M&A Β·
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS204511 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/204511Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/204511" | jq