AS50251 NURTELECOM-AS2 NUR Telecom LLC
🇰🇬Org handle: ORG-NTL33-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)3.1×10²⁹
Announced (BGP)3.1×10²⁹
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.106.48.0/22 | 🇰🇬 KG | RIPENCC | assigned |
| 2a0b:d7c4::/30 | 🇰🇬 KG | RIPE | assigned |
All 6 announced prefixes of AS50251 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS50251 hands its own prefixes to: transit providers, or peers at an exchange.
- AS47237NURTELECOM RIPE NUR Telecom6
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 AS50251 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/50251Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50251" | jq