Mio experienced a minor incident on July 23, 2026 affecting API, lasting 6d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- 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.
- 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.
- resolved Jul 30, 2026, 03:14 PM UTC
This incident has been resolved.