AS44341 SEVONLINE Nikita Sergienko
🇷🇺Org handle: ORG-NS573-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
5 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
🇷🇺 RURIR
RIPE NCCStatus
allocated
Allocated
2007-12-27
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 | |
| No ROA | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.8.62.0/24 | 🇷🇺 RU | RIPE | assigned |
| 46.8.206.0/24 | 🇷🇺 RU | RIPE | assigned |
| 176.96.225.0/24 | 🇷🇺 RU | RIPE | assigned |
| 176.96.239.0/24 | 🇷🇺 RU | RIPE | assigned |
All 5 announced prefixes of AS44341 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS44341 hands its own prefixes to: transit providers, or peers at an exchange.
- AS28761CrimeaCom South5
Transfer History
Registry transfers of AS44341 between organisations.
- AS44341Transfer ·
- AS44341Transfer ·
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 AS44341 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/44341Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/44341" | jq