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 11, 2026, 03:35 PM UTC· resolved Aug 13, 2026, 05:05 PM UTC

1. identified Aug 11, 2026, 03:35 PM UTC

   What happened On both August 10 and August 11, we experienced intermittent delays in message delivery during early morning hours. Our engineering team identified the issue quickly on each occasion and took immediate action to restore normal processing. Impact During these windows, some messages were delivered later than usual. We are not aware of any messages being lost, delivery was delayed, not dropped. Current status Our team continues to monitor the platform closely and is actively working on a permanent fix to prevent this issue from recurring. We are treating this as a high priority. What we're doing We've taken immediate steps to stabilize the system and are evaluating longer-term infrastructure improvements to strengthen reliability going forward. We'll share an update once that work is complete. We apologize for any inconvenience this may have caused and appreciate your patience. If you have questions about how this may have affected your account specifically, please reach out to your support contact.

2. monitoring Aug 11, 2026, 06:48 PM UTC

   The affected systems are now stable. We have increased the capacity of the underlying infrastructure to give our application more headroom under load. Since making these changes, we have not seen the issue recur, and we are actively monitoring the platform to confirm stability. We have not yet identified a definitive root cause. Our team continues to investigate in parallel with this monitoring period.

3. monitoring Aug 12, 2026, 06:04 PM UTC

   Update Since our last update, we've made several changes to strengthen the platform, including increasing our processing capacity and shifting some services onto an alternate messaging system to reduce load on the affected infrastructure. Last night, our platform handled a comparable traffic spike to the one that previously triggered latency, and we did not see a recurrence. This is an encouraging sign that these changes are helping. This is not a confirmed resolution and we have not yet identified a definitive root cause. We remain in an active monitoring period and will continue watching closely before we consider this fully resolved. What we're doing We're continuing to monitor platform performance closely while our investigation into the underlying cause continues in parallel. We'll provide a further update once we've either confirmed the issue is fully resolved or have more to share.

4. resolved Aug 13, 2026, 05:05 PM UTC

   Mio has been experiencing strong growth across our customer base, and that growth has been pushing the limits of a subscription model we'd relied on with one of our upstream integration partners. To keep pace, we shifted to a new subscription approach designed to support significantly higher volume going forward. That transition increased the amount of data flowing through our application, and during periods of peak traffic, that data flow exceeded the capacity of our infrastructure at the time. This caused messages to back up and be delivered later than expected. To resolve this, we increased the processing capacity of our infrastructure and migrated the affected services to a more scalable messaging architecture built to handle this higher volume as we continue to grow. Since making these changes, the platform has successfully handled traffic spikes at the same scale that previously caused delays, with no recurrence. We're closing this incident as resolved. Scaling to support our growing customer base is a good problem to have, but we understand these delays affected your operations. We appreciate your patience while we worked through it, and please reach out to your support contact with any questions.

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 Jul 23, 2026, 04:09 PM UTC· resolved Jul 30, 2026, 03:14 PM UTC

1. investigating Jul 23, 2026, 04:09 PM UTC

   Users are experiencing elevated message delivery latency on the messaging platform. Root cause is still under investigation.

2. identified Jul 24, 2026, 04:47 PM UTC

   We have identified the root cause of the issue causing elevated response times and delays across our messaging services for Microsoft users. Core services remain operational, but message delivery may be delayed while these events fail to process as expected. Our engineering team is actively working with Microsoft toward resolution. We will provide our next update as soon as new information becomes available.

3. monitoring Jul 27, 2026, 02:51 PM UTC

   The messaging latency was caused by a degraded Microsoft endpoint for managing lifecycle subscriptions. Microsoft has fixed the endpoint, and message delivery has returned to normal latency. No action required on our side.

4. resolved Jul 30, 2026, 03:14 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 26, 2026, 12:04 AM UTC· resolved May 15, 2026, 05:17 PM UTC

1. investigating Apr 26, 2026, 12:04 AM UTC

   We're currently seeing elevated latency in message delivery and are actively investigating. A subset of messages is taking longer than usual to send. Messages are still being delivered, they're just delayed. We've identified the root cause as upstream rate limiting on a Microsoft API we depend on for keeping subscriptions current. We're working directly with Microsoft to resolve it and have implemented mitigations on our side to reduce impact in the meantime. No action is required. Your messages are queued and will be delivered. We'll continue posting updates here until the issue is fully resolved. We'll share an update when there is a development. Thanks for your patience.

2. monitoring Apr 27, 2026, 07:41 PM UTC

   We've implemented a fix for the elevated message delivery latency and are now monitoring the situation. Message delivery times have returned to normal levels. Any messages that were queued during the incident have been delivered. We deployed changes on our end to make the application more resilient to upstream rate limiting, so subscription refreshes can continue smoothly even under pressure. We'll continue monitoring closely over the next several hours to confirm stability before marking this fully resolved. If you notice any lingering issues, please reach out to support. Thanks for your patience while we worked through this.

3. monitoring Apr 27, 2026, 07:43 PM UTC

   We are continuing to monitor for any further issues.

