AS209360 bulud Bulud Telecom LLC
🇦🇿Org handle: ORG-BTL59-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARIN | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| Valid | ARIN | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.32.177.0/24 | 🇦🇿 AZ | RIPENCC | allocated |
| 130.193.74.0/24 | 🇦🇿 AZ | RIPENCC | allocated |
| 193.105.123.0/24 | 🇦🇿 AZ | RIPENCC | allocated |
| 2a0d:2700::/29 | 🇦🇿 AZ | RIPENCC | allocated |
All 6 announced prefixes of AS209360 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS209360 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 AS209360 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/209360Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/209360" | jq