Autonomous system
AS34121 RUSAL-AS
Unclassified APNIC Enterprise
Summary
Rusal
business corporate aluminum russia
The AS handle RUSAL-AS is operated by Rusal Management JSC.
What it's used for
- The address space carries corporate infrastructure for the aluminum producer, evidenced by the netname
RUSALand registrantRUSAL MANAGEMENT JSC; RUSAL HQ NOC. - The network announces 1024 IPv4 addresses and 1 IPv6 prefix, with only 2 observed neighbours, indicating a small internal corporate estate rather than a transit or access provider.
Notable
- The registrant
RUSAL MANAGEMENT JSCaligns directly with the AS holder and the netnameRUSAL. - Rusal is a major global aluminum producer, and this AS represents its headquarters network operations.
- The inventory consists of a single /22 IPv4 block and a /48 IPv6 block, reflecting a compact, self-contained corporate network.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-26, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 1.02K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 2 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS34121- Registry name
- RUSAL-AS
- Registrant
- RUSAL MANAGEMENT JSC
- Abuse contact
- noc@rusal.com
- Registered
- 2004-10-28
- Last changed
- 2025-04-09
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- RUSAL MANAGEMENT
- Network type
- Enterprise
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
AS34121- Website
- https://www.rusal.com
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 2 valid, 0 with no ROA
- ROAs
- 2 authorising AS34121
- ASPA
- 2 declared providers
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 2 naming AS34121
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 445 networks and 1,817 prefixes, as published 2026-10-27. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere