Mixmax incident
Mixmax Paid Features Were Temporarily Unavailable
Mixmax experienced a major incident on June 29, 2026 affecting Sending emails in Gmail/Inbox and Web app and 1 more component, lasting 2h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 29, 2026, 01:57 PM UTC
Some users are experiencing issues getting access to the features they are subscribed for -- their accounts behaving as free user accounts. We have identified the cause and we're delivering a fix.
- identified Jun 29, 2026, 02:02 PM UTC
The fix has been delivered and the system is recovering. We're continuing active monitoring of the problem.
- identified Jun 29, 2026, 02:27 PM UTC
The applied fix was not effective. We're continuing to research the problem.
- monitoring Jun 29, 2026, 03:11 PM UTC
A new fix is improving the situation. We're continuing to actively monitor the issue.
- monitoring Jun 29, 2026, 04:04 PM UTC
System is back to normal operation.
- resolved Jun 29, 2026, 04:51 PM UTC
This incident has been resolved.
- postmortem Jun 30, 2026, 10:35 PM UTC
**Post-Incident Update: Mixmax Paid Features Were Temporarily Unavailable \(June 27–29, 2026\)** **What happened** From June 27 to June 29, 2026, some customers were unable to access certain paid features. This included creating and activating sequences, using Meeting Copilot for specific meetings, and using other features that require a paid plan. **Root cause** Our system that verifies account access to paid features became overwhelmed. As a result, some paid accounts were temporarily classified as free accounts, blocking access to paid features. **How we resolved it** We addressed the issue by increasing the capacity of the affected system and alleviating the extra load that was contributing to the problem. All affected features are now functioning normally. **What we’re doing to prevent this from happening again** We have reviewed the incident and are making the following improvements: 1. Increasing system capacity to accommodate higher demand. 2. Enhancing system efficiency by streamlining unnecessary checks. 3. Upgrading our monitoring systems to detect issues more quickly. 4. Implementing stronger safeguards to prevent similar problems in the future. We sincerely apologize for the disruption this has caused and appreciate your patience while we resolve it. If you are still experiencing any issues related to this incident, please reach out to our support team via [[email protected]](mailto:[email protected]).