AS52041 SCALEBLADE Scaleblade, Ltd.
🇬🇧Org handle: ORG-SL1164-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
22total
13 IPv49 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)3,328
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)2.9×10²⁵
Routing hygiene
Score 5/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
90.9%
2 prefixes registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
5
diversity 67/100
- No significant routing hygiene issues found
Based on 22 announced prefixes, updated daily (2026-10-19). How the score works · RPKI explained
Announced Prefixes
(BGP)22|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARIN | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Invalid | - | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 | |
130.12.142.0/24MOAS | Valid | - | 2026-10-26 |
130.12.143.0/24MOAS | Valid | - | 2026-10-26 |
1-10 of 22
1 / 3
Allocated Prefixes
(RIR)16Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.84.91.0/24 | 🇬🇧 GB | RIPE | assigned |
| 82.215.64.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 85.208.112.0/24 | 🇬🇧 GB | RIPE | assigned |
| 86.54.213.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 87.121.44.0/24 | 🇧🇬 BG | RIPENCC | allocated |
| 185.248.134.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 194.46.57.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 194.180.36.0/24 | 🇬🇧 GB | RIPE | assigned |
| 2a12:bec0::/29 | 🇬🇧 GB | RIPENCC | allocated |
| 2a12:bec0:7d::/48 | 🇺🇸 US | RIPE | assigned |
1-10 of 16
1 / 2
All 22 announced prefixes of AS52041 →
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS52041 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (8)
Networks whose own prefixes AS52041 passes on: usually its customers.
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/52041Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/52041" | jq