Transifex incident
Subscription Pages – Partial Outage Due to AWS Service Issue
Transifex experienced a minor incident on October 20, 2025 affecting Transifex App, lasting 17h 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 20, 2025, 10:30 AM UTC
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.
- identified Oct 20, 2025, 10:50 AM UTC
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.
- monitoring Oct 20, 2025, 11:43 AM UTC
Subscription pages are currently operating normally. We will continue to monitor and provide updates as needed. We appreciate your patience.
- monitoring Oct 20, 2025, 04:01 PM UTC
AWS is continuing recovery efforts. Our systems remain stable, but we continue to monitor closely for any potential impact.
- resolved Oct 21, 2025, 04:22 AM UTC
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.