AS201011 CORE-BACKBONE Core-Backbone GmbH
🇩🇪Org handle: ORG-IICG1-RIPE
CORE-BACKBONE GMBH GLOBAL NETWORK
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
50total
33 IPv417 IPv6
IPv4 Addresses
Allocated (RIR)33,280
Announced (BGP)36,608
IPv6 Addresses
Allocated (RIR)1.2×10³⁰
Announced (BGP)1.2×10³⁰
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
100
Country
🇩🇪 DERIR
RIPE NCCStatus
allocated
Allocated
2015-02-20
Routing hygiene
Score 17/100 · Low riskRPKI ROA coverage
78%
no RPKI invalid prefixes
IRR route objects
96%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
- 22% of announced prefixes (11 of 50) have no valid ROA
Based on 50 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)50|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
1-10 of 50
1 / 5
Allocated Prefixes
(RIR)41Prefix | Country | RIR | Status |
|---|---|---|---|
| 2.59.28.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 5.56.16.0/21 | 🇩🇪 DE | RIPENCC | allocated |
| 31.7.176.0/20 | 🇩🇪 DE | RIPENCC | allocated |
| 31.7.177.0/24 | 🇳🇱 NL | RIPE | assigned |
| 80.255.0.0/20 | 🇩🇪 DE | RIPENCC | allocated |
| 81.95.0.0/20 | 🇩🇪 DE | RIPENCC | allocated |
| 82.199.128.0/19 | 🇩🇪 DE | RIPENCC | allocated |
| 82.199.131.0/24 | 🇦🇹 AT | RIPE | assigned |
| 82.199.147.0/24 | 🇩🇪 DE | RIPE | assigned |
| 82.199.149.0/24 | 🇩🇪 DE | RIPE | assigned |
1-10 of 41
1 / 5
All 50 announced prefixes of AS201011 →
Upstream Providers(1)
| ASN | Name |
|---|---|
| AS33891 | 🇩🇪CORE-BACKBONE Core-Backbone GmbH |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201011 hands its own prefixes to: transit providers, or peers at an exchange.
- AS33891CORE BACKBONE Core Backbone50
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/201011Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201011" | jq