Mio incident

Investigation - Message latency from Microsoft to Google

Resolved after 1 day 21 hours, on April 20, 2026.

monitoring Apr 21, 2026, 03:14 PM UTC

Mio has fixed the issue where end user messages were delayed 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. We will resolve this issue after monitoring for the next few hours.

Started
Apr 20, 2026, 05:10 PM UTC
Resolved
Apr 22, 2026, 02:37 PM UTC
Duration
1d 21h
Detected by Pingoru
Apr 20, 2026, 05:10 PM UTC

Update timeline

  1. investigating Apr 20, 2026, 05:10 PM UTC

    Mio is currently investigating message latency from Microsoft to Google. We will update this incident when a root cause is identified.

  2. monitoring Apr 21, 2026, 03:14 PM UTC

    Mio has fixed the issue where end user messages were delayed 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. We will resolve this issue after monitoring for the next few hours.

  3. resolved Apr 22, 2026, 02:37 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.

Add your stack →