AS50020 RACCOM-AS CETIN Bulgaria EAD
π§π¬Org handle: ORG-CBE2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,328
Announced (BGP)3,328
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
π§π¬ BGRIR
RIPE NCCStatus
allocated
Allocated
2009-10-27
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.16.192.0/21 | π§π¬ BG | RIPENCC | allocated |
| 185.201.36.0/22 | π§π¬ BG | RIPENCC | allocated |
| 193.104.79.0/24 | π§π¬ BG | RIPENCC | assigned |
All 3 announced prefixes of AS50020 β
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS50020 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (6)
Networks whose own prefixes AS50020 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS50020 in the transit part of AS paths: peers, providers or customers.
- AS44901Belcloud1
Transfer History
Registry transfers of AS50020 between organisations.
- AS50020M&A Β·
- AS50020M&A Β·
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 AS50020 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/50020Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50020" | jq