AS38934 PRIDENET-AS Pride LLC
🇷🇺Org handle: ORG-PLC1-RIPE
Nizhnevartovsk, Russia
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)20,480
Announced (BGP)13,312
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)19Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.158.96.0/19 | 🇷🇺 RU | RIPENCC | allocated |
| 5.158.96.0/22 | 🇷🇺 RU | RIPE | assigned |
| 5.158.100.0/22 | 🇷🇺 RU | RIPE | assigned |
| 5.158.104.0/22 | 🇷🇺 RU | RIPE | assigned |
| 5.158.108.0/22 | 🇷🇺 RU | RIPE | assigned |
| 5.158.112.0/24 | 🇷🇺 RU | RIPE | assigned |
| 5.158.113.0/24 | 🇷🇺 RU | RIPE | assigned |
| 5.158.114.0/23 | 🇷🇺 RU | RIPE | assigned |
| 5.158.118.0/24 | 🇷🇺 RU | RIPE | assigned |
| 5.158.119.0/24 | 🇷🇺 RU | RIPE | assigned |
1-10 of 19
1 / 2
All 3 announced prefixes of AS38934 →
BGP Neighbours
(seen in AS paths)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 AS38934 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/38934Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/38934" | jq