Mio Outage History

Mio degraded · 1 active incident View live status →

There were 6 Mio outages since February 13, 2026 totaling 250h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://mio.statuspage.io

Notice April 20, 2026

Investigation - Message latency from Microsoft to Google

Detected by Pingoru
Apr 20, 2026, 05:10 PM UTC
Resolved
Apr 22, 2026, 02:37 PM UTC
Duration
1d 21h
Timeline · 3 updates
  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.

Read the full incident report →

Notice April 13, 2026

Investigation - Message Latency

Detected by Pingoru
Apr 13, 2026, 04:43 PM UTC
Resolved
Apr 13, 2026, 06:45 PM UTC
Duration
2h 1m
Timeline · 2 updates
  1. investigating Apr 13, 2026, 04:43 PM UTC

    Mio is investigating a potential issue impacting message latency. Mio will update this page over the next few hours with further details.

  2. resolved Apr 13, 2026, 06:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 13, 2026

Potential Mio Service Degradation

Detected by Pingoru
Mar 13, 2026, 01:47 AM UTC
Resolved
Mar 16, 2026, 03:44 PM UTC
Duration
3d 13h
Timeline · 2 updates
  1. investigating Mar 13, 2026, 01:47 AM UTC

    We are currently investigating a potential service degradation for Mio users. Initial investigations point to an issue with the Microsoft service responsible for rate limiting. We are actively investigating and will update when we know more.

  2. resolved Mar 16, 2026, 03:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 17, 2026

Third Party Endpoint Causing Message Latency

Detected by Pingoru
Feb 17, 2026, 04:31 PM UTC
Resolved
Feb 19, 2026, 05:49 PM UTC
Duration
2d 1h
Affected: API
Timeline · 3 updates
  1. investigating Feb 17, 2026, 04:31 PM UTC

    Mio is currently investigating a third party end point that looks to be the root cause for message latency. We will provide more details once our investigation has completed.

  2. monitoring Feb 17, 2026, 07:52 PM UTC

    We are actively monitoring a Microsoft outage that occurred early on 2/17/2025 that is impacting Microsoft Teams. "Users may experience delays and failures when sending and receiving chat messages that include inline media (images, code snippets, videos)" - This incident can be tracked under the Microsoft ticket TM1233974 (admin.microsoft.com/#/MessageCenter/:/messages/TM1233974).

  3. resolved Feb 19, 2026, 05:49 PM UTC

    We have moved this to resolved, as we have seen the third party api be stable over the past few days. Mio will continue to monitor the impact of the degraded performance to make sure service is working as expected for all clients.

Read the full incident report →

Minor February 13, 2026

Experiencing Message Latency Microsoft to Google

Detected by Pingoru
Feb 13, 2026, 03:36 PM UTC
Resolved
Feb 14, 2026, 12:05 AM UTC
Duration
8h 29m
Affected: API
Timeline · 3 updates
  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.

Read the full incident report →

Looking to track Mio downtime and outages?

Pingoru polls Mio's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Mio reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Mio alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Mio for free

5 free monitors · No credit card required