Mio Outage History

Mio degraded · 1 active incident View live status →

Mio had 15 outages in the last 2 years totaling 1322h 22m of downtime — averaging 0.6 incidents per month.

There were 15 Mio outages since August 13, 2025 totaling 1322h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://mio.statuspage.io

Notice April 20, 2026

Investigation - Message latency from Microsoft to Google

Detected by Pingoru
Apr 20, 2026, 05:10 PM UTC
Resolved
Apr 22, 2026, 02:37 PM UTC
Duration
1d 21h
Timeline · 3 updates
  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 →

Notice April 13, 2026

Investigation - Message Latency

Detected by Pingoru
Apr 13, 2026, 04:43 PM UTC
Resolved
Apr 13, 2026, 06:45 PM UTC
Duration
2h 1m
Timeline · 2 updates
  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 →

Notice March 13, 2026

Potential Mio Service Degradation

Detected by Pingoru
Mar 13, 2026, 01:47 AM UTC
Resolved
Mar 16, 2026, 03:44 PM UTC
Duration
3d 13h
Timeline · 2 updates
  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 →

Minor February 17, 2026

Third Party Endpoint Causing Message Latency

Detected by Pingoru
Feb 17, 2026, 04:31 PM UTC
Resolved
Feb 19, 2026, 05:49 PM UTC
Duration
2d 1h
Affected: API
Timeline · 3 updates
  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 →

Minor February 13, 2026

Experiencing Message Latency Microsoft to Google

Detected by Pingoru
Feb 13, 2026, 03:36 PM UTC
Resolved
Feb 14, 2026, 12:05 AM UTC
Duration
8h 29m
Affected: API
Timeline · 3 updates
  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 →

Minor December 4, 2025

Intermittent Message Failure Update

Detected by Pingoru
Dec 04, 2025, 04:17 PM UTC
Resolved
Dec 10, 2025, 04:06 PM UTC
Duration
5d 23h
Affected: API
Timeline · 2 updates
  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 →

Minor November 18, 2025

System Wide Message Delivery Delays

Detected by Pingoru
Nov 18, 2025, 04:30 PM UTC
Resolved
Nov 19, 2025, 02:54 PM UTC
Duration
22h 23m
Affected: API
Timeline · 3 updates
  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 →

Minor October 20, 2025

Degraded Performance due to AWS issue in the US-East-1 region

Detected by Pingoru
Oct 20, 2025, 11:55 AM UTC
Resolved
Oct 21, 2025, 11:46 AM UTC
Duration
23h 51m
Affected: APIManagement Portal
Timeline · 3 updates
  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 →

Minor August 26, 2025

Slow message delivery from Microsoft Teams to Google

Detected by Pingoru
Aug 26, 2025, 01:11 PM UTC
Resolved
Sep 02, 2025, 01:54 PM UTC
Duration
7d
Affected: API
Timeline · 3 updates
  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 →

Notice August 25, 2025

Directory Sync Issues for Organizations that use Google Groups

Detected by Pingoru
Aug 25, 2025, 07:02 PM UTC
Resolved
Aug 24, 2025, 05:00 AM UTC
Duration
Timeline · 1 update
  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 →

Notice August 13, 2025

Outbound Message Latency

Detected by Pingoru
Aug 13, 2025, 05:13 PM UTC
Resolved
Aug 13, 2025, 05:13 PM UTC
Duration
Affected: APIManagement Portal
Timeline · 1 update
  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 →