Is Mio down?

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.

This incident has been resolved.

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

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.

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.

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.

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.

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.

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.

This incident has been resolved.

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

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.

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.

This incident has been resolved.