Autonomous system
AS41771 MTS-BB-OMSK
Unclassified RIPE
Summary
MTS PJSC
mobile residential access russia
The AS handle MTS-BB-OMSK is held by MTS PJSC.
What it's used for
- The address space carries subscriber traffic for the Omsk region, evidenced by reverse DNS entries such as
omsk.mts.ruandomsk.mts.mkc-omsk.ru. - The network announces 4608 IPv4 addresses across 3 prefixes with only 1 observed neighbour, a ratio that indicates an access or eyeball network rather than a transit provider.
- Traffic from this AS consists of mobile and fixed-line subscriber connections for MTS customers in Omsk, including web browsing, VoIP, and general internet access.
Notable
- All registrants for the announced prefixes are consistent with the announcer, listing MTS PJSC, MR-SIB-MTS Administration, and MR-SIB-MTS NOC.
- The address inventory is composed of three distinct IPv4 blocks: 77.87.80.0/21, 91.90.32.0/21, and 193.34.184.0/23, all located in the Russian Federation.
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, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS30922 | MTS PJSC | 176 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-31, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 4.61K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 3 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS41771- Registry name
- MTS-BB-OMSK
- Registrant
- MKC-OMSK-MNT
- Abuse contact
- abuse@mtu.ru
- Registered
- 2006-10-23
- Last changed
- 2018-09-04
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 3 with no ROA
- ROAs
- 0 authorising AS41771
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 9 naming AS41771
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,845 prefixes, as published 2026-10-31. 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