AS39399 FENIXVT-AS Private Enterprise Firma Fenix VT
🇺🇦Org handle: ORG-PFV1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
5 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)6,656
Announced (BGP)6,144
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | 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 |
Allocated Prefixes
(RIR)7Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.199.194.0/24 | 🇺🇦 UA | RIPENCC | assigned |
| 91.215.24.0/22 | 🇺🇦 UA | RIPENCC | assigned |
| 91.224.84.0/23 | 🇺🇦 UA | RIPENCC | assigned |
| 91.224.84.0/24 | 🇺🇦 UA | RIPENCC | assigned |
| 178.215.176.0/20 | 🇺🇦 UA | RIPENCC | assigned |
| 195.182.192.0/23 | 🇺🇦 UA | RIPENCC | assigned |
| 2001:67c:2280::/48 | 🇺🇦 UA | RIPENCC | assigned |
All 6 announced prefixes of AS39399 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS39399 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS39399 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/39399Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39399" | jq