Skip to main content
Miro

Issue with creating support requests for customers with language set to Japanese

Degraded Lasted 30m · started · Miro's page

Level
confirmed
Worst impact
Degraded
Down Index
26of 100

What to do

  • Check whether your product depends on Miro. 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 30m it lasted.

    Anything that failed between 2025-09-10 06:34 UTC and 2025-09-10 07:04 UTC may need a replay.
  • Subscribe to Miro's feed to hear about the next one first. RSS feed

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

Updates from Miro 3

  1. investigating

    Customers with language set to Japanese are unable to raise support requests via the learning centre or access learning centre content.  While we are investigating - it is still possible to contact support by using the following link: Our engineering team is working to identify the root cause and will provide updates as we learn more. We apologize for any inconvenience this may cause and appreciate your patience.

    provider

  2. identified

    We identified the cause of the issue which is affecting users using Miro in the Japanese and Portuguese languages. The issue is related to a software update that we are now fixing. We will provide further updates in 15 minutes.

    provider

  3. resolved

    The Learning centre issue affecting users in Japanese and Portuguese languages has now been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our support team.

    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-267ecf4013

Is Miro still down?

No, this incident was resolved 2025-09-10 07:04 UTC. For Miro's live state, see https://down.guide/miro.

How long did it last?

30m, from 2025-09-10 06:34 UTC to 2025-09-10 07:04 UTC, by the times Miro posted.

What caused it?

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

Where does this come from?

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