52 Pricehubble incidents · 2021年7月 — official updates, affected components, duration and resolution details.
インフォメーション 2026年9月8日、10:11と10:59 CESTの間、テンプレートと共有リンクAPIに影響を及ぼす事件を経験しました。 このウィンドウでは、ページリンクを生成またはacccessingしたときにエラーが発生することがあります。 10:59 CEST でフルサービスが復元されました。 根本原因 最近の依存性アップグレードでは、APIフレームワークと基礎的なオブザーバビリティライブラリとの間の互換性の問題が導入され、トラフィックが一定のボリュームを通過したときに失敗するいくつかの特定のエンドポイントを引き起こしました。 インフォメーション 影響を受けたデプロイメントをロールバックし、サービスをすぐに復元します。 変更を削減する前に、依存関係の問題に永続的な修正を適用しています。 大変ご迷惑をおかけいたしますが、何卒ご了承賜りますようお願い申し上げます.
公式のインシデント更新を自動翻訳しています。
取引エンドポイントの故障率が増加しました。 可能な原因を発見し、修正を加えました。 サービスの監視、更新は30分以内です.
修正後、エラーは未確認です。 事件は解決されます.
公式のインシデント更新を自動翻訳しています。
We are aware of an issue affecting offers search API and are investigating. Updates will be posted here as we progress
We are investigating an issue affecting database capacity that is causing elevated error rates and service disruption for some customers. Our engineering team is actively working to restore full service. Further updates will be provided as they become available.
We are continuing to investigate this issue.
We identified the issue affecting database capacity and have applied corrective changes. Services have recovered and are currently operating normally. We are monitoring the platform closely to ensure stability before resolving the incident.
The mitigation measures have been successfully applied and all services have recovered. System health metrics are within normal ranges and customer-facing functionality has been restored. We are continuing to monitor the platform closely to ensure ongoing stability before formally resolving the incident.
All services have returned to normal operation and are stable. We have identified and paused the processes that contributed to the incident, and the platform has fully recovered. We will continue to monitor the environment closely to ensure stability. A detailed postmortem, including root cause analysis, impact assessment, and follow-up actions, will be shared as soon as it is available. Thank you for your patience while we worked to resolve the issue.
Summary On 13 May 2025, between 10:30 and 11:05 CEST, we experienced an incident affecting our API services. The majority of users were unable to access the Valuation API during this window, and elevated response latency was observed across all API endpoints. Full service was restored at 11:05 CEST. Root Cause We identified a bottleneck in a component on the critical path of our infrastructure. Under load, this component became a limiting factor and degraded service availability and performance. Remediation We are actively implementing improvements to the affected component to increase its scalability and prevent recurrence. We will continue to monitor the situation closely following these changes. Monitoring & Transparency We are aware that this incident was not surfaced by the monitoring that feeds this status page, which means our customers did not receive a timely notification. We take this seriously. We are expanding our monitoring coverage and adding more granular detail to this status page to more accurately reflect the real-time health of our services. Our goal is to ensure that any future disruption is communicated proactively. We apologise for the disruption this caused and thank you for your patience.
We've identified an internal network issue causing connection problems. Our team is actively working on a fix and we'll share updates as progress is made. Thanks for your patience!
We've implemented a fix for the issue and are currently monitoring to ensure everything is stable. We'll continue to keep you updated.
This incident has been resolved.
We've identified an internal network issue causing connection problems. Our team is actively working on a fix and we'll share updates as progress is made. Thanks for your patience!
We've implemented a fix for the issue and are currently monitoring to ensure everything is stable. We'll continue to keep you updated.
This incident has been resolved.
Our monitoring shows the problem to no longer occur, and no other failures have appeared since. We now consider this incident resolved, and should be back to regular service.
The Valuation API was down from 10:06am to 10:35am (29 minutes) due to a network issue following a configuration change. We sincerely apologize for the inconvenience, and we are taking appropriate measures to prevent such downtime to happen again.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The creation of dossier was done this morning from 8:23 to 9:28 after a release negatively impacting this API.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue with intermittent failure on authentication.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our monitoring is reporting timeouts across our APIs. We are currently investigating the issue
This incident has been resolved.
Dear Customers, We have rolled out a hotfix which should improve the stability of our API endpoints. We also extended our observability capabilities to better isolate the issue. Currently, we are in the phase of monitoring and collecting further metrics to verify if all affected services have been stabilised by the hotfix. Thank you for your understanding!
Dear Customers, Thanks to the extended metric collection we could further isolate the problem we are facing. This triggered further mitigation steps from our side which we are implementing and rolling out. Next update can be expected at 12.00 CEST
Dear Customers, We have prepared the required patches and we are in the process of releasing them. Following the releases, we will closely monitor the situation and release subsequent updates if needed. Next update can be expected at 14:00 CEST
Dear Customers, We have finished with the roll-out phase of the prepared patches and we are currently monitoring the situation. Next update can be expected at 16:00 CEST
Dear Customers, We haven't detected any API endpoint instability since the release of the patches. We will keep monitoring the situation. Next update can be expected at 2022.07.29 10:00 CEST
Dear Customers, We haven't detected any API endpoint instability since the release of the patches. We will keep monitoring the situation. Next update can be expected at 2022.07.29 12:00 CEST
Dear Customers, in the last hours we have released two more fixes for our services, which we are actively monitoring. The series of fixes deployed over the last days allow us to say that services are stable at the present time, but we will keep the incident open until we are thoroughly convinced it is over. Over the weekend our team will remain on duty monitoring the situation and the updates will be sparse. In this case, no update will be good news.
Dear customers, We could successfully rollout all fixes and our systems are now stable. We will continue to closely monitor the situation until tomorrow. This incident will be closed tomorrow if no more problems are observed. Thank you very much
Dear customers, The technical incident that started on Thursday 21 of July is considered resolved. Corporate communication is being prepared and will follow up shortly. Thank you
We are monitoring an incident that affects our endpoints, causing a higher than normal latency. Some endpoints timeout causing disruptions of service.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
