История сбоев Pricehubble

1. 8 сентября 2026 г. в 16:12 UTCresolved

   Резюме 8 сентября 2026 года, между 10:11 и 10:59 CEST, мы столкнулись с инцидентом, затрагивающим наши API-интерфейсы Шаблонов и Share link. Во время этого окна пользователи могли столкнуться с ошибками при создании или получении ссылок на страницы. Полное обслуживание было восстановлено в 10:59 CEST. Коренная причина Недавнее обновление зависимостей ввело проблему совместимости между нашей структурой API и базовой библиотекой наблюдаемости, что привело к тому, что несколько конкретных конечных точек вышли из строя после того, как трафик прошел определенный объем. Восстановление Мы откатили пострадавшее развертывание, чтобы немедленно восстановить службу. Мы применяем постоянное решение проблемы зависимости, прежде чем вводить изменения. Мы приносим свои извинения за причиненные неудобства и благодарим вас за терпение.

Автоматический перевод официального обновления инцидента.

1. 31 августа 2026 г. в 12:55 UTCmonitoring

   Мы выявили повышенный уровень отказов на конечных точках транзакций. Мы нашли возможную причину и применили исправление. Мы следим за сервисом, обновления будут в течение 30 минут.

2. 31 августа 2026 г. в 12:58 UTCresolved

   Мы не заметили никаких ошибок после исправления. Инцидент урегулирован.

Автоматический перевод официального обновления инцидента.

1. 19 июня 2026 г. в 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. 30 мая 2026 г. в 13: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. 30 мая 2026 г. в 13:21 UTCinvestigating

   We are continuing to investigate this issue.

3. 30 мая 2026 г. в 13: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. 30 мая 2026 г. в 13: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. 30 мая 2026 г. в 14: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. 21 мая 2026 г. в 07: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. 11 июля 2025 г. в 19: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. 11 июля 2025 г. в 19: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. 11 июля 2025 г. в 20:13 UTCresolved

   This incident has been resolved.

1. 10 июня 2025 г. в 16: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. 10 июня 2025 г. в 16: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. 10 июня 2025 г. в 16:59 UTCresolved

   This incident has been resolved.

1. 22 августа 2023 г. в 14: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. 14 июля 2023 г. в 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. 9 декабря 2022 г. в 15:46 UTCinvestigating

   We are currently investigating this issue.

2. 9 декабря 2022 г. в 15:58 UTCmonitoring

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

3. 9 декабря 2022 г. в 16:47 UTCresolved

   This incident has been resolved.

1. 7 декабря 2022 г. в 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. 13 октября 2022 г. в 16:40 UTCinvestigating

   We are currently investigating this issue.

2. 13 октября 2022 г. в 17:01 UTCmonitoring

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

3. 8 ноября 2022 г. в 08:44 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 8 ноября 2022 г. в 08:44 UTCresolved

   This incident has been resolved.

1. 26 сентября 2022 г. в 07:19 UTCinvestigating

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

2. 26 сентября 2022 г. в 08:11 UTCidentified

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

3. 26 сентября 2022 г. в 08:36 UTCmonitoring

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

4. 26 сентября 2022 г. в 09:00 UTCresolved

   This incident has been resolved.

1. 9 августа 2022 г. в 10:10 UTCinvestigating

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

2. 9 августа 2022 г. в 10:50 UTCresolved

   This incident has been resolved.

1. 27 июля 2022 г. в 14: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. 28 июля 2022 г. в 08: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. 28 июля 2022 г. в 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. 28 июля 2022 г. в 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. 28 июля 2022 г. в 14: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. 29 июля 2022 г. в 08: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. 29 июля 2022 г. в 15: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. 3 августа 2022 г. в 13: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. 4 августа 2022 г. в 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. 29 июля 2022 г. в 08: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. 22 июля 2022 г. в 06:36 UTCinvestigating

   We are currently investigating this issue.

2. 22 июля 2022 г. в 15:08 UTCmonitoring

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

3. 25 июля 2022 г. в 07:10 UTCresolved

   This incident has been resolved.

1. 11 апреля 2022 г. в 09:16 UTCinvestigating

   We are currently investigating this issue.

2. 11 апреля 2022 г. в 09:40 UTCresolved

   This incident has been resolved.

1. 31 марта 2022 г. в 13:41 UTCinvestigating

   We are currently investigating this issue.

2. 31 марта 2022 г. в 14:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 31 марта 2022 г. в 14:00 UTCresolved

   This incident has been resolved.

1. 29 марта 2022 г. в 08:16 UTCinvestigating

   We are currently investigating this issue.

2. 29 марта 2022 г. в 08:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 марта 2022 г. в 08:25 UTCidentified

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

4. 29 марта 2022 г. в 08:25 UTCmonitoring

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

5. 29 марта 2022 г. в 08:52 UTCresolved

   This incident has been resolved.