#post-mortem

We resolved a Redis connection exhaustion issue in US-East, impacting job processing and queues. Our fixes ensure stability and prevent future incidents.

We've switched to Let's Encrypt for SSL, enhancing security but causing issues for some older systems. Steps are in place to prevent future incidents.

Transloadit quickly fixed a local file inclusion vulnerability in its API, ensuring the security of customer data and highlighting its commitment to privacy.

We've enhanced security by fixing an ImageMagick vulnerability, improving SVG filtering, and reinforcing process monitoring to protect customer data.

On December 6, 2018, we had a significant outage. Here's a detailed look into how we dealt with the situation.

Recently, Transloadit was affected by a security vulnerability in ImageMagick. This posts details our response to the situation and the fixes we applied.

We're reverting a change to the 'crop' resize strategy after affecting users, offering support for those impacted. Our apologies for the oversight.

Between June 15 and June 30, 2017, we mistakenly counted every byte twice towards data usage. The bug was fixed and the affected customers were compensated.

We addressed Redis issues by optimizing our infrastructure, leading to enhanced processing speeds and system stability, ensuring reliable service for our users.

In 2016, word came out about a bug in ImageMagick, which was quickly nicknamed ImageTragick. There was concern that Transloadit might be impacted by this bug.

Apologizing for an issue which affected a small percentage of our users. We have taken cautionary measures to ensure this doesn't happen again.

For some time, many support requests were caught in our spam filter. We have since switched support providers.

In 2015, some of our customers were rejected with false errors from our rate limiter. Read about the measures we took to prevent this from happening again.

We're enhancing our jQuery SDK with rigorous testing and updates, including a critical patch, to ensure stability and prevent future issues.

We resolved an outage caused by 20k /http/import jobs with scaling and connectivity fixes, ensuring a more reliable service for our customers.

Amazon S3 is a widely used service, but it has its own set of bugs. We have fixed various issues regarding PUT requests, error codes, etc.