Transifex had 11 outages in the last 2 years totaling 53h 23m of downtime — averaging 0.5 incidents per month.
There were 11 Transifex outages since July 15, 2024 totaling 53h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating the issue
The issue has been identified and a fix is being implemented
This incident has been resolved.
We are currently investigated this issue
The issue has been identified and a fix is being implemented
A fix has been implemented and we are monitoring the results
The system looks stable. We apologize for any issues you might be experiencing.
We are currently investigating the issue.
We are investigating the issue.
The issue is still under investigation, and our team is working to resolve it as quickly as possible. Thank you for your patience.
The API and the app performance degradation have been resolved after taking the necessary actions on our side. We are now monitoring the system performance to ensure everything remains stable. Thank you for your patience.
The issue has been resolved, and everything is now working as expected. Thanks so much for your patience — apologies for the disruption earlier!
We are currently experiencing an issue affecting the subscription pages within our app. As a result, some users may encounter errors, slow performance, or temporary unavailability when accessing subscription-related features. Our investigation indicates that the issue stems from an upstream AWS service disruption (https://health.aws.amazon.com/health/status). We are closely monitoring the situation and will restore full functionality as soon as AWS resolves the underlying issue. Updates will be posted here as more information becomes available.
Latest update from AWS: "The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution. Additionally, some services are continuing to work through a backlog of events such as Cloudtrail and Lambda. While most operations are recovered, requests to launch new EC2 instances (or services that launch EC2 instances such as ECS) in the US-EAST-1 Region are still experiencing increased error rates. We continue to work toward full resolution. If you are still experiencing an issue resolving the DynamoDB service endpoints in US-EAST-1, we recommend flushing your DNS caches. We will provide an update by 4:15 AM, or sooner if we have additional information to share." We’re monitoring the situation closely and will provide additional updates as AWS shares more information.
Subscription pages are currently operating normally. We will continue to monitor and provide updates as needed. We appreciate your patience.
AWS is continuing recovery efforts. Our systems remain stable, but we continue to monitor closely for any potential impact.
The underlying AWS issue has been resolved, and everything is now fully operational. We’ll continue to monitor system performance, but no further impact is expected. This incident is now considered resolved.
We are performing scheduled maintenance on our infrastructure from 12:00 (UTC) until 12:30 (UTC). During this time, AI Translations may experience brief delays. Thank you for your patience!
Maintenance is complete.
Maintenance is complete. We will continue to monitor closely.
All services are back to normal. Thank you for your patience during this time.
We are investigating intermittent delays with GitHub, Bitbucket, and Gitlab Integrations. You may experience a delay in your workflows. Our team is actively working to mitigate the delays while simultaneously investigating the root cause of the issue. We will provide an update as soon as we have more information to share. Thank you all for your patience, and apologize for any inconvenience caused.
The issue has been identified, and we are actively working on applying the necessary fix to restore functionality without delays.
A fix has been implemented and we are monitoring the results.
The issue has been resolved, and Git app integrations operate normally. The incident was caused by a high rate of incoming tasks, which created a bottleneck in our queueing system and led to delays in task processing. Our team has implemented the necessary fix and will continue to monitor the system closely to ensure continued stability. We sincerely apologize for the inconvenience this may have caused and appreciate your patience throughout the resolution process. If you continue to experience any issues, please don’t hesitate to contact our support team.
We are currently experiencing delays in fillup processing. We apologize for any inconvenience this may be causing and appreciate your patience as we work to resolve this.
We have identified the cause of the delays. The issue is related to a high queue volume, and our team is actively working to address it. Steps are being taken to restore normal processing speeds.
A solution has been applied, and we're closely monitoring the situation.
We are happy to inform you that the issue has been fully resolved. Our team worked diligently to address the problem, and everything is now back to normal. Thank you for your patience and understanding during this time.
We are currently facing issues with the delivery of translations through our CDN, specifically related to Transifex Native projects. As a result, you may encounter issues with the availability of translations for certain languages. Our team is actively investigating the issue and is committed to restoring full functionality as quickly as possible. We appreciate your patience during this time and will provide updates as soon as more information becomes available.
We are still investigating the issue affecting translation delivery for certain languages. We will share updates as soon as we have more information.
Due to a configuration issue, new content updates were unavailable in certain locales. Our team has applied a fix, and normal functionality has been restored. We will continue to monitor to ensure everything works as expected.
We are pleased to inform you that the incident reported has been successfully resolved. We appreciate your patience and understanding during this incident. If you have any questions or require assistance, please do not hesitate to reach out to our support team.
You may experience intermittently a 504 error from our API. Our team is working on identifying the root cause and closely monitoring the system's behavior. We will provide an update as soon as we have more information to share. Thank you all for your patience and we apologize for any inconvenience caused.
We are still investigating the issue. At the moment, we are applying some changes, and we need to monitor the situation. We will keep you posted on our progress.
API is at operational status again. We will continue to monitor the situation and provide updates.
Our team developed a fix to deal with the intermittent issues on our API.
The fix has been deployed, and our team is monitoring the results.
The Issue has been addressed, and everything is back to normal. Thank you for your patience, and we apologize for any inconvenience.
Our team is actively working to identify the cause and restore full functionality as soon as possible. We apologize for any inconvenience this may cause and appreciate your patience. Thank you for your understanding.
We are pleased to inform you that the issue has been resolved, and all systems are back to normal operation.
Our systems are operating normally, and all services are back to full functionality.