Ravelin kesinti geçmişi

1. 20 Ekim 2026 08:08 UTCmonitoring

   Revolut yayınlanan kartlar 3DS kimlik doğrulamaları başarısız oluyor. Revolut platformunda bir sorun gibi görünüyor. Revolut statüsünü buradan takip edebilirsiniz: [https://www.revolut.com/system-status/] (https://www.revolut.com/system-status/ "https://www.revolut.com/system-status/") Diğer sorunculardan gelen kartlar normalde işlenir. Durumu dikkatle izlemeye devam edeceğiz. Herhangi bir rahatsızlık için üzgünüz.

2. 20 Ekim 2026 09:19 UTCmonitoring

   Etkilenen 3DS doğrulama kaynağı, bölgedeki Avrupa West 2. [https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj] (https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj Aşağıdaki Soruncuların ACS'nin etkilendiğini fark ettik. • 3DS LOA ACS RELT 020301 01127 (Revolut) • 3DS LOA ACS OPES 020301 00996 (Openway Europe S.A) Durumu izlemeye devam edeceğiz.

3. 20 Ekim 2026 13:52 UTCmonitoring

   Artık Revolut kartları için yüksek sayıda başarısız kimlik doğrulama görüyoruz. Ancak Revolut durumu sayfası ve Google Cloud Platform hala devam eden olayı gösteriyor. Platformu dikkatle izlemeye devam ediyoruz. Herhangi bir rahatsızlık için üzgünüz.

4. 21 Ekim 2026 07:59 UTCresolved

   Olay şimdi çözüldü. Herhangi bir rahatsızlık için üzgünüz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 3 Eylül 2026 11:01 UTCinvestigating

   Bazı kullanıcıların Ravelin paniğe eriştiğinde hata aldıklarını biliyoruz. Şu anda nedenini araştırıyoruz ve daha fazla bildiğimiz gibi güncellemeler yayınlayacağız.

2. 3 Eylül 2026 11:12 UTCinvestigating

   Pano hatalarına neden olan değişiklikleri geri aldık ve hataları yaklaşık 10:45 UTC'de durdurduk. Sorunun kök nedenini incelemeye devam ediyoruz.

3. 3 Eylül 2026 11:27 UTCmonitoring

   Pano tekrar çalışır, hatalar durdu. Daha fazla pano hataları için izlemeye devam ediyoruz ve kök nedenini araştırmaya devam ediyoruz.

4. 3 Eylül 2026 16:38 UTCresolved

   Önceki olay şimdi çözüldü. Herhangi bir rahatsızlık için üzgünüz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 1 Eylül 2026 15:21 UTCinvestigating

   3DS API'mizden artan hata oranları yaşıyoruz. ABD tabanlı trafik, işlem için AB kümemize geri dönüyor, bu yüzden yüksek yanıt süreleri deneyimleyebilirsiniz. Şu anda ABD kümemizi tamir etme sürecindeyiz. Nedeni keşfetmeye çalışıyoruz. Lütfen daha fazla güncelleme için buraya geri kontrol edin.

2. 1 Eylül 2026 15:44 UTCmonitoring

   " ABD kümemiz kurtarıldı ve normal olarak tekrar işlem trafiğidir. Google aşağıda açıklanan yayınları belirledi: Sanal Özel Bulut (VPC) VM iletişim için VM - İç IP üzerinden VM iletişim için VM Aşağıdaki yerlerde: - asia-east1 (aktif) - Us-merkez1 (aktif) Bu, bileşenlerimizin bağlantılarını bizi merkezi1 bölgesine taşıdı. Durumu izlemeye devam edeceğiz. "

3. 1 Eylül 2026 16:22 UTCmonitoring

   Google şimdi devam eden olayın ayrıntılarını yayınladı: [https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8](https://status.cloud.google.com/Ev) 3DS API'sini izlemeye devam edeceğiz. Herhangi bir rahatsızlık için üzgünüz.

4. 1 Eylül 2026 17:01 UTCresolved

   Önceki olay şimdi çözüldü. Herhangi bir rahatsızlık için üzgünüz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

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

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

4. 9 Temmuz 2026 19:31 UTCresolved

   The incident has been resolved.

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

   API performance has returned to expected performance levels

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

   The dashboard is now fully operational.

1. 21 Ocak 2026 16:45 UTCidentified

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

2. 21 Ocak 2026 16:45 UTCresolved

   This is now resolved

1. 21 Ağustos 2025 14:05 UTCinvestigating

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

2. 21 Ağustos 2025 14:30 UTCmonitoring

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

3. 21 Ağustos 2025 15:29 UTCresolved

   Our system is fully operational

1. 18 Ağustos 2025 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 Ağustos 2025 15:13 UTCmonitoring

   Response times have returned to normal levels.

3. 18 Ağustos 2025 15:29 UTCresolved

   The issue is resolved

1. 12 Haziran 2025 18:11 UTCinvestigating

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

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

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

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

   Our system is fully operational.

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

   Response times have recovered and we are monitoring the situation.

3. 22 Nisan 2025 13:28 UTCresolved

   Latency has returned to normal levels.

4. 22 Nisan 2025 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 Şubat 2025 15:22 UTCresolved

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

1. 6 Eylül 2024 13:50 UTCinvestigating

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

2. 6 Eylül 2024 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 Eylül 2024 15:31 UTCresolved

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

4. 6 Eylül 2024 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 Eylül 2024 16:25 UTCmonitoring

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

6. 6 Eylül 2024 17:44 UTCresolved

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

1. 7 Ağustos 2024 12:28 UTCidentified

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

2. 7 Ağustos 2024 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 Ağustos 2024 13:33 UTCresolved

   This is now resolved.

1. 1 Mayıs 2024 15:52 UTCinvestigating

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

2. 1 Mayıs 2024 15:55 UTCinvestigating

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

3. 1 Mayıs 2024 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 Mayıs 2024 16:29 UTCresolved

   The incident is now resolved

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

   We have identified the problem and are deploying a fix.

3. 22 Nisan 2024 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 Nisan 2024 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 Şubat 2024 08:36 UTCinvestigating

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

2. 28 Şubat 2024 09:16 UTCmonitoring

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

3. 28 Şubat 2024 13:23 UTCresolved

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

1. 6 Şubat 2024 11:57 UTCinvestigating

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

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

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

1. 1 Şubat 2024 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 Şubat 2024 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 Şubat 2024 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 Şubat 2024 11:57 UTCresolved

   This was resolved late last week

1. 5 Aralık 2023 10:35 UTCinvestigating

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

2. 5 Aralık 2023 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 Aralık 2023 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 Aralık 2023 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 Aralık 2023 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 Aralık 2023 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 Aralık 2023 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 Aralık 2023 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