PriceHubble incident

Database capacity incident affecting Service Availability

Critical Resolved View vendor source →

PriceHubble experienced a critical incident on May 30, 2026 affecting Offer Search API and Offer Statistics API, lasting 1h 6m. The incident has been resolved; the full update timeline is below.

Started
May 30, 2026, 01:20 PM UTC
Resolved
May 30, 2026, 02:26 PM UTC
Duration
1h 6m
Detected by Pingoru
May 30, 2026, 01:20 PM UTC

Affected components

Offer Search APIOffer Statistics API

Update timeline

  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.