AS204789 BizbetaLTD BIZBETA LTD
🇬🇧Org handle: ORG-BL521-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
19total
0 IPv419 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)8.4×10²⁸
Announced (BGP)8.3×10²⁸
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
100
Country
🇬🇧 GBRIR
RIPE NCCStatus
allocated
Allocated
2022-09-19
Routing hygiene
Score 2/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
8
diversity 82/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 19 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)19|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARIN | 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 19
1 / 2
Allocated Prefixes
(RIR)21Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a05:b0c7:1000::/39 | 🇸🇬 SG | RIPE | assigned |
| 2a06:1286::/32 | 🇸🇬 SG | RIPE | assigned |
| 2a06:1286::/40 | 🇸🇬 SG | RIPE | assigned |
| 2a06:1286:100::/40 | 🇳🇴 NO | RIPE | assigned |
| 2a06:1286:200::/40 | 🇺🇸 US | RIPE | assigned |
| 2a06:1286:300::/40 | 🇺🇸 US | RIPE | assigned |
| 2a06:1286:400::/40 | 🇳🇱 NL | RIPE | assigned |
| 2a06:1286:500::/40 | 🇱🇺 LU | RIPE | assigned |
| 2a06:1286:600::/40 | 🇸🇬 SG | RIPE | assigned |
| 2a06:1286:700::/40 | 🇸🇬 SG | RIPE | assigned |
1-10 of 21
1 / 3
All 19 announced prefixes of AS204789 →
BGP Neighbours
(seen in AS paths)Upstreams (8)
Networks AS204789 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS204789 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/204789Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/204789" | jq