AS31173 Mediana-PLUS-AS "MEDIANA-TREID" PP
🇺🇦Org handle: ORG-PA1723-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.25.176.0/23 | 🇺🇦 UA | RIPENCC | assigned |
| 2001:678:11f8::/48 | 🇺🇦 UA | RIPENCC | assigned |
All 4 announced prefixes of AS31173 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS31173 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16066TEST UA T.E.S.T4
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 AS31173 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/31173Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/31173" | jq