Transifex Outage History
15 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Transifex Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 22, 2026 | Scheduled maintenanceVerification is currently underway for the maintenance items. | 3h 0m | Scheduled |
| Sep 21, 2026 | Degraded Performance on Transifex WebsiteThis incident has been resolved. | 4h 9m | Resolved |
| Sep 8, 2026 | Degraded PerformanceThis incident has been resolved. | 4h 27m | Resolved |
| Sep 4, 2026 | Scheduled maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Sep 4, 2026 | Scheduled maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Aug 7, 2026 | Scheduled maintenanceThe scheduled maintenance has been completed. | 2h 30m | Scheduled |
| Jun 30, 2026 | Scheduled Maintenance: Transifex App & Transifex API may be affectedThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jun 24, 2026 | API IssueThis incident has been resolved. | 3h 54m | Resolved |
| May 7, 2026 | Performance IssuesThe system looks stable. We apologize for any issues you might be experiencing. | 3h 43m | Resolved |
| Apr 2, 2026 | API Issue**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… | 6h 34m | Resolved |
| Feb 18, 2026 | Infrastructure MaintenanceThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Jan 30, 2026 | Scheduled Maintenance: Infrastructure upgradesThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 4, 2025 | Degrated application performance**Service-to-Service Communication Degradation** **Summary** During the incident, we observed intermittent, seemingly random delays when refreshing the application at… | 5h 7m | Resolved |
| Dec 2, 2025 | Degrated API performanceThe issue has been resolved, and everything is now working as expected. Thanks so much for your patience — apologies for the disruption earlier! | 3h 46m | Resolved |
| Nov 7, 2025 | Scheduled Infrastructure UpgradeThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Transifex incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Transifex Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Transifex acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Transifex outage in this window ran 6h 34m, against a mean recovery of 3h 9m. If you depend on Transifex in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.