AS8771 YUNET-AS YUnet International d.o.o.
🇷🇸Org handle: ORG-YI2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
11total
10 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)90,624
Announced (BGP)69,120
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)11|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
1-10 of 11
1 / 2
Allocated Prefixes
(RIR)19Prefix | Country | RIR | Status |
|---|---|---|---|
| 78.30.128.0/18 | 🇷🇸 RS | RIPENCC | allocated |
| 78.30.128.0/19 | 🇷🇸 RS | RIPE | assigned |
| 78.30.160.0/19 | 🇷🇸 RS | RIPE | assigned |
| 109.121.64.0/19 | 🇷🇸 RS | RIPENCC | allocated |
| 109.121.96.0/20 | 🇷🇸 RS | RIPENCC | allocated |
| 109.121.116.0/22 | 🇷🇸 RS | RIPENCC | allocated |
| 109.121.120.0/22 | 🇷🇸 RS | RIPENCC | allocated |
| 109.121.124.0/23 | 🇷🇸 RS | RIPENCC | allocated |
| 109.121.126.0/24 | 🇷🇸 RS | RIPENCC | allocated |
| 194.247.192.0/19 | 🇷🇸 RS | RIPENCC | allocated |
1-10 of 19
1 / 2
All 11 announced prefixes of AS8771 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS8771 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8400TELEKOM SRBIJA A.D11
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS8771 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/8771Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8771" | jq