Mio incident

Experiencing Message Latency Microsoft to Google

Minor Resolved View vendor source →

Mio experienced a minor incident on February 13, 2026 affecting API, lasting 8h 29m. The incident has been resolved; the full update timeline is below.

Started
Feb 13, 2026, 03:36 PM UTC
Resolved
Feb 14, 2026, 12:05 AM UTC
Duration
8h 29m
Detected by Pingoru
Feb 13, 2026, 03:36 PM UTC

Affected components

API

Update timeline

  1. investigating Feb 13, 2026, 03:36 PM UTC

    Mio is actively investigating an issue that is impacting message delivery from Microsoft to Google, causing slowness of messages, or even failed messages. Mio will update the status as we identify, fix, and monitor the issue.

  2. monitoring Feb 13, 2026, 06:52 PM UTC

    Mio has fixed the issue where end user messages were delayed or failing from Microsoft to Google. This degraded service was caused by a deployment of multiple microservices, where one service was out of sync with the others, causing delays and failures of messages. The failure prevented our retry strategy from completing, which resulted in the delays and failures. Older failures and delays should now be delivered, and new messages are being delivered as expected. We will resolve this issue after monitoring for the next few hours.

  3. resolved Feb 14, 2026, 12:05 AM UTC

    This issue has now been resolved.