4. investigating Apr 28, 2026, 04:23 PM UTC

   We're moving this incident back to investigating. The fix we deployed earlier has reduced the impact, but users are still experiencing elevated message latency, and we want to be transparent that this is not yet resolved. Message delivery is still slower than normal for a portion of users. Messages continue to be delivered, but with delays. We're pursuing two parallel paths. Internally, our team is evaluating additional changes to further reduce our reliance on the affected upstream behavior. Externally, we're working with Microsoft to raise the rate limits that are contributing to the issue. No action is required on your end. We'll continue posting updates here as we make progress. Thanks for your continued patience.

5. identified May 12, 2026, 03:16 PM UTC

   Since our last update, the upstream issue related to Microsoft API rate limiting has been identified and addressed. As traffic has normalized, this has exposed a separate internal issue that is contributing to continued message latency. We have identified the cause and are actively working on a fix. Messages are still being delivered, but some delays may persist while we complete this work. No action is required on your end. We’ll continue to provide updates as we make progress toward full resolution. Thank you for your continued patience.

6. resolved May 15, 2026, 05:17 PM UTC

   We have implemented additional changes to address the internal issue contributing to message delivery latency. System performance has stabilized, and message delivery is now operating within normal expected ranges across all platforms. Over the course of this incident, we identified and mitigated both upstream rate limiting constraints and internal factors that were impacting performance. We have also introduced improvements to increase resilience against similar conditions in the future. Our team has been monitoring the system closely and can confirm that service has remained stable. This incident is now resolved. Thank you for your patience while we worked through this.

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 Mar 05, 2026, 04:55 PM UTC· resolved Mar 06, 2026, 07:18 PM UTC

1. investigating Mar 05, 2026, 04:55 PM UTC

   Mio is currently investigating a potential service degradation related to Microsoft subscriptions endpoint.

2. identified Mar 05, 2026, 09:09 PM UTC

   We have identified the issue and are in the process of recovering.

3. resolved Mar 06, 2026, 07:18 PM UTC

   After monitoring Microsoft's services, and providing details to them about the recent issues with service, we are moving this investigation to resolved. We will continue to work closely with Microsoft when required.

Read the full incident report →

Started Feb 26, 2026, 01:25 PM UTC· resolved Feb 27, 2026, 04:04 PM UTC

1. investigating Feb 26, 2026, 01:25 PM UTC

   Mio is currently investigating a potential service degradation related to Microsoft subscriptions endpoint.

2. monitoring Feb 26, 2026, 04:26 PM UTC

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

3. resolved Feb 27, 2026, 04:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2026, 05:18 PM UTC· resolved Feb 25, 2026, 03:56 PM UTC

1. investigating Feb 20, 2026, 05:18 PM UTC

   Microsoft’s service responsible for delivering message event data to Mio is currently experiencing delays of up to one hour. Mio is actively working with Microsoft to investigate and resolve the issue as quickly as possible.

2. resolved Feb 25, 2026, 03:56 PM UTC

   After monitoring Microsoft's services, and providing details to them about the recent issues with service, we are moving this investigation to resolved. We will continue to work closely with Microsoft when required.

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 22, 2025, 05:27 PM UTC· resolved Dec 22, 2025, 11:36 PM UTC

1. investigating Dec 22, 2025, 05:27 PM UTC

   Mio is currently investigating message latency being experienced by some organizations from Google Chat to Microsoft Teams. We've identified that this began within the last 2 hours(10:30am Eastern). Mio will update this page over the next hour with further details.

2. investigating Dec 22, 2025, 09:23 PM UTC

   Mio has identified and resolved the issue that caused message latency from Google to Microsoft. If you feel like you are still experiencing an issue, please submit a ticket to the help desk for our support engineers to investigate. Thank you.

3. resolved Dec 22, 2025, 11:36 PM UTC

   This incident has 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 Oct 03, 2025, 02:26 PM UTC· resolved Oct 03, 2025, 04:58 PM UTC

1. investigating Oct 03, 2025, 02:26 PM UTC

   We are currently investigating an issue causing slow message delivery for some Mio users. Our engineering team is actively working to identify the root cause and restore normal performance. We will provide updates here as soon as more information becomes available.

2. investigating Oct 03, 2025, 02:26 PM UTC

   We are continuing to investigate this issue.

3. resolved Oct 03, 2025, 04:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 01, 2025, 02:10 PM UTC· resolved Oct 01, 2025, 09:20 PM UTC

1. investigating Oct 01, 2025, 02:10 PM UTC

   We are currently investigating an issue causing slow message delivery for some Mio users. Our engineering team is actively working to identify the root cause and restore normal performance. We will provide updates here as soon as more information becomes available.

2. resolved Oct 01, 2025, 09:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2025, 02:25 PM UTC· resolved Sep 16, 2025, 06:25 PM UTC

1. resolved Sep 16, 2025, 02:30 PM UTC

   From 9:25 AM CT to 1:25 PM CT today, Mio experienced message delivery delays of up to one hour. The issue has been fully resolved, and messages are now sending and receiving without delay. We apologize for the inconvenience and thank you for your understanding.

Read the full incident report →