PriceHubble Outage History

PriceHubble is up right now

Pingoru has recorded 50 incidents for PriceHubble: 5 in the last 12 months and 2 in the last 90 days.

Source: status.pricehubble.com

50incidents recorded
5last 12 months
2last 90 days
23 minutestypical duration
Incidents per month
012MayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOct0%
Pingoru began tracking PriceHubble in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 202622 of 744 (0%)
June 202610 of 720 (0%)
July 202600 of 744 (0%)
August 202610 of 744 (0%)
September 202610 of 720 (0%)
October 202600 of 514 (0%)

Incidents, newest first

Major September 8, 2026 Templates and Share link API degradation 11m

Started Sep 08, 2026, 08:00 AM UTC· resolved Sep 08, 2026, 08:11 AM UTC

  1. resolved Sep 08, 2026, 04:12 PM UTC

    Summary On 8 September 2026, between 10:11 and 10:59 CEST, we experienced an incident affecting our Templates and Share link APIs. During this window, users might have encountered errors when generating or acccessing page links. Full service was restored at 10:59 CEST. Root Cause A recent dependency upgrade introduced a compatibility issue between our API framework and an underlying observability library, which caused a few specific endpoints to fail once traffic passed a certain volume. Remediation We rolled back the affected deployment to immediately restore the service. We are applying a permanent fix to the underlying dependency issue before reintroducing the change. We apologise for any inconvenience this caused and thank you for your patience.

Read the full incident report →

Major August 31, 2026 Intermittent failures on Comparables 2m Transaction Search API, Transaction Statistics API

Started Aug 31, 2026, 12:55 PM UTC· resolved Aug 31, 2026, 12:58 PM UTC

  1. monitoring Aug 31, 2026, 12:55 PM UTC

    We identified an increased failure rate on the Transaction endpoints. We have found a possible cause and applied a fix. We're monitoring the service, updates will follow within 30 minutes.

  2. resolved Aug 31, 2026, 12:58 PM UTC

    We haven't observed any errors after our fix. The incident is resolved.

Read the full incident report →

Notice June 19, 2026 Offers search API degraded –

Started Jun 19, 2026, 10:00 AM UTC· resolved Jun 19, 2026, 10:00 AM UTC

  1. resolved Jun 19, 2026, 10:26 AM UTC

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

Read the full incident report →

Critical May 30, 2026 Database capacity incident affecting Service Availability 1h 6m Offer Search API, Offer Statistics API

Started May 30, 2026, 01:20 PM UTC· resolved May 30, 2026, 02:26 PM UTC

  1. investigating May 30, 2026, 01:20 PM UTC

    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. investigating May 30, 2026, 01:21 PM UTC

    We are continuing to investigate this issue.

  3. identified May 30, 2026, 01:24 PM UTC

    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. monitoring May 30, 2026, 01:27 PM UTC

    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. resolved May 30, 2026, 02:26 PM UTC

    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.

Read the full incident report →

Major May 13, 2026 Valuation API Outage 35m

Started May 13, 2026, 08:30 AM UTC· resolved May 13, 2026, 09:05 AM UTC

  1. resolved May 21, 2026, 07:18 AM UTC

    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.

Read the full incident report →

Notice July 11, 2025 Connection issues due to internal network problem 44m

Started Jul 11, 2025, 07:28 PM UTC· resolved Jul 11, 2025, 08:13 PM UTC

  1. investigating Jul 11, 2025, 07:28 PM UTC

    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. monitoring Jul 11, 2025, 07:53 PM UTC

    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. resolved Jul 11, 2025, 08:13 PM UTC

    This incident has been resolved.

Read the full incident report →