AS200897 jormungand JORMUNGAND LLC
🇷🇺Org handle: ORG-JL170-RIPE
-----BEGIN TOKEN-----357cde68b1b303031ca296d3e56c6f262a6d6182e59d371198c795e0e8d36ff32c15044f1c202ba535234172726e0dde1e0369da9e4bc6e0790346a580cd0814-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.233.114.0/24 | 🇷🇺 RU | RIPE | assigned |
| 193.233.115.0/24 | 🇷🇺 RU | RIPE | assigned |
All 2 announced prefixes of AS200897 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200897 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS2
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 AS200897 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/200897Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200897" | jq