Autonomous system
AS48176 OOOSET-AS MTS PJSC
Unclassified RIPE NSP
Summary
MTS PJSC
mobile isp backbone russia
The AS handle OOOSET-AS is held by MTS PJSC.
What it's used for
- The address space carries MTS backbone and access traffic, evidenced by netnames
RU-MTUandOOOSET-NETand reverse DNS entries pointing tozelenaya.netandstv.zelenaya.net. - The AS announces 34,560 IPv4 addresses across 27 prefixes and 1 IPv6 prefix, with 7 observed neighbours, indicating a large-scale access and backbone network rather than a pure transit provider.
- Traffic from this AS consists of mobile subscriber eyeballs, fixed-line broadband users, and internal MTS infrastructure endpoints, consistent with MTS's role as a major Russian telecommunications operator.
Notable
- Registrants align with the announcer, listing
MTS backbone NOC,MTS PJSC, andLLC Set Main Operating Centerfor the majority of prefixes. - The address inventory is finely subdivided into numerous /21, /22, and /24 blocks, reflecting site-by-site segmentation typical of a large corporate and carrier estate.
- The presence of
LLC Set Main Operating Centerregistrants on some prefixes indicates historical or operational ties to the LLC SET entity, which operates under the MTS umbrella.
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.
Transit providers
1 upstream, 6 downstream and 9 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS8359 | MTS PJSC | 1,900 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-01, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 27 prefixes · 34.56K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 28 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS48176- Registry name
- OOOSET-AS
- Registrant
- MTU-NOC
- Abuse contact
- abuse@mtu.ru
- Registered
- 2008-10-22
- Last changed
- 2026-01-22
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- OOO SET
- Also known as
- LLC SET
- Network type
- NSP
- Scope
- Europe
- Traffic ratio
- Balanced
- Peering policy
- Selective
- IRR as-set
RIPE::AS-OOO-NET RIPE::AS-OOO-NET-V6- Website
- http://www.zelenaya.net
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, 33 with no ROA
- ROAs
- 0 authorising AS48176
- ASPA
- no ASPA record
- IRR
- 100% registered · 33 of 33 announcements
- Route objects
- 27 naming AS48176
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: 447 networks and 1,843 prefixes, as published 2026-11-02. 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