Istoricul incidentelor Ravelin

1. 20 octombrie 2026 la 08:08 UTCmonitoring

   Cardurile emise de Revolut cedează autentificarea 3DS. Se pare că există o problemă pe platforma Revolut. Puteți urmări statutul Revolut aici: [https://www.revolut.com/system-status/](https://www.revolut.com/system-status/ "https://www.revolut.com/system-status/") Cardurile altor emitenți sunt prelucrate în mod normal. Vom continua să monitorizăm situaţia cu atenţie. Ne pare rău pentru neplăceri.

2. 20 octombrie 2026 la 09:19 UTCmonitoring

   Sursa autentificărilor 3DS cu impact este o problemă a Platformei Google Cloud în regiunea Europa de Vest 2. [https://status.cloud.google.com/incidentes/Xs2XTHZAVC9YnafnPyzj](https://status.cloud.google.com/incidentes/Xs2XTHzavC9YnafnPyzj "https://status.cloud.google.com/incidens/Xs2XTHzavC9YnafnPyzj") Am observat că următoarele ACS ale emiţătorilor au fost afectate. • 3DS LOA ACS RELT 020301 01127 (Revolut) • 3DS LOA ACS OPES 020301 00996 (Openway Europe S.A) Vom continua să monitorizăm situaţia.

3. 20 octombrie 2026 la 13:52 UTCmonitoring

   Nu mai vedem un nivel ridicat de autentificare eșuată pentru carduri revolut. Cu toate acestea, pagina de stare Revolut și Platforma Google Cloud încă arată incidentul ca fiind în curs de desfășurare. Continuăm să monitorizăm platforma cu atenţie. Ne pare rău pentru neplăceri.

4. 21 octombrie 2026 la 07:59 UTCresolved

   Incidentul a fost rezolvat. Ne pare rău pentru neplăceri.

Traducere automată din actualizarea oficială a incidentului.

1. 3 septembrie 2026 la 11:01 UTCinvestigating

   Suntem conştienţi că unii utilizatori primesc erori atunci când accesează tabloul de bord Ravelin. În prezent investigăm cauza și vom posta actualizări aici, după cum știm mai multe.

2. 3 septembrie 2026 la 11:12 UTCinvestigating

   Ne-am întors modificările care au cauzat erorile tabloului de bord, și a văzut erorile opri la aproximativ 10:45 UTC. Continuăm să investigăm cauza principală a problemei.

3. 3 septembrie 2026 la 11:27 UTCmonitoring

   Tabloul de bord este din nou operaţional, erorile s-au oprit. Continuăm să monitorizăm orice alte erori de bord şi continuăm să investigăm cauza principală.

4. 3 septembrie 2026 la 16:38 UTCresolved

   Incidentul anterior a fost rezolvat. Ne pare rău pentru neplăceri.

Traducere automată din actualizarea oficială a incidentului.

1. 1 septembrie 2026 la 15:21 UTCinvestigating

   Avem rate de eroare crescute de la API-ul nostru 3DS. Traficul cu sediul în SUA este redirecționat către grupul nostru UE pentru procesare, astfel încât să puteți experimenta perioade de răspuns ridicate. Suntem în curs de reparare a grupului nostru american. Investigăm pentru a descoperi cauza. Vă rugăm să verificați aici pentru actualizări suplimentare.

2. 1 septembrie 2026 la 15:44 UTCmonitoring

   Grupul nostru american s-a recuperat şi procesează traficul normal din nou. Google a identificat sistemul emis descris mai jos: Nor privat virtual (VPC) - comunicare VM la VM - Comunicare VM la VM peste IP interne În următoarele locații: - asia- est1 (activ) - noi-central1 (activ) Acest lucru a avut un impact asupra conectivității componentelor noastre care rulează în regiunea noastră centrală1. Vom continua să monitorizăm situaţia.

3. 1 septembrie 2026 la 16:22 UTCmonitoring

   Google a postat acum detalii despre incidentul în curs aici: [https://status.cloud.google.com/incidente/J5ia5t9p3g9Q5Wi7r8Ev](https://status.cloud.google.com/incidente/J5ia5t9p3g9Q5Wi7r8Ev "https://status.cloud.google.com/incidente/J5ia5t9p9Q5Wi7r8Ev") Vom continua să monitorizăm API-ul 3DS. Ne pare rău pentru neplăceri.

4. 1 septembrie 2026 la 17:01 UTCresolved

   Incidentul anterior a fost rezolvat. Ne pare rău pentru neplăceri.

Traducere automată din actualizarea oficială a incidentului.

1. 9 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 17:42 UTCmonitoring

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

4. 9 iulie 2026 la 19:31 UTCresolved

   The incident has been resolved.

1. 18 iunie 2026 la 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 iunie 2026 la 16:11 UTCresolved

   API performance has returned to expected performance levels

1. 2 martie 2026 la 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 martie 2026 la 16:48 UTCresolved

   The dashboard is now fully operational.

1. 21 ianuarie 2026 la 16:45 UTCidentified

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

2. 21 ianuarie 2026 la 16:45 UTCresolved

   This is now resolved

1. 21 august 2025 la 14:05 UTCinvestigating

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

2. 21 august 2025 la 14:30 UTCmonitoring

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

3. 21 august 2025 la 15:29 UTCresolved

   Our system is fully operational

1. 18 august 2025 la 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 august 2025 la 15:13 UTCmonitoring

   Response times have returned to normal levels.

3. 18 august 2025 la 15:29 UTCresolved

   The issue is resolved

1. 12 iunie 2025 la 18:11 UTCinvestigating

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

2. 12 iunie 2025 la 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 iunie 2025 la 18:55 UTCidentified

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

4. 12 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 21:10 UTCresolved

   Our system is fully operational.

1. 22 aprilie 2025 la 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 aprilie 2025 la 12:36 UTCmonitoring

   Response times have recovered and we are monitoring the situation.

3. 22 aprilie 2025 la 13:28 UTCresolved

   Latency has returned to normal levels.

4. 22 aprilie 2025 la 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 februarie 2025 la 15:22 UTCresolved

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

1. 6 septembrie 2024 la 13:50 UTCinvestigating

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

2. 6 septembrie 2024 la 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 septembrie 2024 la 15:31 UTCresolved

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

4. 6 septembrie 2024 la 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 septembrie 2024 la 16:25 UTCmonitoring

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

6. 6 septembrie 2024 la 17:44 UTCresolved

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

1. 7 august 2024 la 12:28 UTCidentified

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

2. 7 august 2024 la 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 august 2024 la 13:33 UTCresolved

   This is now resolved.

1. 1 mai 2024 la 15:52 UTCinvestigating

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

2. 1 mai 2024 la 15:55 UTCinvestigating

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

3. 1 mai 2024 la 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 mai 2024 la 16:29 UTCresolved

   The incident is now resolved

1. 22 aprilie 2024 la 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 aprilie 2024 la 09:55 UTCidentified

   We have identified the problem and are deploying a fix.

3. 22 aprilie 2024 la 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 aprilie 2024 la 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 februarie 2024 la 08:36 UTCinvestigating

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

2. 28 februarie 2024 la 09:16 UTCmonitoring

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

3. 28 februarie 2024 la 13:23 UTCresolved

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

1. 6 februarie 2024 la 11:57 UTCinvestigating

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

2. 6 februarie 2024 la 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 februarie 2024 la 08:51 UTCresolved

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

1. 1 februarie 2024 la 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 februarie 2024 la 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 februarie 2024 la 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 februarie 2024 la 11:57 UTCresolved

   This was resolved late last week

1. 5 decembrie 2023 la 10:35 UTCinvestigating

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

2. 5 decembrie 2023 la 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 decembrie 2023 la 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 decembrie 2023 la 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 decembrie 2023 la 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 decembrie 2023 la 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 decembrie 2023 la 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 decembrie 2023 la 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