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, 18 Jun 2025 19:22:59 +0000 https://status.cryptomaticbot.com/en#2f9dc7f8d3e89ba837427ac53c32689bdf0bf8e388b7c7f2c29ebbfbae896015 Futures Analysis recovered https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:22:59 +0000 https://status.cryptomaticbot.com/en#64d38ab484a0117e354a6af1f4166375b4dfaaba0575840747969598342d1a61 Spot Analysis recovered https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:22:59 +0000 https://status.cryptomaticbot.com/en#2ca7900094a3618777701f3cacf05a28102f8b4ac1302918426b7d273c48b5f8 Position Tracking 3 recovered https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:22:59 +0000 https://status.cryptomaticbot.com/en#67e58bf4a3e9e5ba4d97e02739f3a1d852575112aca6d46b10f5aa386ad11100 Position Tracking 2 recovered https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:22:59 +0000 https://status.cryptomaticbot.com/en#6fa1525f052d6f956faf4562315e871d45078b9a34dfc171cd3c187a57e3d0c8 Position Tracking 4 recovered https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:22:59 +0000 https://status.cryptomaticbot.com/en#7b8cb175df42ff200b4ac0824c42bfbd7f98d9beead87d48b1097f78d9a9bade Position Tracking 1 recovered https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:22:59 +0000 https://status.cryptomaticbot.com/en#f280a4783a3444bc148832de009c984efc968cc02ce143ed396f1bbe1d98c821 Website & Trader Panel recovered https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:21:36 +0000 https://status.cryptomaticbot.com/en#2d45298947b94a1cacc1fc6641ad79134ccdc56b10d99eebae166600236a6473 Webhook & Exchange Connection recovered https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:00:34 +0000 https://status.cryptomaticbot.com/en#2f9dc7f8d3e89ba837427ac53c32689bdf0bf8e388b7c7f2c29ebbfbae896015 Futures Analysis went down https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:00:15 +0000 https://status.cryptomaticbot.com/en#64d38ab484a0117e354a6af1f4166375b4dfaaba0575840747969598342d1a61 Spot Analysis went down https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 19:00:05 +0000 https://status.cryptomaticbot.com/en#2ca7900094a3618777701f3cacf05a28102f8b4ac1302918426b7d273c48b5f8 Position Tracking 3 went down https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 18:59:44 +0000 https://status.cryptomaticbot.com/en#67e58bf4a3e9e5ba4d97e02739f3a1d852575112aca6d46b10f5aa386ad11100 Position Tracking 2 went down https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 18:59:35 +0000 https://status.cryptomaticbot.com/en#6fa1525f052d6f956faf4562315e871d45078b9a34dfc171cd3c187a57e3d0c8 Position Tracking 4 went down https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 18:59:14 +0000 https://status.cryptomaticbot.com/en#7b8cb175df42ff200b4ac0824c42bfbd7f98d9beead87d48b1097f78d9a9bade Position Tracking 1 went down https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 18:58:56 +0000 https://status.cryptomaticbot.com/en#f280a4783a3444bc148832de009c984efc968cc02ce143ed396f1bbe1d98c821 Website & Trader Panel went down https://status.cryptomaticbot.com/en Wed, 18 Jun 2025 18:58:16 +0000 https://status.cryptomaticbot.com/en#2d45298947b94a1cacc1fc6641ad79134ccdc56b10d99eebae166600236a6473 Webhook & Exchange Connection 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.