We started checking Transifex 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 Transifex 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 Transifex's own status page declared. Below it, any public chatter we saw about Transifex 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 Transifex's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Transifex in the last 24 hours, which is not evidence that nothing is wrong.
Transifex'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 Transifex's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Transifex 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%
441
US-West
100.00%
325
Europe
100.00%
300
Asia-Pacific
100.00%
180
Their declared record
Transifex's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Degraded Performance on Transifex WebsiteMinor incident
Sep 21, 2026, 10:48 AM UTC to Sep 21, 2026, 2:58 PM UTC (4h 10m)resolved
their latest update (Sep 21, 2026, 2:58 PM UTC): This incident has been resolved.
Degraded PerformanceMinor incident
Sep 8, 2026, 9:20 AM UTC to Sep 8, 2026, 1:47 PM UTC (4h 27m)resolved
their latest update (Sep 8, 2026, 1:47 PM UTC): This incident has been resolved.
API IssueAll systems operational
Jun 24, 2026, 2:09 PM UTC to Jun 24, 2026, 6:03 PM UTC (3h 54m)resolved
their latest update (Jun 24, 2026, 6:03 PM UTC): This incident has been resolved.
Performance IssuesAll systems operational
May 7, 2026, 9:37 AM UTC to May 7, 2026, 1:21 PM UTC (3h 44m)resolved
their latest update (May 7, 2026, 1:21 PM UTC): The system looks stable. We apologize for any issues you might be experiencing.
API IssueAll systems operational
Apr 2, 2026, 12:50 PM UTC to Apr 2, 2026, 7:25 PM UTC (6h 34m)postmortem published
their latest update (Apr 7, 2026, 8:23 AM UTC): **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…
Degrated application performanceMinor incident
Dec 4, 2025, 11:39 AM UTC to Dec 4, 2025, 4:47 PM UTC (5h 8m)postmortem published
their latest update (Dec 9, 2025, 8:14 AM UTC): **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…
Degrated API performanceAll systems operational
Dec 2, 2025, 2:22 PM UTC to Dec 2, 2025, 6:08 PM UTC (3h 46m)resolved
their latest update (Dec 2, 2025, 6:08 PM UTC): The issue has been resolved, and everything is now working as expected.
Thanks so much for your patience — apologies for the disruption earlier!
Subscription Pages – Partial Outage Due to AWS Service IssueMinor incident
Oct 20, 2025, 10:30 AM UTC to Oct 21, 2025, 4:22 AM UTC (17h 52m)resolved
their latest update (Oct 21, 2025, 4: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.
Scheduled Maintenance: AI TranslationsAll systems operational
Aug 27, 2025, 12:14 PM UTC to Aug 27, 2025, 12:34 PM UTC (20 min)resolved
their latest update (Aug 27, 2025, 12:34 PM UTC): All services are back to normal. Thank you for your patience during this time.
Intermittent Delays with Git appAll systems operational
Jul 4, 2025, 11:22 AM UTC to Jul 4, 2025, 8:59 PM UTC (9h 37m)resolved
their latest update (Jul 4, 2025, 8:59 PM UTC): 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 …
Showing the 10 most recent of 50 incidents Transifex has declared in the history we hold.
These entries are Transifex'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.
Transifex'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.