Crowdin Outage History
5 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Crowdin Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 22, 2026 | Investigating Performance IssuesThe performance issue affecting Crowdin Enterprise has been resolved, and the service is now operating normally. | 12 min | Resolved |
| Jul 7, 2026 | False Downtime Report for Crowdin Translate [Resolved]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… | 0 min | Resolved |
| Mar 16, 2026 | Downgraded performance of Crowdin and Crowdin EnterpriseAfter thorough monitoring, we can confirm the service is fully back to normal. The incident has now been marked as "Resolved". We will continue to monitor Crowdin's health 24/7/365. Thank you! | 50 min | Resolved |
| Jan 19, 2026 | Issue with the access to organizations hosted in EU data centerThe solution was delivered several minutes after the incident was reported, we were monitoring the performance of EU data center organizations and confirmed that it got back to normal | 19 min | Resolved |
| Nov 12, 2025 | Intermittent UI Access Issues for Crowdin Enterprise ProjectsBetween 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… | -165 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Crowdin incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Crowdin Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Crowdin acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Crowdin outage in this window ran 50 min, against a mean recovery of 20 min. If you depend on Crowdin in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.