AS214719 GBN LLC DZHIBIEN HOST
🇷🇺Org handle: ORG-LDH2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,792
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)3×10²⁶
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | - | 2026-10-11 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.8.124.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 45.8.124.0/24 | 🇪🇪 EE | RIPE | assigned |
| 45.8.126.0/24 | 🇪🇪 EE | RIPE | assigned |
| 192.124.216.0/24 | 🇨🇿 CZ | RIPENCC | assigned |
| 2a0e:7200::/29 | 🇷🇺 RU | RIPENCC | allocated |
| 2a0e:7200::/40 | 🇪🇪 EE | RIPE | assigned |
All 4 announced prefixes of AS214719 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS214719 hands its own prefixes to: transit providers, or peers at an exchange.
- AS8728INFONET4
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 AS214719 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/214719Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/214719" | jq