Histórico de interrupções do Ravelin

1. 20 Here 2026 da 08:08 UTCmonitoring

   Os cartões emitidos pela Revolut estão falhando as autenticaçãos 3DS. Parece haver um problema na plataforma Revolut. Você pode rastrear o status de Revolut aqui: [https://www.revolut.com/system-status/](https://www.revolut.com/system-status/ "https://www.revolut.com/system-status/") Cartões de outros emitentes estão sendo processados normalmente. Continuaremos a acompanhar atentamente a situação. Lamentamos qualquer inconveniente.

2. 20 Here 2026 da 09:19 UTCmonitoring

   A fonte de autenticação 3DS impactada é um problema na Plataforma Google Cloud na região Europa Oeste 2. [https://status.cloud.google.com/incidentes/Xs2XTHzAVC9YnafnPyzj](https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj "https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj") Notamos que os seguintes ACS dos Emissores foram impactados. • 3DS LOA ACS RELT 020301 01127 (Revolução) • 3DS LOA ACS OPES 020301 00996 (Openway Europe S.A.) Continuaremos a acompanhar a situação.

3. 20 Here 2026 da 13:52 UTCmonitoring

   Não estamos mais vendo um alto nível de autenticação falhada para as cartas Revolut. No entanto, a página de status Revolut e o Google Cloud Platform ainda estão mostrando o incidente como contínuo. Continuamos a monitorizar cuidadosamente a plataforma. Lamentamos qualquer inconveniente.

4. 21 Here 2026 da 07:59 UTCresolved

   O incidente já foi resolvido. Lamentamos qualquer inconveniente.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Gwengolo 2026 da 11:01 UTCinvestigating

   Sabemos que alguns usuários estão recebendo erros ao acessar o painel Ravelin. Atualmente estamos investigando a causa e vamos postar atualizações aqui como sabemos mais.

2. 3 Gwengolo 2026 da 11:12 UTCinvestigating

   Nós retrocedemos as mudanças que estavam causando os erros do painel, e vimos os erros pararem em aproximadamente 10:45 UTC. Continuamos a investigar a causa principal da questão.

3. 3 Gwengolo 2026 da 11:27 UTCmonitoring

   O painel está operacional novamente, os erros pararam. Continuamos a monitorar quaisquer erros no painel e a investigar a causa raiz.

4. 3 Gwengolo 2026 da 16:38 UTCresolved

   O incidente anterior já foi resolvido. Lamentamos qualquer inconveniente.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gwengolo 2026 da 15:21 UTCinvestigating

   Estamos tendo taxas de erro aumentadas da nossa API 3DS. O tráfego baseado nos EUA está a ser reencaminhado para o nosso cluster da UE para processamento, pelo que poderá experimentar tempos de resposta elevados. Estamos atualmente no processo de reparação do nosso cluster EUA. Estamos a investigar para descobrir a causa. Por favor, verifique aqui para mais atualizações.

2. 1 Gwengolo 2026 da 15:44 UTCmonitoring

   «`` Nosso cluster dos EUA recuperou e está processando o tráfego normalmente novamente. A Google identificou a emissão descrita abaixo: Nuvem privada virtual (VPC) - Comunicação VM para VM - Comunicação VM para VM sobre IPs internos Nos seguintes locais: - Ásia-Leste1 (activa) - us-central1 (activa) Isso afetou a conectividade de nossos componentes que executam a região centro-americana1. Continuaremos a acompanhar a situação. «``

3. 1 Gwengolo 2026 da 16:22 UTCmonitoring

   O Google publicou agora detalhes do incidente em curso aqui: [https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev") Continuaremos a monitorar a API 3DS. Lamentamos qualquer inconveniente.

4. 1 Gwengolo 2026 da 17:01 UTCresolved

   O incidente anterior já foi resolvido. Lamentamos qualquer inconveniente.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Gouere 2026 da 17:10 UTCinvestigating

   We are seeing a small number of errors periodically due to an issue in our aggregations service. We are currently investigating.

2. 9 Gouere 2026 da 17:34 UTCidentified

   We have identified the issue and have mitigations in place such that the api should no longer be returning errors. We are continuing to monitor and address the root cause.

3. 9 Gouere 2026 da 17:42 UTCmonitoring

   We have stopped returning 500s. We are monitoring the situation.

4. 9 Gouere 2026 da 19:31 UTCresolved

   The incident has been resolved.

1. 18 Mezheven 2026 da 15:47 UTCmonitoring

   An issue regarding datalist configuration caused an increase in errors returned from the PSP API. This has now been resolved and we are monitoring.

2. 18 Mezheven 2026 da 16:11 UTCresolved

   API performance has returned to expected performance levels

1. 2 Meurzh 2026 da 16:40 UTCmonitoring

   Between 14:46 and 15:47 (UTC), some clients experienced 500 errors when accessing the Explore Customers and Orders features in the Dashboard. This was caused by a code deployment that inadvertently removed functionality required for filters in Explore. We have rolled back the problematic deployment and confirmed that the Explore feature is now functioning normally. All services have been restored to their previous stable state.

2. 2 Meurzh 2026 da 16:48 UTCresolved

   The dashboard is now fully operational.

1. 21 Genver 2026 da 16:45 UTCidentified

   An issue with a database update caused a subset of requests to return a 500 error.

2. 21 Genver 2026 da 16:45 UTCresolved

   This is now resolved

1. 21 Eost 2025 da 14:05 UTCinvestigating

   We're seeing elevated scoring response times at the moment. We are investigating as a priority

2. 21 Eost 2025 da 14:30 UTCmonitoring

   Response times have returned to normal. We are continuing to investigate and are monitoring the situation.

3. 21 Eost 2025 da 15:29 UTCresolved

   Our system is fully operational

1. 18 Eost 2025 da 15:09 UTCidentified

   We are seeing some elevated latency on the API. We have identified the issue and are looking to remedy it ASAP.

2. 18 Eost 2025 da 15:13 UTCmonitoring

   Response times have returned to normal levels.

3. 18 Eost 2025 da 15:29 UTCresolved

   The issue is resolved

1. 12 Mezheven 2025 da 18:11 UTCinvestigating

   We are experiencing a partial API outage. We are investigating and will provide updates when we have more information.

2. 12 Mezheven 2025 da 18:29 UTCinvestigating

   It appears GCP, where Ravelin is hosted, is experiencing an outage. This is also affecting the Ravelin dashboard and the PCI and 3DS API. We are continuing to investigate.

3. 12 Mezheven 2025 da 18:55 UTCidentified

   This appears to be a widespread issue with GCP, our cloud provider. We are continuing to look into it.

4. 12 Mezheven 2025 da 19:18 UTCmonitoring

   We are seeing the system start to recover, but are still seeing elevated response times. We expect this to continue as we retry failed requests. We are continuing to monitor and investigate.

5. 12 Mezheven 2025 da 19:43 UTCmonitoring

   Our system appears to have recovered. Error responses have stopped and response times have returned to normal. We are continuing to monitor the situation.

6. 12 Mezheven 2025 da 21:10 UTCresolved

   Our system is fully operational.

1. 22 Ebrel 2025 da 11:50 UTCidentified

   We are seeing elevated latency on the core Ravelin API. We have identified the issue and you should see latency coming down. We apologise for the issue.

2. 22 Ebrel 2025 da 12:36 UTCmonitoring

   Response times have recovered and we are monitoring the situation.

3. 22 Ebrel 2025 da 13:28 UTCresolved

   Latency has returned to normal levels.

4. 22 Ebrel 2025 da 16:26 UTCresolved

   One of our server nodes in our Kubernetes cluster was running with high CPU for all the pods provisioned on that node. We are unsure the cause at the moment (could be a noisy neighbour, could be hardware issues, etc) but we have removed that node which solved the issue.

1. 19 Cʼhwevrer 2025 da 15:22 UTCresolved

   Our API was generating 500 errors for about six minutes due to a delay in configuration between services

1. 6 Gwengolo 2024 da 13:50 UTCinvestigating

   We are seeing an increase in error responses from our API. We are currently investigating.

2. 6 Gwengolo 2024 da 14:18 UTCmonitoring

   We have identified the source of the issue and have taken steps to reduce the errors. Errors rates have now dropped. We are continuing to monitor the situation.

3. 6 Gwengolo 2024 da 15:31 UTCresolved

   The API outage has been resolved, and all services are now fully operational.

4. 6 Gwengolo 2024 da 16:04 UTCinvestigating

   We are now seeing issues accessing the Ravelin dashboard. We are also seeing a slight increase in API response times. We are not sure if this is related to the previous issue but are investigating.

5. 6 Gwengolo 2024 da 16:25 UTCmonitoring

   We have made some changes which we believe have addressed the issues. We are continuing to monitor the situation.

6. 6 Gwengolo 2024 da 17:44 UTCresolved

   We have not seen any further issues since our previous update. The dashboard and API are both operating normally.

1. 7 Eost 2024 da 12:28 UTCidentified

   We are experiencing errors on the fraud API. The issue has been identified and is being fixed now.

2. 7 Eost 2024 da 12:35 UTCmonitoring

   Things have recovered after a roll back of a deploy. We are monitoring the situation but expect no more errors at this point.

3. 7 Eost 2024 da 13:33 UTCresolved

   This is now resolved.

1. 1 Mae 2024 da 15:52 UTCinvestigating

   We're investigating an issue with connections to Ravelin's dashboard.

2. 1 Mae 2024 da 15:55 UTCinvestigating

   We seem to be getting some connections to the dashboard but still investigating the issue.

3. 1 Mae 2024 da 16:25 UTCmonitoring

   The issue has been identified as an increased load on the database due to an error case in a recent deploy. This has been mitigated and we are monitoring the issue

4. 1 Mae 2024 da 16:29 UTCresolved

   The incident is now resolved

1. 22 Ebrel 2024 da 09:19 UTCinvestigating

   We are currently investigating an issue with the thresholds displayed in the threshold configuration section of the dashboard. This was due to a recent config migration. We do not believe this is having any effect on the thresholds used for scoring. Please do not make any threshold changes via the dashboard based on the current values. We are currently investigating and working on a fix.

2. 22 Ebrel 2024 da 09:55 UTCidentified

   We have identified the problem and are deploying a fix.

3. 22 Ebrel 2024 da 10:11 UTCmonitoring

   Our fix has been deployed and the correct thresholds should now be displayed in the dashboard. We are continuing to monitor the situation. When rolling out the threshold config change we did also see a temporary issue with scoring requests between 08:20 and 08:25 UTC, when a small number of requests failed with a 500 response code. We will also be investigating this as part of this incident.

4. 22 Ebrel 2024 da 12:50 UTCresolved

   The issue has been resolved. We will continue to investigate the cause for this issue and provide an update on any further findings.

1. 28 Cʼhwevrer 2024 da 08:36 UTCinvestigating

   We are currently investigating issues loading the rules page on the dashboard.

2. 28 Cʼhwevrer 2024 da 09:16 UTCmonitoring

   We are continuing to monitor the situation but the affected component has recovered

3. 28 Cʼhwevrer 2024 da 13:23 UTCresolved

   This incident is resolved. It was an issue with queries not progressing within Bigquery. Bigquery has since recovered

1. 6 Cʼhwevrer 2024 da 11:57 UTCinvestigating

   We are seeing elevated errors on the API. We are investigating

2. 6 Cʼhwevrer 2024 da 12:07 UTCmonitoring

   This has settled down. It was caused by a short spike in latency on our primary database, we are continuing to investigate.

3. 7 Cʼhwevrer 2024 da 08:51 UTCresolved

   This incident has resolved. We are continuing to monitor and investigate isolated cases of increased latency.

1. 1 Cʼhwevrer 2024 da 16:59 UTCmonitoring

   We're seeing timeouts loading data from our primary database to view in the dashboard. We've scaled this up a little and are monitoring the situation. Although the same database is used for scoring that has not been effected so far

2. 1 Cʼhwevrer 2024 da 19:23 UTCmonitoring

   We continue to monitor the timeouts related to loading data from our primary database. Our primary and secondary databases have been swapped. That caused a spike in response times but those are now improving.

3. 2 Cʼhwevrer 2024 da 16:48 UTCmonitoring

   We're continuing to see intermittent performance issues with our main database. We've now seen it affect our main API as well as the dashboard. The overall impact remains small. We've scaled up the database server capacity and are monitoring the situation

4. 6 Cʼhwevrer 2024 da 11:57 UTCresolved

   This was resolved late last week

1. 5 Kerzu 2023 da 10:35 UTCinvestigating

   Searching in the dashboard will occasionally timeout or be slower than expected. We are currently investigating.

2. 5 Kerzu 2023 da 11:06 UTCidentified

   We are aware of a slow down in our search database. We are attempting to scale further nodes and investigate root cause.

3. 5 Kerzu 2023 da 11:59 UTCidentified

   We are still investigating and managing node scaling on our search database. We will update you further as things progress.

4. 5 Kerzu 2023 da 12:55 UTCidentified

   We have done some mitigation that will improve search latency for the dashboard but data will be delayed. We are continuing to work on the core database issue.

5. 5 Kerzu 2023 da 14:12 UTCidentified

   Mitigation is still ongoing. Search times have improved and index latency is improving. Not recovered yet but going in the right direction.

6. 5 Kerzu 2023 da 14:41 UTCmonitoring

   Index time has gone back to nominal latency. We are currently draining queues of backfilled data. Expect to have search data up to date shortly

7. 5 Kerzu 2023 da 15:06 UTCmonitoring

   We've fixed the elastic search database cluster issues, so we are no longer experiencing any errors or timeouts. However the cluster is not running completely up to date yet so there will be stale data returned on searches. We're running through the queues to fix that, and expect them to finish in ~2hrs by 5pm GMT

8. 5 Kerzu 2023 da 16:03 UTCresolved

   All data has now been updated. Searching within the dashboard should be up to date and running as normal. Thanks for your patience