Incidents reported on status page for CryptoMatic Bot https://status.cryptomaticbot.com/en https://d1lppblt9t2x15.cloudfront.net/logos/eff158f9352debfcf82528fd9e813916.png https://status.cryptomaticbot.com/en en https://status.cryptomaticbot.com/en Wed, 22 Oct 2025 07:44:02 +0000 https://status.cryptomaticbot.com/en#d3112eedc373d81dcff220519a4299008dae5b8a7d9df1f0af99938714541753 Webhook & Exchange Connection recovered https://status.cryptomaticbot.com/en Wed, 22 Oct 2025 07:39:40 +0000 https://status.cryptomaticbot.com/en#6f6aa7b4653909e09722b6367bb2def1a71bb9c4276190c6f7c565abd81e0ad9 Spot Analysis recovered https://status.cryptomaticbot.com/en Wed, 22 Oct 2025 07:25:02 +0000 https://status.cryptomaticbot.com/en#d3112eedc373d81dcff220519a4299008dae5b8a7d9df1f0af99938714541753 Webhook & Exchange Connection went down https://status.cryptomaticbot.com/en Wed, 22 Oct 2025 07:22:45 +0000 https://status.cryptomaticbot.com/en#6f6aa7b4653909e09722b6367bb2def1a71bb9c4276190c6f7c565abd81e0ad9 Spot Analysis went down https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:30:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#4232d3d23207e7bb1d6935cf249273c2c52a670859a7aa2af17fecd3ac78e381 Maintenance completed https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:30:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#4232d3d23207e7bb1d6935cf249273c2c52a670859a7aa2af17fecd3ac78e381 Maintenance completed https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:30:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#4232d3d23207e7bb1d6935cf249273c2c52a670859a7aa2af17fecd3ac78e381 Maintenance completed https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:30:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#4232d3d23207e7bb1d6935cf249273c2c52a670859a7aa2af17fecd3ac78e381 Maintenance completed https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:30:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#4232d3d23207e7bb1d6935cf249273c2c52a670859a7aa2af17fecd3ac78e381 Maintenance completed https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:30:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#4232d3d23207e7bb1d6935cf249273c2c52a670859a7aa2af17fecd3ac78e381 Maintenance completed https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:30:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#4232d3d23207e7bb1d6935cf249273c2c52a670859a7aa2af17fecd3ac78e381 Maintenance completed https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:30:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#4232d3d23207e7bb1d6935cf249273c2c52a670859a7aa2af17fecd3ac78e381 Maintenance completed https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:00:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#bf03d8e622a40cdb4f8949cb0b7655a1c9ae616f72791bc5a134db49d4a2a1cf A server upgrade to accommodate increased workload. https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:00:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#bf03d8e622a40cdb4f8949cb0b7655a1c9ae616f72791bc5a134db49d4a2a1cf A server upgrade to accommodate increased workload. https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:00:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#bf03d8e622a40cdb4f8949cb0b7655a1c9ae616f72791bc5a134db49d4a2a1cf A server upgrade to accommodate increased workload. https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:00:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#bf03d8e622a40cdb4f8949cb0b7655a1c9ae616f72791bc5a134db49d4a2a1cf A server upgrade to accommodate increased workload. https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:00:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#bf03d8e622a40cdb4f8949cb0b7655a1c9ae616f72791bc5a134db49d4a2a1cf A server upgrade to accommodate increased workload. https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:00:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#bf03d8e622a40cdb4f8949cb0b7655a1c9ae616f72791bc5a134db49d4a2a1cf A server upgrade to accommodate increased workload. https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:00:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#bf03d8e622a40cdb4f8949cb0b7655a1c9ae616f72791bc5a134db49d4a2a1cf A server upgrade to accommodate increased workload. https://status.cryptomaticbot.com/en/incident/539311 Thu, 03 Apr 2025 17:00:28 -0000 https://status.cryptomaticbot.com/en/incident/539311#bf03d8e622a40cdb4f8949cb0b7655a1c9ae616f72791bc5a134db49d4a2a1cf A server upgrade to accommodate increased workload. https://status.cryptomaticbot.com/en/incident/345859 Tue, 26 Mar 2024 17:30:00 -0000 https://status.cryptomaticbot.com/en/incident/345859#b11a0f34e7c25817804688d9741d1a70245968f91e0fecd415e1a301f9066ff8 Maintenance completed https://status.cryptomaticbot.com/en/incident/345859 Tue, 26 Mar 2024 17:30:00 -0000 https://status.cryptomaticbot.com/en/incident/345859#b11a0f34e7c25817804688d9741d1a70245968f91e0fecd415e1a301f9066ff8 Maintenance completed https://status.cryptomaticbot.com/en/incident/345859 Tue, 26 Mar 2024 17:30:00 -0000 https://status.cryptomaticbot.com/en/incident/345859#b11a0f34e7c25817804688d9741d1a70245968f91e0fecd415e1a301f9066ff8 Maintenance completed https://status.cryptomaticbot.com/en/incident/345859 Tue, 26 Mar 2024 17:00:00 -0000 https://status.cryptomaticbot.com/en/incident/345859#e6858bbe0a34f3f695eddb13f6b1ef747f9c3782e093721d124b3cb02446513f In order to meet the increasing workload in the system, we will strengthen our database server on Tuesday, March 26, at 17:00 (UTC). While this process is taking place, there will be an interruption of 15-60 minutes in the system. During the outage, the robot will not make any transactions and you will need to track your open positions through the Binance application. Please be prepared to take precautions accordingly. https://status.cryptomaticbot.com/en/incident/345859 Tue, 26 Mar 2024 17:00:00 -0000 https://status.cryptomaticbot.com/en/incident/345859#e6858bbe0a34f3f695eddb13f6b1ef747f9c3782e093721d124b3cb02446513f In order to meet the increasing workload in the system, we will strengthen our database server on Tuesday, March 26, at 17:00 (UTC). While this process is taking place, there will be an interruption of 15-60 minutes in the system. During the outage, the robot will not make any transactions and you will need to track your open positions through the Binance application. Please be prepared to take precautions accordingly. https://status.cryptomaticbot.com/en/incident/345859 Tue, 26 Mar 2024 17:00:00 -0000 https://status.cryptomaticbot.com/en/incident/345859#e6858bbe0a34f3f695eddb13f6b1ef747f9c3782e093721d124b3cb02446513f In order to meet the increasing workload in the system, we will strengthen our database server on Tuesday, March 26, at 17:00 (UTC). While this process is taking place, there will be an interruption of 15-60 minutes in the system. During the outage, the robot will not make any transactions and you will need to track your open positions through the Binance application. Please be prepared to take precautions accordingly.