Resolved after 3 hours 37 minutes, on August 10, 2026.
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.
Update timeline
- 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.
- resolved Aug 10, 2026, 06:53 PM UTC
This incident has been resolved.
Your product runs on more than Mio
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services