Mio experienced a minor incident on April 26, 2026 affecting API, lasting 19d 17h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- 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.
- monitoring Apr 27, 2026, 07:43 PM UTC
We are continuing to monitor for any further issues.
- 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.
- 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.
- 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.