Calamari Status

Resolved: The issue has been resolved at 19:11:58 on 2024.11.14. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.

Investigating: At 19:06:51 on 2024.11.14 our monitoring system discovered a problem in eu-west-1. Our team was notified and we're already working on fixing the issue.

Resolved: We've restored 100% accounts. Right now, we are monitoring systems.

Monitoring: We've restored 100% of accounts in the US and ASIA regions and are consequently restoring the data for clients in the EU. Currently, we've fixed approximately 80% of affected accounts in EU.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 50% of affected accounts.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 25% of affected accounts.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 15% of affected accounts. The ETA for correcting balances will take longer than we expected.

Monitoring: We are consequently restoring the data from the moment before our last release. The ETA for correcting balances in all accounts is 60-90 minutes.

Monitoring: We are consequently restoring the data from the moment before our last release. The process of restoring the data is in the production environment. Carry-over balances will be fixed in the next 30-60 min for the first group of our clients.

Identified: We've found a solution to prevent the problem from spreading—it is currently rolling out to the production environment. We are still working on a solution for recalculating carry-over to the correct amount.

Identified: We are working on a solution to ensure the consistency of all our clients' data. We still do not have an ETA for solving the problem, but we will let you know as soon as we find one.

Identified: We found the cause of the issue and are working on a solution. The problem is related to our recent release - improvements in the carry-over engine.

Investigating: We are currently investigating the issue.

Resolved: The issue has been resolved at 19:11:58 on 2024.11.14. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.

Investigating: At 19:06:51 on 2024.11.14 our monitoring system discovered a problem in eu-west-1. Our team was notified and we're already working on fixing the issue.

Resolved: We've restored 100% accounts. Right now, we are monitoring systems.

Monitoring: We've restored 100% of accounts in the US and ASIA regions and are consequently restoring the data for clients in the EU. Currently, we've fixed approximately 80% of affected accounts in EU.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 50% of affected accounts.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 25% of affected accounts.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 15% of affected accounts. The ETA for correcting balances will take longer than we expected.

Monitoring: We are consequently restoring the data from the moment before our last release. The ETA for correcting balances in all accounts is 60-90 minutes.

Monitoring: We are consequently restoring the data from the moment before our last release. The process of restoring the data is in the production environment. Carry-over balances will be fixed in the next 30-60 min for the first group of our clients.

Identified: We've found a solution to prevent the problem from spreading—it is currently rolling out to the production environment. We are still working on a solution for recalculating carry-over to the correct amount.

Identified: We are working on a solution to ensure the consistency of all our clients' data. We still do not have an ETA for solving the problem, but we will let you know as soon as we find one.

Identified: We found the cause of the issue and are working on a solution. The problem is related to our recent release - improvements in the carry-over engine.

Investigating: We are currently investigating the issue.

Investigating: At 09:46:50 on 2024.10.08 our monitoring system discovered a problem in us-east-1. Our team was notified and we're already working on fixing the issue.

Resolved: The issue has been resolved at 12:57:03 on 2024.11.17. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.

Investigating: At 12:52:05 on 2024.11.17 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.

Resolved: We've restored 100% accounts. Right now, we are monitoring systems.

Monitoring: We've restored 100% of accounts in the US and ASIA regions and are consequently restoring the data for clients in the EU. Currently, we've fixed approximately 80% of affected accounts in EU.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 50% of affected accounts.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 25% of affected accounts.

Monitoring: We are consequently restoring the data. Currently, we've fixed approximately 15% of affected accounts. The ETA for correcting balances will take longer than we expected.

Monitoring: We are consequently restoring the data from the moment before our last release. The ETA for correcting balances in all accounts is 60-90 minutes.

Monitoring: We are consequently restoring the data from the moment before our last release. The process of restoring the data is in the production environment. Carry-over balances will be fixed in the next 30-60 min for the first group of our clients.

Identified: We've found a solution to prevent the problem from spreading—it is currently rolling out to the production environment. We are still working on a solution for recalculating carry-over to the correct amount.

Identified: We are working on a solution to ensure the consistency of all our clients' data. We still do not have an ETA for solving the problem, but we will let you know as soon as we find one.

Identified: We found the cause of the issue and are working on a solution. The problem is related to our recent release - improvements in the carry-over engine.

Investigating: We are currently investigating the issue.

Resolved: The issue has been resolved at 15:17:09 on 2024.11.18. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.

Investigating: At 15:12:05 on 2024.11.18 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.

Resolved: The issue has been resolved at 12:17:07 on 2024.11.20. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.

Investigating: At 12:12:06 on 2024.11.20 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.

Investigating: At 09:46:50 on 2024.10.08 our monitoring system discovered a problem in us-east-1. Our team was notified and we're already working on fixing the issue.

Resolved: The issue has been resolved at 12:57:03 on 2024.11.17. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.

Investigating: At 12:52:05 on 2024.11.17 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.

Resolved: The issue has been resolved at 15:17:09 on 2024.11.18. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.

Investigating: At 15:12:05 on 2024.11.18 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.

Resolved: The issue has been resolved at 12:17:07 on 2024.11.20. We're incredibly sorry for the inconvenience. This problem will be investigated further to make sure it won't happen again. We will add a postmortem shortly.

Investigating: At 12:12:06 on 2024.11.20 our monitoring system discovered a problem in ap-southeast-1. Our team was notified and we're already working on fixing the issue.