Channable Outage History

Started Oct 02, 2026, 08:32 AM UTC· resolved Oct 06, 2026, 01:54 PM UTC

1. investigating Oct 02, 2026, 08:32 AM UTC

   We have identified an issue causing instability when trying to use the tool, and causing delays in background processing. We are investigating the exact cause.

2. investigating Oct 02, 2026, 08:45 AM UTC

   We are continuing to investigate this issue.

3. investigating Oct 02, 2026, 10:08 AM UTC

   We are continuing to investigate this issue.

4. investigating Oct 02, 2026, 10:45 AM UTC

   The instability has increased and is causing most of the tool to be unavailable. and most background processing is further delayed. Existing feeds are still available.

5. monitoring Oct 02, 2026, 01:26 PM UTC

   We have applied several fixes to our infrastructure. The Channable tool is stable again, and background processing is back to normal speed. Insights & Analytics and CSS are still working through a backlog, so data in these areas may be delayed for a while longer. We are monitoring the situation and will post an update once the backlog is cleared.

6. monitoring Oct 05, 2026, 01:37 PM UTC

   Background processing for Insights and CSS is still seeing delays. If your project uses these features, the rest of the project's run may also be delayed. We are currently working on a solution to mitigate these delays, and expect to roll this out by tomorrow (October 5th).

7. monitoring Oct 06, 2026, 10:47 AM UTC

   The Channable tool is stable again. We have increased processing capacity, and the backlog for Insights, Analytics, and CSS has been cleared. We will continue to monitor over the next few hours to make sure that it stays that way.

8. resolved Oct 06, 2026, 01:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 22, 2026, 11:53 AM UTC· resolved Aug 22, 2026, 01:36 PM UTC

1. investigating Aug 22, 2026, 11:53 AM UTC

   We are currently investigating this issue.

2. identified Aug 22, 2026, 11:57 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Aug 22, 2026, 12:04 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Aug 22, 2026, 01:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 24, 2026, 01:33 PM UTC· resolved Jul 29, 2026, 01:38 PM UTC

1. investigating Jul 24, 2026, 01:33 PM UTC

   We are currently experiencing an elevated error rate for product and offer submissions through our Kaufland integration. We are actively investigating the issue and are in direct contact with the Kaufland team to find a resolution. Note: Order processing remains fully unaffected. We will provide another update as soon as we have more information.

2. monitoring Jul 27, 2026, 09:27 AM UTC

   We have identified the cause of the errors and rolled out changes to mitigate the issue. Error rates are currently still elevated while we validate the effectiveness of these changes with Kaufland. Performance will remain degraded in the meantime. We are continuing to monitor the situation closely.

3. resolved Jul 29, 2026, 01:38 PM UTC

   We have identified the cause of the errors and the situation has improved significantly. The overall impact is currently limited; however, because we are still seeing occasional errors, our mitigation efforts will remain in place while we continue to monitor the situation. If you are still experiencing issues, please reach out to our Support team so we can assist you further.

Read the full incident report →

Started Jun 30, 2026, 04:44 PM UTC· resolved Jul 01, 2026, 11:06 AM UTC

1. monitoring Jun 30, 2026, 04:44 PM UTC

   Since 12:00 PM UTC today we have been experiencing a disruption with our Mirakl order connections. This is causing a delay in fetching orders from marketplaces into Channable. We are actively monitorring the issue and will provide an update as soon as we have more information.

2. resolved Jul 01, 2026, 11:06 AM UTC

   All Mirakl orders now being retrieved and processed.

Read the full incident report →

Started Jun 03, 2026, 01:34 PM UTC· resolved Jun 03, 2026, 03:20 PM UTC

1. investigating Jun 03, 2026, 01:34 PM UTC

   We are experiencing issues with Shopify imports and order processing. Shopify has acknowledge an incident on their end: https://www.shopifystatus.com/ We are investigating what the exact impact of this incident is on our integration and will update once we know more.

2. identified Jun 03, 2026, 01:57 PM UTC

   The issues we are seeing are related to the Shopify incident linked below. Shopify imports will not succeed and order synchronization can not succeed while this is ongoing.

