We started checking Crowdin on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Crowdin reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Crowdin's own status page declared. Below it, any public chatter we saw about Crowdin and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Crowdin's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Crowdin in the last 24 hours, which is not evidence that nothing is wrong.
Crowdin's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Crowdin's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Crowdin next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
429
US-West
100.00%
325
Europe
100.00%
298
Asia-Pacific
100.00%
181
Their declared record
Crowdin's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Investigating Performance IssuesPartial outage
Oct 22, 2026, 11:13 AM UTC to Oct 22, 2026, 11:25 AM UTC (13 min)resolved
their latest update (Oct 22, 2026, 11:25 AM UTC): The performance issue affecting Crowdin Enterprise has been resolved, and the service is now operating normally.
False Downtime Report for Crowdin Translate [Resolved]All systems operational
Jul 7, 2026, 6:27 PM UTC to Jul 7, 2026, 6:27 PM UTC (0 min)resolved
their latest update (Jul 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…
Downgraded performance of Crowdin and Crowdin EnterpriseMinor incident
Mar 16, 2026, 8:55 AM UTC to Mar 16, 2026, 9:46 AM UTC (50 min)resolved
their latest update (Mar 16, 2026, 9:46 AM UTC): After 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!
Issue with the access to organizations hosted in EU data centerMajor outage
Jan 19, 2026, 2:30 PM UTC to Jan 19, 2026, 2:50 PM UTC (20 min)resolved
their latest update (Jan 19, 2026, 2:50 PM UTC): The 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
Intermittent UI Access Issues for Crowdin Enterprise ProjectsAll systems operational
Nov 12, 2025, 1:30 PM UTC to Nov 12, 2025, 1:30 PM UTC (0 min)resolved
their latest update (Nov 12, 2025, 1:30 PM UTC): 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 full…
Project builds fail under certain conditionsMinor incident
Oct 20, 2025, 8:16 PM UTC to Oct 20, 2025, 8:29 PM UTC (13 min)resolved
their latest update (Oct 20, 2025, 8:29 PM UTC): 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.
Issues when exporting translations via UI and APIAll systems operational
Oct 20, 2025, 10:25 AM UTC to Oct 20, 2025, 12:39 PM UTC (2h 14m)resolved
their latest update (Oct 20, 2025, 12:39 PM UTC): After nearly 3 hours of monitoring, we confirm that translations are exported on time, and all connectors are fully accessible. We consider the case as resolved.
Downgraded performance of Crowdin EnterpriseMinor incident
Oct 10, 2025, 3:06 PM UTC to Oct 10, 2025, 3:30 PM UTC (24 min)resolved
their latest update (Oct 10, 2025, 3:30 PM UTC): After additional monitoring, we can confirm that the service is fully operational
Performance downgrade at Crowdin EnterpriseAll systems operational
Oct 10, 2025, 2:34 PM UTC to Oct 10, 2025, 2:41 PM UTC (6 min)resolved
their latest update (Oct 10, 2025, 2:41 PM UTC): All services are fully operational
Degraded Performance of Downloads and Redirect ServerAll systems operational
Jan 11, 2025, 8:09 AM UTC to Jan 11, 2025, 8:09 AM UTC (0 min)resolved
their latest update (Jan 11, 2025, 8:09 AM UTC): We experienced a temporary downtime of our Downloads and redirect service, which impacted the ability of some users to download translations.
Showing the 10 most recent of 14 incidents Crowdin has declared in the history we hold.
These entries are Crowdin's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Crowdin's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.