On the morning of April 16th, we suffered an incident due to API instances being stopped.

Upon investigation, we identified that the primary factor behind the incident was a memory leak issue encountered while handling very large datasets. Our engineering team responded by restarting the affected API instances, restoring accessibility to the impacted environments.

The total outage period for affected environments was 1 hour and 50 minutes.