Mio incident

Third Party Endpoint Causing Message Latency

Minor Resolved View vendor source →
Started
Feb 17, 2026, 04:31 PM UTC
Resolved
Feb 19, 2026, 05:49 PM UTC
Duration
2d 1h
Detected by Pingoru
Feb 17, 2026, 04:31 PM UTC

Affected components

API

Update timeline

  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.

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