Transifex Status

The system looks stable. We apologize for any issues you might be experiencing.

**API v3 Partial Downtime** **Date:** 02 April 2026  **Service Impacted:** api-v3  **Impact Scope:** Services depending on api-v3 experienced degraded functionality **Summary** On April 2nd, api-v3 experienced partial downtime due to a database performance issue. A database query caused contention within the database, leading to increased resource utilization and degraded responsiveness of api-v3 pods. As a result, api-v3 instances were intermittently failing health checks and restarting, which further amplified database load and connection pressure. **Impact** * Degraded performance and intermittent unavailability of api-v3 * Increased error rates for dependent services * Elevated database CPU usage and connection counts ‌ **Root Cause** The incident was caused by a database query that partially blocked operations within the database. This led to: * Query contention and locking behavior * Increased execution times for other queries * Accumulation of database connections from api-v3 pods This combination resulted in reduced system responsiveness and instability in api-v3. **Mitigation & Resolution** * Problematic long-running queries were identified and terminated * The affected query was optimized to improve performance and reduce locking behavior Following these actions, system performance returned to normal and stability was restored. **Follow-up Actions** * Optimize database query performance related to the incident * Improve monitoring and alerting for long-running or blocking queries * Evaluate database connection handling and limits in api-v3 * Consider implementing specific query timeouts and safeguards to prevent similar issues ‌ **Current Status** The issue has been resolved, and the system has remained stable since the fix was applied.

**Service-to-Service Communication Degradation** **Summary** During the incident, we observed intermittent, seemingly random delays when refreshing the application at [app.transifex.com](http://app.transifex.com). These delays affected the handling of customer requests and overall platform responsiveness. **Investigation & Findings** Following the initial reports, we investigated our load balancer logs and identified an unusually high volume of requests between our core service and the Transifex-delivery service. By correlating the load balancer logs with our application logs, we determined that a substantial number of requests were being throttled and retried between those services. This led to performance degradation when handling incoming requests on our main platform. **Impact** The issue caused performance degradation across our platform at irregular time intervals. **Mitigation & Resolution** As part of scheduled maintenance, we temporarily paused translation activity to adjust certain configurations. After the maintenance changes were applied, translation activity was re-enabled. However, the system did not immediately return to a fully stable state. To ensure reliable request handling and prevent further performance degradation, we made additional adjustments to the affected language configurations to reduce internal service load and fully stabilize the platform. Once system stability was fully confirmed, all affected languages and their translations were restored, and the platform was gradually returned to full functionality. **Preventive Actions & Improvements** To reduce the risk of similar issues occurring in the future, we have introduced improvements to how requests are handled between our core platform services and the Transifex-delivery service, including configuring throttling and retry mechanisms.

The issue has been resolved, and everything is now working as expected. Thanks so much for your patience — apologies for the disruption earlier!

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.

All services are back to normal. Thank you for your patience during this time.

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 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 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.

The Issue has been addressed, and everything is back to normal. Thank you for your patience, and we apologize for any inconvenience.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been successfully completed. Thank you for your patience and understanding!

Our scheduled maintenance has been completed successfully. Services are fully restored and functioning as expected. Thank you for your patience!

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.