HiveCPQ Outage History

HiveCPQ is up right now

HiveCPQ had 5 outages in the last 2 years totaling 23h 37m of downtime — averaging 0.2 incidents per month.

There were 5 HiveCPQ outages since January 15, 2026 totaling 23h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.hivecpq.com

Major May 15, 2026

Investigating - Degraded performance

Detected by Pingoru
May 15, 2026, 12:19 PM UTC
Resolved
May 15, 2026, 01:01 PM UTC
Duration
42m
Affected: HiveCPQ application
Timeline · 2 updates
  1. investigating May 15, 2026, 12:19 PM UTC

    We’re currently investigating reports of slower-than-usual performance in the Hive CPQ application. Some users may experience delays when loading pages or performing actions. The application remains available and no data is affected. Our team is actively working on a resolution. We’ll share an update as soon as we have more information. Thank you for your patience.

  2. resolved May 15, 2026, 01:01 PM UTC

    Resolved — Platform stability The issue causing intermittent instability on the platform has been identified and resolved. All services are operating normally again. We are continuing to monitor closely over the coming hours to confirm stable behaviour. Thank you for your patience.

Read the full incident report →

Major April 12, 2026

Degraded Performanc: Configurator Loading Times

Detected by Pingoru
Apr 12, 2026, 09:21 AM UTC
Resolved
Apr 12, 2026, 10:41 AM UTC
Duration
1h 19m
Affected: HiveCPQ application
Timeline · 2 updates
  1. investigating Apr 12, 2026, 09:21 AM UTC

    We are currently aware of increased response times when loading and interacting with configurators. Our team has identified the root cause and is working on a fix.

  2. resolved Apr 12, 2026, 10:41 AM UTC

    The degraded performance affecting configurator loading times has been resolved. A database query optimization has been deployed that significantly reduces response times. No data was affected during this incident. All systems are operating normally. Thank you for your patience.

Read the full incident report →

Minor February 10, 2026

Visual Duplication in Sub-Configurators

Detected by Pingoru
Feb 10, 2026, 10:00 AM UTC
Resolved
Feb 10, 2026, 10:37 AM UTC
Duration
37m
Affected: HiveCPQ application
Timeline · 3 updates
  1. investigating Feb 10, 2026, 10:00 AM UTC

    We have identified a display issue following the latest update where some users are seeing duplicated data within sub-configurator blocks. Resolution: Our team has identified the cause and is actively working on a fix to restore the correct display logic.

  2. investigating Feb 10, 2026, 10:20 AM UTC

    Update Details: Our engineering team has completed their investigation and identified the root cause of the duplication reports. Viewing Issue Only: We can confirm this is strictly a front-end display issue. The user interface is rendering duplicates, but the underlying data structure is not affected. Logic is Intact: The configurator logic remains correct. Calculations and saved configurations are processing accurately, despite the visual duplication on screen.

  3. resolved Feb 10, 2026, 10:37 AM UTC

    The technical incident that occurred earlier has been successfully resolved. Our dedicated team worked to identify and fix the issue, ensuring minimal disruption to our operations. We apologize for any inconvenience caused and appreciate your patience and understanding. Thank you for your support!

Read the full incident report →

Major January 20, 2026

Investigating Delays in Hive Query Performance

Detected by Pingoru
Jan 20, 2026, 02:18 PM UTC
Resolved
Jan 20, 2026, 02:38 PM UTC
Duration
20m
Affected: HiveCPQ applicationHiveConnectHiveCPQ APIHiveCPQ Support
Timeline · 2 updates
  1. investigating Jan 20, 2026, 02:18 PM UTC

    Some users may experience delays or timeouts when running queries. Data integrity is not affected. Status: Our team is actively identifying the issue and working toward a resolution. We will provide another update in [30/60] minutes.

  2. resolved Jan 20, 2026, 02:38 PM UTC

    The performance issues affecting Hive queries have been resolved. All systems are now fully operational.

Read the full incident report →

Major January 15, 2026

Service Outage: Application Unresponsive

Detected by Pingoru
Jan 15, 2026, 04:23 PM UTC
Resolved
Jan 16, 2026, 01:00 PM UTC
Duration
20h 36m
Affected: HiveCPQ applicationHiveConnectHiveCPQ API
Timeline · 5 updates
  1. investigating Jan 15, 2026, 04:23 PM UTC

    We are currently experiencing a major service disruption affecting the availability of Hive. Users are currently unable to access the application, and the system is not responding to requests. Our engineering team has identified the issue and is actively working on a resolution to restore service immediately.

  2. investigating Jan 15, 2026, 04:32 PM UTC

    We are pleased to report that the application is back online and responding normally. You should now be able to log in and access your data. While service has been restored, our team is continuing to investigate the root cause of the incident and is closely monitoring system performance to ensure stability.

  3. investigating Jan 15, 2026, 05:46 PM UTC

    The issue has been isolated to a backend infrastructure component. We are currently implementing fixes and closely monitoring system performance to ensure stability.

  4. monitoring Jan 16, 2026, 07:57 AM UTC

    We are continuing to closely monitor the backend infrastructure component. We have observed some minor performance irregularities and are keeping the incident in a “Monitoring” state to ensure full stability. Our team is actively investigating these fluctuations to ensure everything is in perfect order before we consider the incident resolved.

  5. resolved Jan 16, 2026, 01:00 PM UTC

    Good news! The technical incident that occurred earlier has been successfully resolved. Our dedicated team worked to identify and fix the issue, ensuring minimal disruption to our operations. We apologize for any inconvenience caused and appreciate your patience and understanding. Thank you for your support!

Read the full incident report →