AS35067 PROKK-AS ProKK SE
🇺🇦Org handle: ORG-PRKK1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 195.16.76.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 2001:678:5f0::/48 | 🇺🇦 UA | RIPENCC | assigned |
All 1 announced prefix of AS35067 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS35067 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35297DATALINE1
Downstreams (1)
Networks whose own prefixes AS35067 passes on: usually its customers.
- AS58098SZATMARNET Bt5
Other adjacent networks (1)
Adjacent to AS35067 in the transit part of AS paths: peers, providers or customers.
- AS3255UARNET EKSINTECH5
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 AS35067 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/35067Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35067" | jq