All Systems Operational

About This Site

We're closely monitoring the performance of the Transifex.com platform and services. This page reflects the status of our services and documents any interruptions. If you are experiencing problems but there are no notices on this page, please email support@transifex.com.

Transifex Home page ? Operational
Transifex App Operational
Translation Memory Operational
API Operational
Translation Order Services ? Operational
Transifex Client Operational
Notifications Operational
Documentation Site Operational
Operational
Degraded Performance
Partial Outage
Major Outage
System Metrics Month Week Day
Uptime ?
Fetching
Website Response Time ?
Fetching
Past Incidents
May 29, 2015

No incidents reported today.

May 28, 2015

No incidents reported.

May 27, 2015

No incidents reported.

May 26, 2015
Resolved - This incident has been resolved.
May 26, 09:10 UTC
Monitoring - After an exhaustive search we found our Elasticsearch mapping was being deleted due to an erroneous API call. We've implemented a fix and will continue monitoring over the next few hours.

Thank you for your patience.
May 25, 10:43 UTC
Investigating - We have identified intermittent errors when loading the project explore page. We are investigating the issue and will let you know of any updates.

Sorry for the inconvenience.
May 20, 13:16 UTC
May 24, 2015

No incidents reported.

May 23, 2015

No incidents reported.

May 22, 2015

No incidents reported.

May 21, 2015

No incidents reported.

May 19, 2015
Resolved - This issue has been resolved. The 3rd party provider has repaired the fiber cut.
May 19, 06:32 UTC
Update - TL;DR: Use 199.85.126.20 as your DNS server for a possible remedy of the situation

We have conducted some tests and have figured out that it might be possible to access our site faster by using Norton DNS's 199.85.126.20 as your DNS server. If you are using Google Public DNS (for example 8.8.8.8) or OpenDNS (for example 208.67.220.220) as your DNS server, you may be impacted by the fiber cut that affects many networks. We have found out that for some of the users affected, using 199.85.126.20 as their DNS server helps accessing our site. This is because paths to 199.85.126.20 from your machine do not go through the problematic fiber, while it is possible that paths to 8.8.8.8 or 208.67.220.220 go through there as our experiments showed.
May 18, 19:45 UTC
Identified - Our website is loading slowly, especially from the US. Our cloud provider informs us that this is due to a fiber cut causing intermittent latency. A 3rd party fiber cut in Kernersville, NC that is currently impacting several major ISPs in the region. This issue is occurring outside of our internal network. We cannot control the paths customer traffic takes outside of our network, and customers may continue to experience latency, packet loss, or dropped connections impacting traffic traveling over the affected provider.
May 18, 19:40 UTC
May 17, 2015

No incidents reported.

May 16, 2015

No incidents reported.

May 15, 2015

No incidents reported.