Previous incidents

usetada.com recovered.

Msite Service recovered.

usetada.com recovered.

Msite Service recovered.

usetada.com recovered.

usetada.com recovered.

The team already fix the issue, and our services status are stabilizing.

usetada.com recovered.

usetada.com recovered.

Wallet API recovered.

the storage issue has been resolved.
The database autoscale fail due to limit imposed. The limit has now been increased.

usetada.com recovered.

Buyfrom.io recovered.

Postmortem Analysis:

Our Redis server encountered numerous persistent, unowned connections. As these connections lacked identifiable owners, they were unable to be terminated, which consequently hindered incoming connections to the server. This unexpected influx resulted in a high CPU and memory load on the server.

The resolution to this issue necessitated terminating these persistent connections. Given the unresponsiveness of the Redis server, we chose to accomplish this by rebooting t...

Postmortem:
Our elasticsearch server instance have the JVM setting for memory used set to 10GB. The instance is using EC2 spot instance and managed with https://spot.io for better cost optimization.
We configured the ES instance within spot.io in such a way that we can use a variety of EC2 spot instance types, depending on which type have the best value at that time.
But the problem is some of the configured instance types doesn't have the memory capacity required for the JVM setting abo...

usetada.com recovered.

usetada.com recovered.

usetada.com recovered.

usetada.com recovered.

usetada.com recovered.

usetada.com recovered.

usetada.com recovered.

usetada.com recovered.