Pricehubble 장애 기록

1. 2026년 9월 8일 오후 4:12 UTCresolved

   제품정보 에 8 9월 2026, 사이 10:11 과 10:59 CEST, 우리는 우리의 템플릿과 공유 링크 API에 영향을 미치는 사건을 경험. 이 창에서 사용자는 페이지 링크를 생성하거나 단축 할 때 오류가 발생할 수 있습니다. 전체 서비스는 10:59 CEST에 복원되었습니다. 뿌리 원인 최근의 의존성 향상은 API 프레임 워크와 비교할 수 없는 관측성 라이브러리 사이의 호환성 문제를 도입했습니다. 이는 특정한 엔드포인트가 한 번 트래픽이 특정 볼륨을 통과하지 못하게 합니다. 관련 기사 우리는 즉시 서비스를 복원에 영향을 미치는 배포를 다시 압니다. 변경을 재발생하기 전에 종속성 문제로 영구적인 수정을 적용하고 있습니다. 우리는이 기인하고 당신의 인내에 당신을 감사하는 어떤 불편을 위해 사과합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 31일 오후 12:55 UTCmonitoring

   Transaction endpoints의 증가된 실패율을 확인했습니다. 우리는 가능한 원인을 발견하고 수정을 적용했습니다. 우리는 서비스를 감시하고, 갱신은 30 분 안에 따릅니다.

2. 2026년 8월 31일 오후 12:58 UTCresolved

   우리는 우리의 수정 후 오류를 관찰하지 않았습니다. 사건은 해결됩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 19일 오전 10:26 UTCresolved

   We are aware of an issue affecting offers search API and are investigating. Updates will be posted here as we progress

1. 2026년 5월 30일 오후 1:20 UTCinvestigating

   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.

2. 2026년 5월 30일 오후 1:21 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 5월 30일 오후 1:24 UTCidentified

   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.

4. 2026년 5월 30일 오후 1:27 UTCmonitoring

   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.

5. 2026년 5월 30일 오후 2:26 UTCresolved

   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.

1. 2026년 5월 21일 오전 7:18 UTCresolved

   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.

1. 2025년 7월 11일 오후 7:28 UTCinvestigating

   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!

2. 2025년 7월 11일 오후 7:53 UTCmonitoring

   We've implemented a fix for the issue and are currently monitoring to ensure everything is stable. We'll continue to keep you updated.

3. 2025년 7월 11일 오후 8:13 UTCresolved

   This incident has been resolved.

1. 2025년 6월 10일 오후 4:19 UTCidentified

   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!

2. 2025년 6월 10일 오후 4:40 UTCmonitoring

   We've implemented a fix for the issue and are currently monitoring to ensure everything is stable. We'll continue to keep you updated.

3. 2025년 6월 10일 오후 4:59 UTCresolved

   This incident has been resolved.

1. 2023년 8월 22일 오후 2:46 UTCresolved

   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.

1. 2023년 7월 14일 오후 12:27 UTCresolved

   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.

1. 2022년 12월 9일 오후 3:46 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 12월 9일 오후 3:58 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2022년 12월 9일 오후 4:47 UTCresolved

   This incident has been resolved.

1. 2022년 12월 7일 오전 10:26 UTCresolved

   The creation of dossier was done this morning from 8:23 to 9:28 after a release negatively impacting this API.

1. 2022년 10월 13일 오후 4:40 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 10월 13일 오후 5:01 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2022년 11월 8일 오전 8:44 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2022년 11월 8일 오전 8:44 UTCresolved

   This incident has been resolved.

1. 2022년 9월 26일 오전 7:19 UTCinvestigating

   We are currently investigating an issue with intermittent failure on authentication.

2. 2022년 9월 26일 오전 8:11 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2022년 9월 26일 오전 8:36 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2022년 9월 26일 오전 9:00 UTCresolved

   This incident has been resolved.

1. 2022년 8월 9일 오전 10:10 UTCinvestigating

   Our monitoring is reporting timeouts across our APIs. We are currently investigating the issue

2. 2022년 8월 9일 오전 10:50 UTCresolved

   This incident has been resolved.

1. 2022년 7월 27일 오후 2:16 UTCmonitoring

   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!

2. 2022년 7월 28일 오전 8:27 UTCmonitoring

   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

3. 2022년 7월 28일 오전 10:12 UTCmonitoring

   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

4. 2022년 7월 28일 오후 12:46 UTCmonitoring

   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

5. 2022년 7월 28일 오후 2:55 UTCmonitoring

   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

6. 2022년 7월 29일 오전 8:04 UTCmonitoring

   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

7. 2022년 7월 29일 오후 3:16 UTCmonitoring

   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.

8. 2022년 8월 3일 오후 1:23 UTCmonitoring

   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

9. 2022년 8월 4일 오후 12:55 UTCresolved

   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

1. 2022년 7월 29일 오전 8:23 UTCresolved

   We are monitoring an incident that affects our endpoints, causing a higher than normal latency. Some endpoints timeout causing disruptions of service.

1. 2022년 7월 22일 오전 6:36 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 7월 22일 오후 3:08 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2022년 7월 25일 오전 7:10 UTCresolved

   This incident has been resolved.

1. 2022년 4월 11일 오전 9:16 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 4월 11일 오전 9:40 UTCresolved

   This incident has been resolved.

1. 2022년 3월 31일 오후 1:41 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 3월 31일 오후 2:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 2022년 3월 31일 오후 2:00 UTCresolved

   This incident has been resolved.

1. 2022년 3월 29일 오전 8:16 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 3월 29일 오전 8:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 2022년 3월 29일 오전 8:25 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 2022년 3월 29일 오전 8:25 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2022년 3월 29일 오전 8:52 UTCresolved

   This incident has been resolved.