500 Errors - Application and API errors
Incident Report for Redash
Resolved
Our internal Redis instance ran low on memory which affected both application load and API responses. We restarted Redis which freed up resources and brought all services back online. Due to an internal process deficiency we were not able to bounce Redis or update our StatusPage timely. This deficiency has now been resolved. We're still investigating what caused Redash to run low on memory.
Posted Aug 03, 2020 - 21:30 UTC