AS207858 DMBZ-AS Dmytro Moiseiev
🇺🇦Org handle: ORG-DM202-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.28.255.0/24 | 🇺🇦 UA | RIPENCC | allocated |
| 193.29.1.0/24 | 🇺🇦 UA | RIPENCC | allocated |
| 193.29.4.0/24 | 🇺🇦 UA | RIPENCC | allocated |
| 193.29.8.0/24 | 🇺🇦 UA | RIPENCC | allocated |
| 2a0f:7a40::/29 | 🇺🇦 UA | RIPENCC | allocated |
All 5 announced prefixes of AS207858 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS207858 hands its own prefixes to: transit providers, or peers at an exchange.
- AS34056KIEVNET Kyiv Optic Networks5
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 AS207858 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/207858Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/207858" | jq