Update - We are continuing to work on the fix. We sincerely apologise for the delay in resoving the incident. Keeping you updated on where we stand, we’re almost at the point where we have all the data backed up, then we can reset the messaging system and restore the data. We will make sure to provide a detailed RCA after this is resolved.
Jan 22, 2026 - 07:27 UTC
Update - We are continuing to work on the fix. Due to the huge amount of data to recover in our internal messaging system, it is taking longer than expected. We are now switching strategy to backup the data and restart the system. ETA still not available but our entire Engineering team and the leaders are continuing to work with external vendor to address this as soon as possible
Jan 22, 2026 - 06:00 UTC
Update - We are continuing to work on the fix. Incident was caused by our internal messaging system outage and now we are in the final stage of restoring it. We will keep you posted with the progress.
Jan 22, 2026 - 03:25 UTC
Identified - We have identified the root cause of the issue and are working on a fix. We are still all-hands on the issue, but do not have an ETA at this stage yet.
Jan 22, 2026 - 00:11 UTC
Investigating - We are actively investigating an issue causing elevated error rates and degraded service availability across multiple endpoints. Our team is aware of the impact and are currently all-hands on this incident. We will provide updates as soon as we can.
Jan 21, 2026 - 22:54 UTC