- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Crowdin. 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 2025-11-12 16:15 UTC and 2025-11-12 13:30 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.
Updates from Crowdin 1
- resolved
Between 13:40 and 14:10 UTC, a subset of Crowdin Enterprise users experienced server errors when attempting to access projects via the web interface (UI). The issue affected users with specific project configurations. Access via the API remained operational. The service was fully available for translators, though. Our team identified and deployed a fix for the underlying server issue. The problem is resolved, and project access is fully restored. If you were affected by this issue, please refresh your browser page to ensure full functionality. We apologize for the inconvenience.
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-e8f34077a9
Is Crowdin still down?
No, this incident was resolved 2025-11-12 13:30 UTC. For Crowdin's live state, see https://down.guide/crowdin.
How long did it last?
0m, from 2025-11-12 16:15 UTC to 2025-11-12 13:30 UTC, by the times Crowdin posted.
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.