AS8323 CYFRONET-AS2 Academic Computer Centre CYFRONET AGH
🇵🇱Org handle: ORG-ACCC1-RIPE
Metropolitan Area Network Autonomous System
RIPE NCCallocated
Announced Prefixes (BGP)
7total
5 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)8,704
Announced (BGP)57,856
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)7.1×10²⁹
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.193.64.0/19 | 🇵🇱 PL | RIPENCC | allocated |
| 194.8.45.0/24 | 🇵🇱 PL | RIPENCC | assigned |
| 194.8.46.0/24 | 🇵🇱 PL | RIPENCC | assigned |
| 2001:6d8::/29 | 🇵🇱 PL | RIPENCC | allocated |
All 7 announced prefixes of AS8323 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS8323 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (6)
Networks whose own prefixes AS8323 passes on: usually its customers.
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 AS8323 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/8323Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8323" | jq