AS56603 NET-AS Aleksey Ershov
🇷🇺Org handle: ORG-AE121-RIPE
NETAS
RIPE NCCallocated
Announced Prefixes (BGP)
3total
1 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)2.4×10²⁴
Announced (BGP)2.4×10²⁴
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 195.128.133.0/24 | 🇷🇺 RU | RIPENCC | allocated |
| 2a09:6280:1::/48 | 🇷🇺 RU | RIPE | assigned |
| 2a09:6280:4::/48 | 🇷🇺 RU | RIPE | assigned |
All 3 announced prefixes of AS56603 →
BGP Neighbours
(seen in AS paths)Transfer History
Registry transfers of AS56603 between organisations.
- AS56603Transfer ·
- AS56603M&A ·
- AS56603Transfer ·
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 AS56603 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/56603Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/56603" | jq