Mio Incident History

1. monitoringSep 2 · 16:48 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.

Reported by Mio on their status page.

1. resolvedAug 28 · 14:34 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.

Reported by Mio on their status page.

1. resolvedAug 13 · 17:05 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.

Reported by Mio on their status page.

1. resolvedAug 10 · 18:53 UTC

   This incident has been resolved.

Reported by Mio on their status page.