AS44597 RIPN-RU-SMR Join-stock company "Internet Exchange"MSK-IX"
🇷🇺Org handle: ORG-JCE1-RIPE
for Samara Project
RIPE NCCallocated
Announced Prefixes (BGP)
5total
3 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)2.4×10²⁴
Announced Prefixes
(BGP)5|
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 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.232.134.0/24 | 🇷🇺 RU | RIPENCC | allocated |
| 193.232.225.0/24 | 🇷🇺 RU | RIPE | assigned |
| 2a0c:a9c7:225::/48 | 🇷🇺 RU | RIPE | assigned |
All 5 announced prefixes of AS44597 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS44597 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS44597 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS44597 in the transit part of AS paths: peers, providers or customers.
- AS60764TK Telecom Samara1
Transfer History
Registry transfers of AS44597 between organisations.
- AS44597Transfer ·
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 AS44597 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/44597Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/44597" | jq