AS59585 NETRIDER-UA-as PE Vinokurov Anton Vladyslavovych
🇺🇦Org handle: ORG-PVAV1-RIPE
-----BEGIN TOKEN-----75b890ea79427d1ac65928e4fc01b00b9b417e56a4a84a2e746830b259d07adafe3cd2ab4f1e72427d7306f9ecad963f34c2e96aa634216850768a669bf77605-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.239.74.0/24 | 🇺🇦 UA | RIPENCC | assigned |
All 1 announced prefix of AS59585 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS59585 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35680VOLIA Cable1
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 AS59585 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/59585Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/59585" | jq