3. monitoring Jun 03, 2026, 03:01 PM UTC

   Shopify has identified the issue and rolled out a mitigation. We are seeing recovery of order synchronization and processing of import jobs. We will keep monitoring until full recovery of processes.

4. resolved Jun 03, 2026, 03:20 PM UTC

   The issue has improved and Shopify order sync and stock updates are largely processing again. No action required: Any orders that failed during the incident have been or are being automatically re-sent by us.

Read the full incident report →

Started May 22, 2026, 06:31 PM UTC· resolved Jun 02, 2026, 02:02 PM UTC

1. investigating May 22, 2026, 06:31 PM UTC

   We are investigating a potential issue with Shopify authentication. Channable projects affected by this issue will show a red 'failed' marker for Shopify imports, and will not receive new orders, returns or stock updates. This incident will be updated once we know more.

2. identified May 22, 2026, 07:04 PM UTC

   The issue has been identified and a potential fix is being worked on. The potential fix will require manual action from an authorized Shopify user to re-link Channable to Shopify. Instructions to perform this re-linking will be shared once they are ready.

3. identified May 22, 2026, 07:16 PM UTC

   We have applied a fix which has allowed stock updates to work again. This means that Channable is again able to notify marketplaces of stock changes when orders are placed on Shopify, but we are not yet able to send new orders or returns from other marketplaces to Shopify.

4. identified May 22, 2026, 08:19 PM UTC

   We have identified a fix for the issue affecting Shopify connections. This fix requires manual intervention by an authorized Shopify user, which means Channable cannot apply this fix for you. To restore Shopify connectivity, please 'Renew' the connection as described in this page: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection

5. identified May 22, 2026, 09:11 PM UTC

   Contrary to our previous update we have identified that stock updates are still affected by this issue. The previously-shared fix for order connections will also fix stock updates and imports from Shopify. To restore Shopify connectivity, please 'Renew' the connection as described in this page: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection After renewing the connection any orders that failed while the connection was not working, will need to be re-sent by following the steps in this helpcenter article: https://helpcenter.channable.com/list-advertise/orders/troubleshooting-orders/how-to-fix-resend-a-failed-order#resend-all-orders

6. identified May 23, 2026, 11:11 AM UTC

   As part of Shopify's own security measures our Shopify app has been delisted. We are currently reaching out to Shopify to re-list our app as soon as possible. Until that time renewing connections as described in the previous updates is not possible. We will update when it is again possible to renew connection(s) and resend all failed orders.

7. identified May 23, 2026, 01:18 PM UTC

   We have identified a fix for renewing Shopify connections while our app remains delisted. We are currently working on implementing this and getting it in our tool. We expect to provide an update on this within 30 minutes.

8. identified May 23, 2026, 01:33 PM UTC

   Shopify connections can be renewed again in Channable. Companies with broken Shopify connections will see a notification on log in. To restore Shopify connectivity, please 'Renew' the connection as described in this page: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection. After pressing 'Renew' and logging in to Shopify you will need to press 'Open app'. This triggers the reauthentication process between Channable and your Shopify store.

9. monitoring May 26, 2026, 10:34 AM UTC

   Additional instructions for renewing Shopify connections and manual fallback We have provided further details and a manual workaround for users experiencing difficulties renewing their Shopify connection. You can find these full instructions at: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection. - Do NOT uninstall the current Channable app in Shopify during this recovery process. - If the 'Renew' button does not work, you can manually trigger the reauthentication flow by logging into admin.shopify.com, navigating to Installed apps, opening the Channable app, and clicking Open app. - Orders that failed while the connection was down will not automatically retry. Re-send them manually once your connection is active. Note that re-sent orders may take some time to appear in Shopify. If you are still unable to renew your connection after trying the manual fallback, please contact our support team at [email protected].

