Skip to main content
incident.io

Increased latency in Microsoft Teams

Degraded Lasted 1h 49m · started · incident.io's page

Level
confirmed
Worst impact
Degraded
Down Index
19of 100

What to do

  • Check whether your product depends on incident.io. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 49m it lasted.

    Anything that failed between 2026-08-20 14:42 UTC and 2026-08-20 16:31 UTC may need a replay.
  • Subscribe to incident.io's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=incident-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from incident.io 3

  1. identified

    We have identified increased latency in our Microsoft Teams app. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.

    provider

  2. identified

    We are continuing to see periods of increased latency with our Microsoft Teams app. All other surfaces, including the dashboard and our mobile app, remain unaffected.

    provider

  3. resolved

    Latency has now returned to normal. Between 13:00 and 15:08 UTC there were periods of increased latency from some Microsoft APIs. Messages in Microsoft Teams were delivered with increased latency. Our dashboard and mobile app were not affected.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-007e6e13aa

Is incident.io still down?

No, this incident was resolved 2026-08-20 16:31 UTC. For incident.io's live state, see https://down.guide/incident-io.

How long did it last?

1h 49m, from 2026-08-20 14:42 UTC to 2026-08-20 16:31 UTC, by the times incident.io posted.

What caused it?

incident.io hasn't published a root cause. If it does, it shows here.

Where does this come from?

incident.io's official status page, https://status.incident.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.