AS219123 MorniNetwork Oleg Mironov
🇷🇺Org handle: ORG-OA1477-RIPE
-----BEGIN TOKEN-----8acb629cf7aba1ef16dbd394948b77fd252c75fbe7cd6ce95e8c2ba5c1e02cb1aa6d73360b4b22b44d3317f4cefd46f268a80baf643991fc86e3e859dbab8646-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
3total
0 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)3.6×10²⁴
Routing hygiene
Score 3/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
3
diversity 67/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 3 announced prefixes, updated daily (2026-10-22). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARIN | 2026-10-23 | |
| Valid | ARIN | 2026-10-23 | |
| Valid | RIPE | 2026-10-23 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0d:d940:2018::/48 | 🇷🇺 RU | RIPE | assigned |
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 AS219123 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/219123Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/219123" | jq