Autonomous system
AS35522 BUSINESS-CENTER_CAPITAL_AS
Unclassified RIPE
Summary
Stadion Spartak
business corporate russia
BUSINESS-CENTER_CAPITAL_AS is held by SZ Stadion Spartak LLC.
What it's used for
- The space carries corporate infrastructure for the stadium operator, evidenced by the netname
StadionSpartak-LANand the registrantSZ Stadion Spartak LLC. - The AS announces 512 IPv4 addresses and 1 IPv6 prefix, with 12 observed neighbours; this ratio suggests a business network with moderate peering rather than a transit provider.
Notable
- The registrant
SZ Stadion Spartak LLCmatches the registry holder, confirming consistent ownership of the address space. - The address inventory consists of a single IPv4 block (194.88.200.0/23) and one IPv6 prefix (2001:678:9c4::/48), indicating a compact, internally managed estate.
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
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| MSK-IX Moscow | Moscow, Russia | 195.208.209.76 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-15, 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 · 512 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS35522- Registry name
- StadionSpartak-AS
- Registrant
- SZ Stadion Spartak LLC
- Abuse contact
- nic@stadionspartak.com
- Registered
- 2022-12-20
- Last changed
- 2026-08-07
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Capital
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- https://mcenter.ru
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
- 0% valid · 0 valid, 4 with no ROA
- ROAs
- 0 authorising AS35522
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 4 naming AS35522
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: 442 networks and 1,782 prefixes, as published 2026-10-16. 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