10. monitoring May 27, 2026, 01:53 PM UTC

    The Channable App is still unlisted in Shopify We are aware that the Channable app is no longer listed in Shopify’s app marketplace. We are working with Shopify to get the Channable app re-instated. In the meantime, DO NOT uninstall the Channable app in Shopify. Removing the app will prevent you from renewing your Shopify connection. Follow the renewal instructions here: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection

11. monitoring May 28, 2026, 09:49 AM UTC

    Fix implemented for Shopify metafields error message We have released a fix for users encountering the error message "Channable cannot access your Shopify metafields" for their Shopify imports. You can resolve this either by switching to Shopify Markets (if you haven't already done so), OR by applying a workaround in your Channable import settings. We have published the instructions for both methods in our changelog: https://helpcenter.channable.com/changelog#error-message-channable-cannot-access-your-shopify-metafields

12. monitoring May 28, 2026, 02:35 PM UTC

    Re-installations and new Shopify connections are now possible While we continue to work with Shopify to get the Channable app re-listed in Shopify's App store, we have identified temporary workarounds as follows: If you uninstalled the Channable app: You can now reinstall it directly from your Shopify admin backend without needing the app marketplace. Follow the instructions here: https://helpcenter.channable.com/changelog#i-uninstalled-the-channable-app-from-shopify If you need to install Channable for the first time: We have identified a direct installation URL that allows you to bypass the marketplace and establish a new connection. Follow the instructions here: https://helpcenter.channable.com/import-data/import-how-to/import-your-product-data/import-via-a-webshop/shopify#install-the-channable-app-in-shopify In addition, all issues affecting order synchronization have been resolved as connection renewal allows processing of all your orders

13. resolved Jun 02, 2026, 02:02 PM UTC

    We're closing this status page now, as the majority of technical issues have been resolved. We're still working with Shopify to get the Channable app up and running again on the Shopify App store. All workarounds, such as the temporary fix for metafields, still apply. You can stay up-to-date by following the changelog.

Read the full incident report →

Started May 12, 2026, 08:44 AM UTC· resolved May 12, 2026, 10:41 AM UTC

1. investigating May 12, 2026, 08:44 AM UTC

   We have identified an issue with background processing that started around 2:15 EST. We are investigating the cause.

2. investigating May 12, 2026, 08:49 AM UTC

   We are continuing to investigate this issue.

3. identified May 12, 2026, 09:04 AM UTC

   We have identified the cause and are working on mitigating the issue. Until the this mitigation is in place background jobs will continue processing with delays.

4. monitoring May 12, 2026, 09:32 AM UTC

   We have implemented a mitigation and are working through our backlog of background jobs. Imports, Channel exports and other jobs are being processed.

5. resolved May 12, 2026, 10:41 AM UTC

   This issue has been resolved. We are working through our backlog of background jobs at a normal pace again.

Read the full incident report →

Started Mar 04, 2026, 01:56 PM UTC· resolved Mar 04, 2026, 04:26 PM UTC

1. identified Mar 04, 2026, 01:56 PM UTC

   We have identified an issue which is causing some import jobs to fail to run. Affected jobs will show a red 'Failed' marker in the Channable tool. We have identified a likely cause of the issue and are working on a fix. Any affected import or export jobs will be rerun automatically once we have determined the issue is fixed.

2. monitoring Mar 04, 2026, 02:30 PM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Mar 04, 2026, 02:53 PM UTC

   The issue that was causing the import jobs has been determined to be fixed. We have been made aware of an additional issue which is preventing projects using the image editor from working correctly. Affected projects will also show a red 'Failed' marker in the Channable tool. We have identified the cause of this issue as well and are working on deploying a fix. Any affected export jobs will be rerun automatically once we have determined the issue is fixed.

4. monitoring Mar 04, 2026, 03:25 PM UTC

   The issue affecting the exports using the image editor has been confirmed to be fixed. All affected import and export jobs have been resubmitted and will be retried by our system shortly.

5. resolved Mar 04, 2026, 04:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2026, 03:22 PM UTC· resolved Feb 20, 2026, 04:31 PM UTC

1. investigating Feb 20, 2026, 03:22 PM UTC

   Issues loading and processing items causing the tool to sometimes not show pages correctly. We are investigating the scope of the problem at the moment. We can see that exports, rules and creatives are mainly affected.

2. monitoring Feb 20, 2026, 03:30 PM UTC

   Restarted affected services and we will monitor. Missed orders or offer updates will be picked up, although with a slight delay. Any delayed exports or imports will continue to run again.

3. resolved Feb 20, 2026, 04:31 PM UTC

   The incident has been resolved. No systems are currently affected anymore and processes are being caught up on. Do note that there still might be a small delay while we work through the backlog of tasks that got delayed.

Read the full incident report →

Started Jan 23, 2026, 11:46 AM UTC· resolved Jan 26, 2026, 01:13 PM UTC

1. monitoring Jan 23, 2026, 11:46 AM UTC

   Since January 20th, we have observed a reduction in performance for our Shopify order connections, occasionally resulting in the error message 'Unable to claim inventory' during order creation. Shopify is aware of this issue and is actively working on a solution. We have implemented measures to addressing this issue by increasing retries on order creation, to mitigate the impact. For any failed orders, the current workaround is to manually resend the Shopify order within our platform. We are monitoring the situation closely and will provide updates on this page as the situation evolves. Please note: This incident is isolated and does not affect any of our other integrations.

2. resolved Jan 26, 2026, 01:13 PM UTC

   This incident has been resolved. After an extended period of monitoring, we have confirmed that Shopify orders are once again being created successfully and error rates have returned to normal. All systems are fully operational. Thank you for your patience.

Read the full incident report →

Started Jan 19, 2026, 08:07 AM UTC· resolved Jan 19, 2026, 08:45 AM UTC

1. identified Jan 19, 2026, 08:07 AM UTC

   Our phone provider is experiencing issues with their authentication system. This means our support department is not reachable by telephone. We are still reachable through all other means

2. identified Jan 19, 2026, 08:45 AM UTC

   We are continuing to work on a fix for this issue.

3. resolved Jan 19, 2026, 08:45 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 03, 2025, 08:37 AM UTC· resolved Dec 03, 2025, 10:05 AM UTC

1. investigating Dec 03, 2025, 08:37 AM UTC

   We are currently investigating a report about Returns not working as expected for different Mirakl platforms (i.e. Carrefour, Fonq and Kruidvat among others). We are determining the impact as we speak. Exports to these channels or regular Order handling remain unaffected.

2. investigating Dec 03, 2025, 08:54 AM UTC

   We are continuing to investigate this issue.

3. resolved Dec 03, 2025, 10:05 AM UTC

   We have determined what caused the problem and changed our internal logic for handling Returns for the different Mirakl platforms. The system is now quicker and more robust. Handling of returns will continue and works as expected. Other features were fully unaffected.

Read the full incident report →

Started Nov 18, 2025, 12:43 PM UTC· resolved Nov 18, 2025, 06:12 PM UTC

1. identified Nov 18, 2025, 12:43 PM UTC

   We have identified that we are affected by an ongoing outage in the global Cloudflare network. While this incident is ongoing images using background removal or the image editor may not work and fail to load with a 500 server error. This means that platforms configured to load feeds with images processed through Channable will not be able to load them. Exported feeds themselves are unaffected at this time and are being updated normally. Cloudflare is providing updates for this outage at the following URL: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

2. monitoring Nov 18, 2025, 03:03 PM UTC

   Cloudflare has reported that a fix has been implemented for the outage, and we can confirm that the performance of the affected infrastructure has significantly improved. We are still monitoring the situation to conclude whether the effect on Channable's infrastructure has fully been resolved.

3. resolved Nov 18, 2025, 06:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 07, 2025, 08:51 AM UTC· resolved Nov 07, 2025, 10:17 AM UTC

1. investigating Nov 07, 2025, 08:51 AM UTC

   We are currently investigating a problem with our rule processing engine which leads to degraded performance of item processing in Channable. This means that any page where items are shown in Channable will not work as expected and might show signs of slowness.

2. investigating Nov 07, 2025, 08:58 AM UTC

   After some further complications, Channable is reported to be unreachable for certain users. We are working to add processing capacity in order to restore operations.

3. monitoring Nov 07, 2025, 09:03 AM UTC

   The issue was identified and our expected solution is having a positive effect on the recovery of the system. We are actively monitoring while the system recovers.

4. resolved Nov 07, 2025, 10:17 AM UTC

   After monitoring we concluded that our systems are operational again and back to their original state of working.

Read the full incident report →

Started Oct 09, 2025, 06:33 AM UTC· resolved Oct 09, 2025, 10:07 AM UTC

1. investigating Oct 09, 2025, 06:33 AM UTC

   We are currently investigating this issue.

2. monitoring Oct 09, 2025, 07:04 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 09, 2025, 10:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 26, 2025, 06:46 AM UTC· resolved Aug 27, 2025, 07:56 AM UTC

1. investigating Aug 26, 2025, 06:46 AM UTC

   We are currently investigating this issue.

2. investigating Aug 26, 2025, 07:15 AM UTC

   We are seeing an high backlog of failed imports that originate from the 'docs.google.com' domain. Because of this, other systems got backed up too. We are actively working on unclogging the backlog and getting systems operational again. The systems surrounding orders are unaffected.

3. investigating Aug 26, 2025, 07:19 AM UTC

   While we work to resolve the blockade, we were forced to pause our jobs system. So no importers or exporters are running at the moment, everything remains queued for now.

4. identified Aug 26, 2025, 08:24 AM UTC

   The jobs system is unpaused. All projects not in scope of the problem are unblocked and are running again. All projects relying on a Google Spreadsheet importer are still being blocked.

5. monitoring Aug 26, 2025, 02:22 PM UTC

   Google is rolling out a fix, projects relying on the Google Spreadsheet importer are no longer blocked. We will continue to monitor the status.

6. resolved Aug 27, 2025, 07:56 AM UTC

   After monitoring for a while we concluded that the problems have been resolved and systems are back to normal operation.

Read the full incident report →

Started Aug 14, 2025, 04:19 PM UTC· resolved Aug 16, 2025, 08:32 AM UTC

1. monitoring Aug 14, 2025, 04:19 PM UTC

   The image downloader is experiencing heavy load. We have applied performance improvements but it will take more time for us to fully catch up with the backlog. In the meantime, this might temporarily cause a `NOT DOWNLOADED YET` error to be shown for new images that we have not downloaded before.

2. monitoring Aug 15, 2025, 09:11 AM UTC

   We are continuing to monitor for any further issues.

3. resolved Aug 16, 2025, 08:32 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 13, 2025, 02:26 PM UTC· resolved Aug 20, 2025, 01:54 PM UTC

1. identified Aug 13, 2025, 02:26 PM UTC

   We are seeing an increase in failed exports because part of the creatives suite is not working as expected. We are actively working to resolve this problem, however for certain exports that use the Image Editor it could result in failures. The hosted feeds are unaffected, but won't be updated when this problem happens. Other parts of the tool, including the downloading of images, are not affected.

2. monitoring Aug 13, 2025, 02:56 PM UTC

   For a small number of projects, a small number of product image files have been causing problems. A temporary fix has been implemented, causing us to mark images that are affected by the problem to appear as `NOT AVAILABLE`. The items causing problems can be omitted by editing your Image Generation Safety settings in the feed, or you can choose to wait for the problem to be fully resolved.

3. resolved Aug 20, 2025, 01:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 07, 2025, 01:39 PM UTC· resolved Aug 08, 2025, 11:40 AM UTC

1. identified Aug 07, 2025, 01:39 PM UTC

   We are seeing delays in fetching images for our creatives suite. New images may be delayed by several hours. Images that have already been downloaded into our systems will function as normal. The problem has been identified and we are working on a solution.

2. monitoring Aug 07, 2025, 03:05 PM UTC

   A fix has been deployed and we are making progress towards our backlog. We expect to have caught up in a few more hours.

3. resolved Aug 08, 2025, 11:40 AM UTC

   Our backlog has been cleared and everything is operational.

Read the full incident report →

Started Jun 25, 2025, 10:33 AM UTC· resolved Jun 26, 2025, 11:29 AM UTC

1. identified Jun 25, 2025, 10:33 AM UTC

   We have identified an issue with Beslist stock updates. We have paused them for now and new updates will not be visible in the app. We will unpause them as soon as things are running smoothly again.

2. monitoring Jun 26, 2025, 10:00 AM UTC

   Beslist stock updates are being processed again, we will continue to monitor the situation.

3. resolved Jun 26, 2025, 11:29 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 18, 2025, 02:10 PM UTC· resolved Jun 19, 2025, 03:19 PM UTC

1. identified Jun 18, 2025, 02:10 PM UTC

   Cdiscount has reported a widespread outage on their systems: https://developer.octopia-io.net/seller-monitoring/ Channable is currently unable to sync offer listings or process orders for the Cdiscount marketplace as a result of this outage. Orders and offer synchronization will resume once the outage is resolved on Cdiscount's side. Real-time stock updates received during the outage will not be resubmitted after the outage is resolved. This incident does not affect any other marketplace.

2. monitoring Jun 19, 2025, 07:19 AM UTC

   Cdiscount has partially restored their services at June 18th 20:00 UTC: https://developer.octopia-io.net/seller-monitoring/ Channable's API exporters are operational again, but order connections and real-time stock updates are still affected by the outage. We will continue to monitor the restoration of operations.

3. resolved Jun 19, 2025, 03:19 PM UTC

   Cdiscount reported the problem to be resolved on their end as of 14:00 UTC. Channable's services are all operational again for Cdiscount.

Read the full incident report →

Started Jun 02, 2025, 09:21 AM UTC· resolved Jun 03, 2025, 07:58 AM UTC

1. monitoring Jun 02, 2025, 09:21 AM UTC

   Since Thursday 29/05 at 16:30 CEST, the Amazon repricer has been experiencing delayed repricing. This means that updated offer prices will take more time to reflect on Amazon. We have identified the problem and are now working through the repricing backlog. We expect it will take multiple hours to complete.

2. resolved Jun 03, 2025, 07:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 12, 2025, 04:28 PM UTC· resolved May 13, 2025, 10:56 AM UTC

1. investigating May 12, 2025, 04:28 PM UTC

   We are currently investigating an issue which is affecting our processing time for real-time stock updates via order connections. While this incident is ongoing stock updates for received orders may be delayed by several hours. This incident does not impact stock updates via channels.

2. identified May 13, 2025, 08:55 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring May 13, 2025, 09:42 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved May 13, 2025, 10:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2025, 02:23 PM UTC· resolved Apr 16, 2025, 07:44 PM UTC

1. investigating Apr 16, 2025, 02:23 PM UTC

   Our Support department is currently not available over the phone, because our call provider is experiencing issues. They have already posted their own status page as well: https://status.aircall.io/incidents/tvtssv8x3r9s We'll be monitoring the situation.

2. monitoring Apr 16, 2025, 02:24 PM UTC

   We'll be monitoring the status page from Aircall, while we wait for them to implement a fix.

3. monitoring Apr 16, 2025, 02:57 PM UTC

   Support agents report certain calls are coming through again. We hope to be back to full available as soon as possible.

4. resolved Apr 16, 2025, 07:44 PM UTC

   Aircall reported the issue to have been resolved completely.

Read the full incident report →

Started Mar 31, 2025, 01:27 PM UTC· resolved Mar 31, 2025, 02:47 PM UTC

1. identified Mar 31, 2025, 01:27 PM UTC

   We are seeing an increased number of failed exports for Google Ads. We are working to resolve this issue as we know what is causing this.

2. identified Mar 31, 2025, 02:33 PM UTC

   We are continuing to approach this problem with new solutions. A possible fix is being currently verified.

3. resolved Mar 31, 2025, 02:47 PM UTC

   We have found a working solution to the problem and we have resumed normal operations. All features are working as expected again.

Read the full incident report →