Previous incidents

We have identified the root cause of the issue as non-critical and created a ticket to fix the underlying problem. The API is fully operational.

A fix has been deployed and the API is fully operational again.

We have identified the root cause of the issue and are implementing a fix.

We have identified the root cause of the issue and are implementing a fix.

We have identified the root cause and are working on a fix to avoid future similar scenarios.

The fix has been implemented the issue is now resolved.

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue and deployed a fix, the API is fully operational again. A misconfiguration in the exchange rate API manifest was deployed on May 23, 2026 at 0:47 AM UTC that attached the exchange rate API to a private overlay network, cutting of the service's access to in/outbound public internet. For the brief moment between May 23, 2026 23:23 PM UTC and May 23, 2026 0:47 AM UTC, the service utilized the window to backfill currency pair rates but was hindered f...

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

We have identified the root cause of the issue being the exchange rate API unavailability due to a network misconfiguration in the production overlay manifest for the cluster. A fix has been deployed making the exchange rate API available and the issue is now resolved.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

There was a problem importing data into the live database with a yet unknown reason for request failures. The imported data has been removed and the API works as expected again.

We have identified the root cause of the issue and deployed a fix. The issue has been mitigated and the API is fully operational now.

The issue has been identified and a fix has been deployed. The API is now operational.

The portal has been updated to use the new SDK version and is operational now.