Mio Outage History

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 24, 2025, 05:00 AM 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, 07:40 AM UTC· resolved Aug 13, 2025, 03:30 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, 03:15 PM UTC

1. resolved Jan 31, 2025, 02:30 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 →