AS50368 BULSATTV-AS Bulsat Ltd.
๐ง๐ฌOrg handle: ORG-BL92-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,792
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
๐ง๐ฌ BGRIR
RIPE NCCStatus
allocated
Allocated
2009-12-29
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 87.121.128.0/22 | ๐ง๐ฌ BG | RIPENCC | allocated |
All 4 announced prefixes of AS50368 โ
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS50368 hands its own prefixes to: transit providers, or peers at an exchange.
- AS29030Telekabel TELECABEL PLC4
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 AS50368 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/50368Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50368" | jq