- Level
- confirmed
- Worst impact
- Degraded
- Components
- crowdin.com, Crowdin Enterprise
- Down Index
- 18of 100
What to do
Check whether you use Crowdin crowdin.com, Crowdin Enterprise. 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 13m it lasted.
Anything that failed between 2025-10-20 20:16 UTC and 2025-10-20 20:29 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 2
- monitoring
We have noticed that builds are failing or taking longer than usual due to an issue with the cloud provider. This issue is not global; we are continuing to monitor the status. We will update the status once we confirm that the builds are working properly.
provider
- resolved
Almost right after the incident was raised, the project builds started working as expected. After conducting various tests, we can confirm that the builds have returned to normal, and the incident can be considered resolved.
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-2aa1600a9a
Is Crowdin still down?
No, this incident was resolved 2025-10-20 20:29 UTC. For Crowdin's live state, see https://down.guide/crowdin.
How long did it last?
13m, from 2025-10-20 20:16 UTC to 2025-10-20 20:29 UTC, by the times Crowdin posted.
What was affected?
Crowdin named crowdin.com, Crowdin Enterprise.
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.