Ravelin 中断历史

1. 2026年10月20日 UTC 08:08monitoring

   Revolut已发卡失败3DS认证. Revolut平台上似乎有一个问题。 您可以在此追踪Revolut的地位: [https://www.revolut.com/ system-status/] (https://www.revolut.com/ system-status/ "https://www.revolut.com/ system-status/"). 其他发卡人的卡片正在正常处理. 我们将继续认真监测局势。 我们为任何不便感到遗憾.

2. 2026年10月20日 UTC 09:19monitoring

   受影响3DS认证的来源是Google Cloud平台在欧洲西部2区的一期. [https://status.cloud.google.com/incidents/Xs2XTHZAVC9YnafnPyzj] (https://status.cloud.google.com/incidents/Xs2XTHAVC9YnafnPyzj] (中文(简体) ). 我们注意到以下发行商的ACS受到影响. • 3DS LOA ACS RELT 020301 01127 (Revolution) • 3DS LOA ACS OPES 020301 00996(开放欧洲股份有限公司) 我们将继续监测局势.

3. 2026年10月20日 UTC 13:52monitoring

   我们不再看到Revolut卡认证失败的高度。 然而Revolute状态页面和Google Cloud平台仍然显示事件仍在继续. 我们正在继续认真监测该平台。 我们为任何不便感到遗憾.

4. 2026年10月21日 UTC 07:59resolved

   事件现已解决. 我们为任何不便感到遗憾.

自动翻译自官方事件更新。

1. 2026年9月3日 UTC 11:01investigating

   我们知道,一些用户在访问Ravelin仪表板时收到错误。 我们目前正在调查原因,并将在这里公布我们所了解的更多最新情况.

2. 2026年9月3日 UTC 11:12investigating

   我们把导致仪表板出错的更改卷回, 并在协调世界时10点45分左右看到错误停止。 我们正在继续调查这一问题的根源.

3. 2026年9月3日 UTC 11:27monitoring

   仪表盘又开始运行了 错误已经停止了 我们正在继续监测任何进一步的仪表板错误,并继续调查其根源.

4. 2026年9月3日 UTC 16:38resolved

   先前的事件现在已经得到解决。 我们为任何不便感到遗憾.

自动翻译自官方事件更新。

1. 2026年9月1日 UTC 15:21investigating

   我们3DS API的出错率上升了 以美国为基地的交通正被改道到我们的欧盟集群进行处理,因此你可能会遇到更高的响应时间. 我们目前正在修复我们的美国集群。 我们正在调查找出原因 请检查date=中的日期值 (帮助).

2. 2026年9月1日 UTC 15:44monitoring

   ``` 我们的美国集群已经恢复了 正常地处理交通 Google确定了以下的发行: 虚拟私人云 - VM与VM通信 - VM与VM之间的内部IP通信 在下列地点: - Asia-east1(活动) - 中央一级(活跃) 这影响到我们中一地区各组成部分的连通性。 我们将继续监测局势。 ```

3. 2026年9月1日 UTC 16:22monitoring

   Google现在在此发布正在发生的事件的详情: [https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev] (https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev]). 我们将继续监测3DS API。 我们为任何不便感到遗憾.

4. 2026年9月1日 UTC 17:01resolved

   先前的事件现在已经得到解决。 我们为任何不便感到遗憾.

自动翻译自官方事件更新。

1. 2026年7月9日 UTC 17:10investigating

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

2. 2026年7月9日 UTC 17:34identified

   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. 2026年7月9日 UTC 17:42monitoring

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

4. 2026年7月9日 UTC 19:31resolved

   The incident has been resolved.

1. 2026年6月18日 UTC 15:47monitoring

   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. 2026年6月18日 UTC 16:11resolved

   API performance has returned to expected performance levels

1. 2026年3月2日 UTC 16:40monitoring

   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. 2026年3月2日 UTC 16:48resolved

   The dashboard is now fully operational.

1. 2026年1月21日 UTC 16:45identified

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

2. 2026年1月21日 UTC 16:45resolved

   This is now resolved

1. 2025年8月21日 UTC 14:05investigating

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

2. 2025年8月21日 UTC 14:30monitoring

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

3. 2025年8月21日 UTC 15:29resolved

   Our system is fully operational

1. 2025年8月18日 UTC 15:09identified

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

2. 2025年8月18日 UTC 15:13monitoring

   Response times have returned to normal levels.

3. 2025年8月18日 UTC 15:29resolved

   The issue is resolved

1. 2025年6月12日 UTC 18:11investigating

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

2. 2025年6月12日 UTC 18:29investigating

   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. 2025年6月12日 UTC 18:55identified

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

4. 2025年6月12日 UTC 19:18monitoring

   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. 2025年6月12日 UTC 19:43monitoring

   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. 2025年6月12日 UTC 21:10resolved

   Our system is fully operational.

1. 2025年4月22日 UTC 11:50identified

   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. 2025年4月22日 UTC 12:36monitoring

   Response times have recovered and we are monitoring the situation.

3. 2025年4月22日 UTC 13:28resolved

   Latency has returned to normal levels.

4. 2025年4月22日 UTC 16:26resolved

   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. 2025年2月19日 UTC 15:22resolved

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

1. 2024年9月6日 UTC 13:50investigating

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

2. 2024年9月6日 UTC 14:18monitoring

   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. 2024年9月6日 UTC 15:31resolved

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

4. 2024年9月6日 UTC 16:04investigating

   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. 2024年9月6日 UTC 16:25monitoring

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

6. 2024年9月6日 UTC 17:44resolved

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

1. 2024年8月7日 UTC 12:28identified

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

2. 2024年8月7日 UTC 12:35monitoring

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

3. 2024年8月7日 UTC 13:33resolved

   This is now resolved.

1. 2024年5月1日 UTC 15:52investigating

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

2. 2024年5月1日 UTC 15:55investigating

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

3. 2024年5月1日 UTC 16:25monitoring

   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. 2024年5月1日 UTC 16:29resolved

   The incident is now resolved

1. 2024年4月22日 UTC 09:19investigating

   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. 2024年4月22日 UTC 09:55identified

   We have identified the problem and are deploying a fix.

3. 2024年4月22日 UTC 10:11monitoring

   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. 2024年4月22日 UTC 12:50resolved

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

1. 2024年2月28日 UTC 08:36investigating

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

2. 2024年2月28日 UTC 09:16monitoring

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

3. 2024年2月28日 UTC 13:23resolved

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

1. 2024年2月6日 UTC 11:57investigating

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

2. 2024年2月6日 UTC 12:07monitoring

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

3. 2024年2月7日 UTC 08:51resolved

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

1. 2024年2月1日 UTC 16:59monitoring

   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. 2024年2月1日 UTC 19:23monitoring

   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. 2024年2月2日 UTC 16:48monitoring

   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. 2024年2月6日 UTC 11:57resolved

   This was resolved late last week

1. 2023年12月5日 UTC 10:35investigating

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

2. 2023年12月5日 UTC 11:06identified

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

3. 2023年12月5日 UTC 11:59identified

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

4. 2023年12月5日 UTC 12:55identified

   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. 2023年12月5日 UTC 14:12identified

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

6. 2023年12月5日 UTC 14:41monitoring

   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. 2023年12月5日 UTC 15:06monitoring

   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. 2023年12月5日 UTC 16:03resolved

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