AS24936 RIM2000M-AS Plusinfo OOO
π·πΊOrg handle: ORG-RMl1-RIPE
2, Odesskaya str.,
RIPE NCCallocated
Announced Prefixes (BGP)
17total
17 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)4,928
Announced (BGP)7,680
IPv6 Addresses
Allocated (RIR)1.5Γ10Β²βΉ
Announced (BGP)0
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
5
Country
π·πΊ RURIR
RIPE NCCStatus
allocated
Allocated
2002-05-30
Announced Prefixes
(BGP)17|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
1-10 of 17
1 / 2
Allocated Prefixes
(RIR)11Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.173.30.0/23 | πΊπΈ US | RIPENCC | assigned |
| 83.166.224.0/23 | π·πΊ RU | RIPENCC | allocated |
| 83.166.224.128/26 | π·πΊ RU | RIPE | assigned |
| 83.166.226.0/24 | π·πΊ RU | RIPENCC | allocated |
| 83.166.228.0/22 | π·πΊ RU | RIPENCC | allocated |
| 83.166.240.0/22 | π·πΊ RU | RIPENCC | allocated |
| 217.150.192.0/23 | π·πΊ RU | RIPENCC | allocated |
| 217.150.198.0/23 | π·πΊ RU | RIPENCC | allocated |
| 217.150.202.0/23 | π·πΊ RU | RIPENCC | allocated |
| 2a00:b1c0::/32 | π·πΊ RU | RIPENCC | allocated |
1-10 of 11
1 / 2
All 17 announced prefixes of AS24936 β
BGP Neighbours
(seen in AS paths)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 AS24936 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/24936Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/24936" | jq