Crowdin: False Downtime Report for Crowdin Translate [Resolved]

What to do

Check whether you use Crowdin Crowdin Translate. 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 0m it lasted.
Anything that failed between 2026-07-07 18:27 UTC and 2026-07-07 18:27 UTC may need a replay.
Subscribe to Crowdin's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=crowdin works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedJul 7, 2026, 6:27 PM UTC
Resolution We've resolved a status page reporting issue and removed an incident record that incorrectly showed 7 hours and 53 minutes of downtime for Crowdin Translate. The service was fully operational the entire time — there was no actual downtime or user impact. What Happened? The false "Major Outage" status was triggered by an automation notification glitch. Two conflicting updates (DOWN and UP) arrived at the exact same time. Due to a race condition, the system processed the DOWN alert but ignored the simultaneous UP notification, leaving the status page stuck in an incorrect state.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Crowdin still down?

No, this incident was resolved 2026-07-07 18:27 UTC. For Crowdin's live state, see https://down.guide/crowdin.

How long did it last?

0m, from 2026-07-07 18:27 UTC to 2026-07-07 18:27 UTC, by the times Crowdin posted.

What was affected?

Crowdin named Crowdin Translate.

What caused it?

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

Where does this come from?

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