Historique des pannes de Pricehubble

1. 8 septembre 2026 à 16:12 UTCresolved

   Résumé Le 8 septembre 2026, entre 10:11 et 10:59 CEST, nous avons connu un incident affectant nos APIs de modèles et de liens de partage. Pendant cette fenêtre, les utilisateurs ont pu rencontrer des erreurs lors de la création ou de l'accessing des liens de page. Le service complet a été restauré à 10:59 CEST. Cause Une mise à jour récente de la dépendance a introduit un problème de compatibilité entre notre cadre API et une bibliothèque d'observation sous-jacente, ce qui a fait échouer quelques paramètres spécifiques une fois le trafic passé un certain volume. Réparation Nous avons repoussé le déploiement affecté pour rétablir immédiatement le service. Nous appliquons une solution permanente à la question de la dépendance sous-jacente avant de réintroduire le changement. Nous nous excusons pour tout inconvénient causé et nous vous remercions de votre patience.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 31 août 2026 à 12:55 UTCmonitoring

   Nous avons identifié un taux de défaillance accru sur les paramètres de la transaction. Nous avons trouvé une cause possible et appliqué une correction. Nous surveillons le service, les mises à jour suivront dans 30 minutes.

2. 31 août 2026 à 12:58 UTCresolved

   Nous n'avons observé aucune erreur après notre réparation. L'incident est résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 19 juin 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 mai 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 mai 2026 à 13:21 UTCinvestigating

   We are continuing to investigate this issue.

3. 30 mai 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 mai 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 mai 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 mai 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 juillet 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 juillet 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 juillet 2025 à 20:13 UTCresolved

   This incident has been resolved.

1. 10 juin 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 juin 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 juin 2025 à 16:59 UTCresolved

   This incident has been resolved.

1. 22 août 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 juillet 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 décembre 2022 à 15:46 UTCinvestigating

   We are currently investigating this issue.

2. 9 décembre 2022 à 15:58 UTCmonitoring

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

3. 9 décembre 2022 à 16:47 UTCresolved

   This incident has been resolved.

1. 7 décembre 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 octobre 2022 à 16:40 UTCinvestigating

   We are currently investigating this issue.

2. 13 octobre 2022 à 17:01 UTCmonitoring

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

3. 8 novembre 2022 à 08:44 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 8 novembre 2022 à 08:44 UTCresolved

   This incident has been resolved.

1. 26 septembre 2022 à 07:19 UTCinvestigating

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

2. 26 septembre 2022 à 08:11 UTCidentified

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

3. 26 septembre 2022 à 08:36 UTCmonitoring

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

4. 26 septembre 2022 à 09:00 UTCresolved

   This incident has been resolved.

1. 9 août 2022 à 10:10 UTCinvestigating

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

2. 9 août 2022 à 10:50 UTCresolved

   This incident has been resolved.

1. 27 juillet 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 juillet 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 juillet 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 juillet 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 juillet 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 juillet 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 juillet 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 août 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 août 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 juillet 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 juillet 2022 à 06:36 UTCinvestigating

   We are currently investigating this issue.

2. 22 juillet 2022 à 15:08 UTCmonitoring

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

3. 25 juillet 2022 à 07:10 UTCresolved

   This incident has been resolved.

1. 11 avril 2022 à 09:16 UTCinvestigating

   We are currently investigating this issue.

2. 11 avril 2022 à 09:40 UTCresolved

   This incident has been resolved.

1. 31 mars 2022 à 13:41 UTCinvestigating

   We are currently investigating this issue.

2. 31 mars 2022 à 14:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 31 mars 2022 à 14:00 UTCresolved

   This incident has been resolved.

1. 29 mars 2022 à 08:16 UTCinvestigating

   We are currently investigating this issue.

2. 29 mars 2022 à 08:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 mars 2022 à 08:25 UTCidentified

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

4. 29 mars 2022 à 08:25 UTCmonitoring

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

5. 29 mars 2022 à 08:52 UTCresolved

   This incident has been resolved.