AS48979 UZINFOCOM DAVLAT AXBOROT TIZIMLARINI YARATISH VA QO`LLAB QUVATLASH BO`YICHA YAGONA INTEGRATOR-UZINFOCOM LLC
🇺🇿Org handle: ORG-USUE1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 | |
| No ROA | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)7Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.212.89.0/24 | 🇺🇿 UZ | RIPENCC | assigned |
| 185.0.36.0/24 | 🇺🇿 UZ | RIPENCC | assigned |
| 185.8.212.0/22 | 🇺🇿 UZ | RIPENCC | allocated |
| 185.8.212.0/24 | 🇺🇿 UZ | RIPE | assigned |
| 185.8.213.0/24 | 🇺🇿 UZ | RIPE | assigned |
| 2001:7f8:14f::/48 | 🇺🇿 UZ | RIPENCC | assigned |
| 2a03:3240::/32 | 🇺🇿 UZ | RIPENCC | allocated |
All 3 announced prefixes of AS48979 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS48979 hands its own prefixes to: transit providers, or peers at an exchange.
- AS34250UZTELECOM "Uzbektelekom" Joint Stock Company3
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 AS48979 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/48979Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48979" | jq