Mio Outage History

Started Sep 02, 2026, 04:48 PM UTC· resolved Sep 08, 2026, 12:59 PM UTC

1. monitoring Sep 02, 2026, 04:48 PM UTC

   Following recent work to improve platform scalability, an additional optimization did not perform as expected and generated significantly higher traffic than anticipated. This created a processing backlog and caused some messages to be delivered late. We have increased processing capacity, are working through the backlog, and are addressing the behavior that caused the unexpected traffic. We continue to monitor the platform closely.

2. resolved Sep 08, 2026, 12:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 28, 2026, 12:47 AM UTC· resolved Aug 28, 2026, 02:34 PM UTC

1. investigating Aug 28, 2026, 12:47 AM UTC

   We are investigating elevated failures (https://admin.cloud.microsoft/?#/servicehealth/:/alerts/TM1462874) when reauthorizing and refreshing Microsoft subscriptions. The issue appears to originate from Microsoft’s backend services. There is currently no known impact to end-user performance or functionality. No customer subscriptions have been confirmed as permanently failed, and the system’s retry and fallback mechanisms are continuing to operate. No customer subscriptions were confirmed to have permanently failed as of the latest assessment. However, if the Microsoft errors persist and retry attempts are exhausted, affected subscriptions could stop receiving events until they are recreated or refreshed. What Mio is doing: Monitoring reauthorization and refresh success rates Retrying failed operations through the existing lifecycle process Tracking subscriptions that may exhaust their retry attempts Coordinating with Microsoft and providing request identifiers for investigation Preparing a bulk refresh operation after Microsoft’s service stabilizes, if required

2. resolved Aug 28, 2026, 02:34 PM UTC

   Microsoft Teams Channel Access Issue — Resolved Status: Resolved Duration: Aug 27, 2026, 3:22 PM – 11:29 PM EDT Summary Some Mio users in North America may have had trouble accessing or managing Microsoft Teams channel features, including viewing shared and private channel membership, due to an incident on Microsoft's side. This was not an issue with Mio's own systems. Resolution Microsoft has confirmed the issue is fully resolved. The root cause was a processing delay within Microsoft Teams infrastructure that caused requests to exceed their retry window, creating a backlog of failed events. Microsoft disabled the affected processing components to stop new requests from adding to the backlog, then confirmed via monitoring that the backlog had cleared. Teams channel features should now be working normally for all affected users. No action is needed on your end. We'll continue monitoring and will post again if anything resurfaces.

Read the full incident report →

Started Aug 10, 2026, 03:15 PM UTC· resolved Aug 10, 2026, 06:53 PM UTC

1. monitoring Aug 10, 2026, 03:15 PM UTC

   At approximately 9:00 AM UTC on August 10th, Mio experienced a brief service outage. Service has since been restored. We are currently processing the backlog of events in the order they occurred. As a result, end users may experience elevated message latency while the queue is worked through. No messages moving forward have been lost — this is a processing delay only. We will post another update once the event queue has been fully processed and confirm when we return to Operations Normal.

2. resolved Aug 10, 2026, 06:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 22, 2026, 04:30 PM UTC· resolved Jul 07, 2026, 04:35 PM UTC

1. investigating May 22, 2026, 04:30 PM UTC

   We are currently investigating intermittent message delivery latency affecting a subset of users across platforms. Messages are continuing to be delivered, but some may experience delays during periods of elevated traffic. Our engineering team has identified instability within an underlying queueing component that is impacting throughput during traffic spikes. We are actively implementing infrastructure changes intended to improve long-term stability and resilience. Because these changes involve core messaging infrastructure, this incident may remain open while work is completed and performance is closely monitored. In the meantime, the platform remains operational, and messages continue to process and deliver. We will continue providing updates here as progress is made. Thank you for your patience.

2. identified May 28, 2026, 06:48 PM UTC

   We want to provide an update on Mio's current latency issues. A subset of users continues to experience minimal message delivery latency across platforms. Messages are being delivered, but delays continue to occur, particularly during periods of elevated traffic. Our engineering team has identified the root cause as instability in the underlying message queueing infrastructure. Under traffic spikes, the current system is not handling throughput at the level we require for consistent, reliable delivery. We are implementing meaningful infrastructure changes, and it is actively underway. In parallel, we have deployed additional capacity to the existing system to reduce the impact while the migration is completed. This incident will remain open until the migration is complete and performance has stabilized. If you are experiencing significant disruption, please reach out to our support team directly. Thank you for your continued patience.

3. identified Jun 03, 2026, 04:48 PM UTC

   Over the past week, we have seen a significant reduction in customer-reported impact related to message delivery latency. The infrastructure changes we implemented have stabilized throughput for the majority of affected users. Our engineering team continues to work on a longer-term solution to fully address the underlying cause. We are in the process of validating these changes in our internal environment before broader deployment. We will provide a timeline for that deployment with our next update.

4. identified Jun 12, 2026, 05:33 PM UTC

   Following successful internal testing, we have deployed the first phase of our solution to address the underlying messaging infrastructure issues. Development fixes are now being rolled out across customer environments. We are closely monitoring system performance and throughput as these changes take effect, and we will provide a completion timeline in our next update.

5. monitoring Jul 06, 2026, 04:35 PM UTC

   Over the past two weeks, our engineering team has made significant progress in addressing the underlying cause of this incident. Message delivery performance has stabilized with latency returning to normal operating ranges. The infrastructure improvements we implemented have proven effective, and we have been monitoring the system closely to confirm sustained stability before closing this incident. We are satisfied that the platform is performing as expected. We recognize this incident remained open longer than we would have liked, and we appreciate your patience. If you continue to experience any delays in message delivery, please contact us.

6. resolved Jul 07, 2026, 04:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 20, 2026, 05:10 PM UTC· resolved Apr 22, 2026, 02:37 PM UTC

1. investigating Apr 20, 2026, 05:10 PM UTC

   Mio is currently investigating message latency from Microsoft to Google. We will update this incident when a root cause is identified.

2. monitoring Apr 21, 2026, 03:14 PM UTC

   Mio has fixed the issue where end user messages were delayed from Microsoft to Google. This degraded service was caused by a deployment of multiple microservices, where one service was out of sync with the others, causing delays and failures of messages. The failure prevented our retry strategy from completing, which resulted in the delays and failures. We will resolve this issue after monitoring for the next few hours.

3. resolved Apr 22, 2026, 02:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 13, 2026, 04:43 PM UTC· resolved Apr 13, 2026, 06:45 PM UTC

1. investigating Apr 13, 2026, 04:43 PM UTC

   Mio is investigating a potential issue impacting message latency. Mio will update this page over the next few hours with further details.

2. resolved Apr 13, 2026, 06:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 13, 2026, 01:47 AM UTC· resolved Mar 16, 2026, 03:44 PM UTC

1. investigating Mar 13, 2026, 01:47 AM UTC

   We are currently investigating a potential service degradation for Mio users. Initial investigations point to an issue with the Microsoft service responsible for rate limiting. We are actively investigating and will update when we know more.

2. resolved Mar 16, 2026, 03:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 09, 2026, 03:29 AM UTC· resolved Mar 11, 2026, 03:17 PM UTC

1. investigating Mar 09, 2026, 03:29 AM UTC

   We are currently investigating this issue.

2. resolved Mar 11, 2026, 03:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 17, 2026, 04:31 PM UTC· resolved Feb 19, 2026, 05:49 PM UTC

1. investigating Feb 17, 2026, 04:31 PM UTC

   Mio is currently investigating a third party end point that looks to be the root cause for message latency. We will provide more details once our investigation has completed.

2. monitoring Feb 17, 2026, 07:52 PM UTC

   We are actively monitoring a Microsoft outage that occurred early on 2/17/2025 that is impacting Microsoft Teams. "Users may experience delays and failures when sending and receiving chat messages that include inline media (images, code snippets, videos)" - This incident can be tracked under the Microsoft ticket TM1233974 (admin.microsoft.com/#/MessageCenter/:/messages/TM1233974).

3. resolved Feb 19, 2026, 05:49 PM UTC

   We have moved this to resolved, as we have seen the third party api be stable over the past few days. Mio will continue to monitor the impact of the degraded performance to make sure service is working as expected for all clients.

Read the full incident report →

Started Feb 13, 2026, 03:36 PM UTC· resolved Feb 14, 2026, 12:05 AM UTC

1. investigating Feb 13, 2026, 03:36 PM UTC

   Mio is actively investigating an issue that is impacting message delivery from Microsoft to Google, causing slowness of messages, or even failed messages. Mio will update the status as we identify, fix, and monitor the issue.

2. monitoring Feb 13, 2026, 06:52 PM UTC

   Mio has fixed the issue where end user messages were delayed or failing from Microsoft to Google. This degraded service was caused by a deployment of multiple microservices, where one service was out of sync with the others, causing delays and failures of messages. The failure prevented our retry strategy from completing, which resulted in the delays and failures. Older failures and delays should now be delivered, and new messages are being delivered as expected. We will resolve this issue after monitoring for the next few hours.

3. resolved Feb 14, 2026, 12:05 AM UTC

   This issue has now been resolved.

Read the full incident report →

Started Dec 04, 2025, 04:17 PM UTC· resolved Dec 10, 2025, 04:06 PM UTC

1. monitoring Dec 04, 2025, 04:17 PM UTC

   Mio is currently experiencing an intermittent issue that may impact an end users message delivery - the issue has been identified, fixed, and is now being monitored by our team, however we want to make sure you are aware that we were alerted of the issue by automated alerts. Mio will update this status after monitoring the fix that has already been released over the next few hours.

2. resolved Dec 10, 2025, 04:06 PM UTC

   After implementing minor changes, and monitoring the fix, we are now confident that the intermittent issue around end user message delivery has been resolved.

Read the full incident report →

Started Nov 27, 2025, 01:15 PM UTC· resolved Nov 27, 2025, 01:15 PM UTC

1. resolved Nov 27, 2025, 01:15 PM UTC

   We are aware of Mixpanel’s recent disclosure of a security incident affecting a limited number of their user accounts. Mio previously used Mixpanel as a subprocessor; however, we have confirmed that Mio was not affected by this incident. To provide full transparency: - Mio stopped sending any data to Mixpanel in March 2025, at which time we initiated a 90-day data deletion request. - The Mixpanel account that previously handled production data was fully deleted in June 2025. - Mixpanel remains listed on our website only because it is scheduled for formal removal as a subprocessor at the end of 2025. - We have not received any breach notification from Mixpanel regarding Mio data, and Mixpanel has confirmed that customers not directly contacted were not impacted. Based on the above, Mio has no evidence of any exposure of customer data related to this incident. We continue to monitor the situation and maintain ongoing diligence in our vendor-security processes. If you have any questions, please contact our support team.

Read the full incident report →

Started Nov 18, 2025, 04:30 PM UTC· resolved Nov 19, 2025, 02:54 PM UTC

1. investigating Nov 18, 2025, 04:30 PM UTC

   We are currently investigating an issue causing message delivery delays of up to five minutes across all supported platforms. This may affect users sending or receiving messages between Google Chat, Microsoft Teams, and Slack. At this time, the underlying cause has not yet been identified, and we do not have an estimated time for recovery. Our engineering team is treating this as a top priority and is actively analyzing system performance, queues, and external dependencies to isolate the source of the delays. We will provide an update as soon as more information becomes available.

2. monitoring Nov 19, 2025, 03:13 AM UTC

   We have implemented changes intended to improve system performance and reduce message delivery delays. Early results are positive, and overall latency has decreased since these updates were applied. At this time, we are closely monitoring the system to confirm stability before marking the incident as resolved. We will provide another update once we have sustained healthy performance across all affected services.

3. resolved Nov 19, 2025, 02:54 PM UTC

   System performance has returned to normal, and message delivery is now operating as expected across all platforms. Our team has been monitoring the environment and has confirmed stable performance following recent adjustments. This incident is now resolved. Thank you for your patience while we worked to restore normal service.

Read the full incident report →

Started Oct 28, 2025, 04:30 PM UTC· resolved Nov 07, 2025, 03:53 PM UTC

1. investigating Oct 28, 2025, 04:30 PM UTC

   We are currently investigating an issue affecting Mio’s ability to refresh subscriptions for secondary users on Google Workspace. This issue is caused by an ongoing service outage impacting Google’s Workspace Events API, specifically the subscription lifecycle service responsible for expiration and renewal events. As a result, some Microsoft Teams users may not receive messages sent to them by their colleagues on Google Chat. We are monitoring Google’s status updates and will restore full functionality as soon as the underlying Google service is operational. In the meantime we are manually recreating subscriptions to restore service ASAP.

2. monitoring Oct 28, 2025, 08:25 PM UTC

   Google has resolved the underlying issue with the Workspace Events lifecycle service, which was preventing Mio from refreshing subscriptions for secondary users. Mio can now successfully refresh subscriptions again. However, we are in the process of manually recreating subscriptions for all affected end users to fully restore service. During this process, some users may continue to experience limited functionality or intermittent message delivery. We’ll post another update once all subscriptions have been recreated and the service is fully restored.

3. monitoring Nov 03, 2025, 12:39 PM UTC

   We are currently experiencing a recurrence of the issue affecting Mio’s ability to refresh and maintain Google Workspace Events lifecycle subscriptions. This issue originates from a Google Workspace service outage impacting the Events API, which is required for Mio to maintain active subscriptions for Google Chat users. As a result, some users across multiple organizations may again experience issues sending messages from Google Chat to Microsoft Teams. We are monitoring Google’s status communications and will begin restoring subscriptions as soon as the affected Google service stabilizes. We understand that this is the second occurrence of this issue, and we apologize for the disruption. Our team is continuing to work with Google to identify ways to reduce customer impact if this service experiences future instability.

4. monitoring Nov 04, 2025, 08:09 PM UTC

   Google is continuing to resolve the underlying Workspace Events service outage that impacted Mio’s ability to maintain and refresh subscriptions. We are actively recreating all expired subscriptions across affected organizations. We expect all users to be fully restored and message delivery between platforms to return to normal operation by approximately 8:00 AM CDT. We appreciate your continued patience as we complete the recovery process.

5. resolved Nov 07, 2025, 03:53 PM UTC

   Google has fully resolved the Workspace Events service outage that impacted Mio’s ability to maintain and refresh subscriptions for Google Workspace users. All expired subscriptions have been successfully recreated across affected organizations, and Mio’s systems are now fully operational. Message delivery between Google Chat and Microsoft Teams has been restored to normal performance levels. We appreciate your patience and understanding throughout this incident, and we are working on additional safeguards to help reduce the impact of similar third-party service disruptions in the future.

Read the full incident report →

Started Oct 20, 2025, 11:55 AM UTC· resolved Oct 21, 2025, 11:46 AM UTC

1. investigating Oct 20, 2025, 11:55 AM UTC

   Due to the 'Operational issue - Multiple services' services issues affecting AWS we are seeing degraded performance and an increase error rate on the Mio service.

2. monitoring Oct 20, 2025, 11:47 PM UTC

   As a result of AWS us-east-1 returning to operational status we are now seeing our own services returning to normal. We will continue to monitor operations closely to confirm full stability.

3. resolved Oct 21, 2025, 11:46 AM UTC

   Following extended monitoring this incident is now considered resolved.

Read the full incident report →

Started Aug 26, 2025, 01:11 PM UTC· resolved Sep 02, 2025, 01:54 PM UTC

1. identified Aug 26, 2025, 01:11 PM UTC

   We have identified the root cause of an issue causing slow delivery of messages from Microsoft Teams to Google. Our engineering team is actively working on a fix and will deploy the solution as soon as possible. We will provide updates as progress is made.

2. identified Aug 28, 2025, 03:05 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved Sep 02, 2025, 01:54 PM UTC

   We identified a misconfiguration in Microsoft’s endpoint classification that affected Mio’s ability to maintain valid subscriptions for message delivery. Microsoft deployed a hotfix and, with additional configuration updates from Mio, full service has been restored. We are also implementing improvements to further strengthen resilience against similar issues in the future.

Read the full incident report →

Started Aug 24, 2025, 05:00 AM UTC· resolved Aug 24, 2025, 05:00 AM UTC

1. resolved Aug 25, 2025, 07:02 PM UTC

   We have identified an issue with our Google Directory Sync process that resulted in unintended deletions of Mio-provisioned Microsoft Guest Accounts. This caused service interruptions for a number of Mio organizations. We have paused the process and are deploying a fix today to prevent further impact. Restoration is underway, which will involve recreating Microsoft Guest Accounts and reinstating channel memberships. Direct Messages with the original accounts and prior file access permissions will no longer work, but history and search remain unaffected. Users will need to re-establish new DMs once guest accounts are recreated. We are working urgently to restore service and will provide updates as progress is made.

Read the full incident report →

Started Aug 13, 2025, 05:13 PM UTC· resolved Aug 13, 2025, 05:13 PM UTC

1. resolved Aug 13, 2025, 05:13 PM UTC

   Between 07:40 UTC and 15:30 UTC, the Mio platform experienced increased outbound message delivery latency. Inbound delivery was unaffected, and all outbound messages were successfully processed after temporary queuing. The issue has been resolved, and we continue to monitor closely.

Read the full incident report →

Started Apr 17, 2025, 04:22 PM UTC· resolved Apr 25, 2025, 06:21 PM UTC

1. investigating Apr 17, 2025, 04:22 PM UTC

   A Microsoft API that Mio uses to post messages from Google users into Microsoft Teams channels, DMs, and group chats is intermittently unavailable. This is resulting in a failure to deliver messages from some users in Google Chat to their cross platform colleagues in Microsoft Teams. We are working to remediate this partial outage as soon as possible and will post updates as they come. Thanks, Mio Support Team

2. investigating Apr 17, 2025, 07:22 PM UTC

   We are continuing to investigate this issue.

3. investigating Apr 17, 2025, 07:24 PM UTC

   Mio has made internal changes to improve the message delivery success rate, however, there are still some message failures. Mio is still working with Microsoft to resolve the API issues.Thank you for your patience. Thanks, Mio Support Team

4. investigating Apr 21, 2025, 11:59 AM UTC

   Following a rollback of changes by Microsoft over the weekend, all systems now appear operational. We will continue to monitor the situation throughout the day but our current delivery metrics indicate this issue is now resolved.

5. monitoring Apr 21, 2025, 01:37 PM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Apr 25, 2025, 06:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 31, 2025, 02:30 PM UTC· resolved Jan 31, 2025, 02:30 PM UTC

1. resolved Jan 31, 2025, 04:03 PM UTC

   There was a Mio service outage for approximately 45 minutes due to general infrastructure issues. Mio is now fully back up and operational. We apologize for any inconvenience during the outage and we appreciate your patience.

Read the full incident report →

Started Dec 12, 2024, 05:13 PM UTC· resolved Dec 13, 2024, 12:54 AM UTC

1. monitoring Dec 12, 2024, 05:13 PM UTC

   Mio is experiencing a temporary disruption affecting some features of our chat interoperability service. The disruption is caused by an outage of a Microsoft API: https://admin.microsoft.com/#/servicehealth/:/alerts/TM955389 Our team is actively monitoring the situation and working with Microsoft to restore full functionality as quickly as possible. What you can expect: - The outage impacts messages sent in direct messages and group chats from Microsoft Teams users to Google Chat users. - Until the API is back online Mio recommends end users move all critical conversations to channels as they are unaffected. We understand that this disruption may be inconvenient, and we sincerely apologize for any impact it may cause. We will keep you updated on the progress and notify you as soon as the issue is resolved. Thank you for your patience and understanding. Sincerely, The Mio Support Team

2. resolved Dec 13, 2024, 12:54 AM UTC

   We're pleased to inform you that the Mio service disruption has been resolved. The Microsoft API issue causing the disruption has been resolved, and full functionality has been restored to Mio. All messages sent from a Microsoft Teams users in a direct message or a group chat to a Google Chat user will be successfully relayed. We understand that this outage caused inconvenience, and we apologize for any impact to your work. We appreciate your patience and understanding while we worked to resolve the issue. We value your business and are committed to providing you with a reliable and seamless experience. If you have any questions or concerns, please don't hesitate to contact our support team at [email protected]. Sincerely, The Mio Support Team

Read the full incident report →