Previous incidents
usetada.com is down
Resolved Jul 31 at 09:12pm WIB
usetada.com recovered.
1 previous update
Msite Service is down
Resolved Jul 27 at 05:28pm WIB
Msite Service recovered.
3 previous updates
usetada.com and Msite Service are down
Resolved Jul 26 at 07:04am WIB
usetada.com recovered.
3 previous updates
Msite Service is down
Resolved Jul 19 at 06:12pm WIB
Msite Service recovered.
3 previous updates
usetada.com is down
Resolved Jul 19 at 06:24am WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved Jul 11 at 10:01am WIB
usetada.com recovered.
3 previous updates
DNS resolution problem
Resolved Jul 09 at 02:12pm WIB
The team already fix the issue, and our services status are stabilizing.
2 previous updates
usetada.com is down
Resolved Jul 09 at 10:05am WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved Jun 24 at 07:21pm WIB
usetada.com recovered.
1 previous update
Msite Service and Wallet API are down
Resolved Jun 19 at 08:55am WIB
Wallet API recovered.
5 previous updates
Unable to login
Resolved Jun 19 at 07:48am WIB
the storage issue has been resolved.
The database autoscale fail due to limit imposed. The limit has now been increased.
2 previous updates
usetada.com is down
Resolved Jun 16 at 11:32pm WIB
usetada.com recovered.
5 previous updates
Buyfrom.io is down
Resolved Jun 14 at 10:47pm WIB
Buyfrom.io recovered.
1 previous update
Issue with redemption
Resolved Jun 20 at 08:48am WIB
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...
3 previous updates
Elasticsearch server is down
Resolved Jun 13 at 10:17am WIB
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...
2 previous updates
usetada.com is down
Resolved Jun 10 at 11:34am WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved May 25 at 03:01am WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved May 18 at 03:52pm WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved May 16 at 10:27pm WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved May 15 at 12:59pm WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved May 12 at 10:55pm WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved May 08 at 12:32pm WIB
usetada.com recovered.
1 previous update
usetada.com is down
Resolved May 06 at 07:57am WIB
usetada.com recovered.
1 previous update