Cronologia delle interruzioni di Ravelin

1. 20 ottobre 2026 alle ore 08:08 UTCmonitoring

   Revolut emesso carte sono in fallimento 3DS autenticazione. Sembra che ci sia un problema sulla piattaforma Revolut. È possibile monitorare lo stato di Revolut qui: [https://www.revolut.com/system-status/](https://www.revolut.com/system-status/ "https://www.revolut.com/system-status/") Le carte di altri emittenti vengono normalmente elaborate. Continueremo a monitorare attentamente la situazione. Ci dispiace per qualsiasi inconveniente.

2. 20 ottobre 2026 alle ore 09:19 UTCmonitoring

   La fonte di autenticazione 3DS è un problema sulla piattaforma Google Cloud nella regione Europa West 2. [https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj](https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj Abbiamo notato i seguenti Emittenti ACS sono stati influenzati. • 3DS LOA ACS RELT 020301 01127 (Rivoluto) • 3DS LOA ACS OPES 020301 00996 (Openway Europe S.A) Continueremo a monitorare la situazione.

3. 20 ottobre 2026 alle ore 13:52 UTCmonitoring

   Non vediamo più un alto livello di autenticazione fallita per le schede Revolut. Tuttavia la pagina di stato Revolut e Google Cloud Platform stanno ancora mostrando l'incidente come in corso. Stiamo continuando a monitorare attentamente la piattaforma. Ci dispiace per qualsiasi inconveniente.

4. 21 ottobre 2026 alle ore 07:59 UTCresolved

   L'incidente è stato risolto. Ci dispiace per qualsiasi inconveniente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 3 settembre 2026 alle ore 11:01 UTCinvestigating

   Siamo consapevoli che alcuni utenti stanno ricevendo errori quando si accede al cruscotto Ravelin. Stiamo attualmente indagando sulla causa e pubblicheremo aggiornamenti qui come sappiamo di più.

2. 3 settembre 2026 alle ore 11:12 UTCinvestigating

   Abbiamo rirottato le modifiche che stavano causando gli errori del cruscotto, e abbiamo visto gli errori fermarsi a circa 10:45 UTC. Stiamo continuando a indagare sulla causa principale del problema.

3. 3 settembre 2026 alle ore 11:27 UTCmonitoring

   Il cruscotto è di nuovo operativo, gli errori si sono fermati. Stiamo continuando a monitorare per ulteriori errori di cruscotto e continuando a indagare sulla causa principale.

4. 3 settembre 2026 alle ore 16:38 UTCresolved

   Il precedente incidente è stato risolto. Ci dispiace per qualsiasi inconveniente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 1 settembre 2026 alle ore 15:21 UTCinvestigating

   Stiamo vivendo tassi di errore aumentati dalla nostra API 3DS. Il traffico statunitense viene reindirizzato al nostro cluster UE per l'elaborazione, in modo da poter sperimentare tempi di risposta elevati. Attualmente stiamo riparando il nostro cluster statunitense. Stiamo indagando per scoprire la causa. Si prega di controllare qui per ulteriori aggiornamenti.

2. 1 settembre 2026 alle ore 15:44 UTCmonitoring

   # Il nostro cluster americano ha recuperato e sta elaborando il traffico normalmente di nuovo. Google ha identificato l'emissione descritta di seguito: Virtual Private Cloud (VPC) - comunicazione VM a VM - comunicazione VM a VM su IP interni Nelle seguenti località: - asia-est1 (attivo) - us-central1 (attivo) Questo ha colpito la connettività dei nostri componenti che eseguono la regione us-central1. Continueremo a monitorare la situazione. #

3. 1 settembre 2026 alle ore 16:22 UTCmonitoring

   Google ha pubblicato i dettagli dell'incidente in corso qui: [https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Eglev "https://status.com. Continueremo a monitorare l'API 3DS. Ci dispiace per qualsiasi inconveniente.

4. 1 settembre 2026 alle ore 17:01 UTCresolved

   Il precedente incidente è stato risolto. Ci dispiace per qualsiasi inconveniente.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 9 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 17:42 UTCmonitoring

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

4. 9 luglio 2026 alle ore 19:31 UTCresolved

   The incident has been resolved.

1. 18 giugno 2026 alle ore 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 giugno 2026 alle ore 16:11 UTCresolved

   API performance has returned to expected performance levels

1. 2 marzo 2026 alle ore 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 marzo 2026 alle ore 16:48 UTCresolved

   The dashboard is now fully operational.

1. 21 gennaio 2026 alle ore 16:45 UTCidentified

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

2. 21 gennaio 2026 alle ore 16:45 UTCresolved

   This is now resolved

1. 21 agosto 2025 alle ore 14:05 UTCinvestigating

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

2. 21 agosto 2025 alle ore 14:30 UTCmonitoring

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

3. 21 agosto 2025 alle ore 15:29 UTCresolved

   Our system is fully operational

1. 18 agosto 2025 alle ore 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 agosto 2025 alle ore 15:13 UTCmonitoring

   Response times have returned to normal levels.

3. 18 agosto 2025 alle ore 15:29 UTCresolved

   The issue is resolved

1. 12 giugno 2025 alle ore 18:11 UTCinvestigating

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

2. 12 giugno 2025 alle ore 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 giugno 2025 alle ore 18:55 UTCidentified

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

4. 12 giugno 2025 alle ore 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 giugno 2025 alle ore 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 giugno 2025 alle ore 21:10 UTCresolved

   Our system is fully operational.

1. 22 aprile 2025 alle ore 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 aprile 2025 alle ore 12:36 UTCmonitoring

   Response times have recovered and we are monitoring the situation.

3. 22 aprile 2025 alle ore 13:28 UTCresolved

   Latency has returned to normal levels.

4. 22 aprile 2025 alle ore 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 febbraio 2025 alle ore 15:22 UTCresolved

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

1. 6 settembre 2024 alle ore 13:50 UTCinvestigating

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

2. 6 settembre 2024 alle ore 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 settembre 2024 alle ore 15:31 UTCresolved

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

4. 6 settembre 2024 alle ore 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 settembre 2024 alle ore 16:25 UTCmonitoring

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

6. 6 settembre 2024 alle ore 17:44 UTCresolved

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

1. 7 agosto 2024 alle ore 12:28 UTCidentified

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

2. 7 agosto 2024 alle ore 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 agosto 2024 alle ore 13:33 UTCresolved

   This is now resolved.

1. 1 maggio 2024 alle ore 15:52 UTCinvestigating

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

2. 1 maggio 2024 alle ore 15:55 UTCinvestigating

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

3. 1 maggio 2024 alle ore 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 maggio 2024 alle ore 16:29 UTCresolved

   The incident is now resolved

1. 22 aprile 2024 alle ore 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 aprile 2024 alle ore 09:55 UTCidentified

   We have identified the problem and are deploying a fix.

3. 22 aprile 2024 alle ore 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 aprile 2024 alle ore 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 febbraio 2024 alle ore 08:36 UTCinvestigating

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

2. 28 febbraio 2024 alle ore 09:16 UTCmonitoring

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

3. 28 febbraio 2024 alle ore 13:23 UTCresolved

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

1. 6 febbraio 2024 alle ore 11:57 UTCinvestigating

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

2. 6 febbraio 2024 alle ore 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 febbraio 2024 alle ore 08:51 UTCresolved

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

1. 1 febbraio 2024 alle ore 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 febbraio 2024 alle ore 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 febbraio 2024 alle ore 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 febbraio 2024 alle ore 11:57 UTCresolved

   This was resolved late last week

1. 5 dicembre 2023 alle ore 10:35 UTCinvestigating

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

2. 5 dicembre 2023 alle ore 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 dicembre 2023 alle ore 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 dicembre 2023 alle ore 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 dicembre 2023 alle ore 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 dicembre 2023 alle ore 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 dicembre 2023 alle ore 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 dicembre 2023 alle ore 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