- 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 2022-11-14 09:06 UTC and 2022-11-13 09:22 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 4
- monitoring
Let your users know once a fix is in place, and keep communication clear and precise.
provider
- identified
As you continue to work through the incident, update your customers frequently.
provider
- resolved
Empathize with those affected and let them know everything is operating as normal.
provider
- investigating
When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
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-7cefe6fb83
Is Crowdin still down?
No, this incident was resolved 2022-11-13 09:22 UTC. For Crowdin's live state, see https://down.guide/crowdin.
How long did it last?
0m, from 2022-11-14 09:06 UTC to 2022-11-13 09:22 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.