PriceHubble Status Page

Jun 19, 2026 · resolved Jun 19

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

May 30, 2026 · resolved May 30

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.

May 13, 2026 · resolved May 13

<strong>Summary</strong> 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. <strong>Root Cause</strong> 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. <strong>Remediation</strong> 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. <strong>Monitoring &amp; Transparency</strong> 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.

Jul 11, 2025 · resolved Jul 11

This incident has been resolved.

Jun 10, 2025 · resolved Jun 10

This incident has been resolved.