HiveCPQ Outage History

HiveCPQ is up right now

Pingoru has recorded 8 incidents for HiveCPQ: 8 in the last 12 months and 0 in the last 90 days.

Source: status.hivecpq.com

8incidents recorded
8last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking HiveCPQ in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202611 of 744 (0%)
June 202610 of 720 (0%)
July 202624 of 744 (1%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 517 (0%)

Incidents, newest first

Major July 10, 2026 Degraded Performance: Investigating 1h 26m Hive CPQ application, Hive CPQ API

Started Jul 10, 2026, 09:45 AM UTC· resolved Jul 10, 2026, 11:11 AM UTC

  1. investigating Jul 10, 2026, 09:45 AM UTC

    We’re currently experiencing elevated response times across parts of the Hive CPQ platform. Our engineering team is investigating the issue. You may notice slower page loads or occasional errors when configuring products or opening projects. The Hive CPQ team

  2. monitoring Jul 10, 2026, 09:59 AM UTC

    The performance of the Hive CPQ application has returned to normal. We are currently monitoring the situation.

  3. resolved Jul 10, 2026, 11:11 AM UTC

    The issue has been resolved. Our team does continue to monitor the situation.

Read the full incident report →

Minor July 8, 2026 Increased error rates for MCP 2h 25m Hive CPQ MCP

Started Jul 08, 2026, 08:52 AM UTC· resolved Jul 08, 2026, 11:17 AM UTC

  1. investigating Jul 08, 2026, 08:52 AM UTC

    We are investigating an issue where MCP is returning 403 errors, while it should operate normally.

  2. resolved Jul 08, 2026, 11:17 AM UTC

    The issue has been identified as a Claude platform issue, non Hive CPQ related.

Read the full incident report →

Major June 29, 2026 App performance degradation 15m Hive CPQ application, HiveConnect, Hive CPQ API

Started Jun 29, 2026, 01:28 PM UTC· resolved Jun 29, 2026, 01:44 PM UTC

  1. investigating Jun 29, 2026, 01:28 PM UTC

    We are aware of an ongoing issue causing the application to run slower than normal. Our team is actively investigating the root cause. There is no confirmed cause or fix yet.

  2. resolved Jun 29, 2026, 01:44 PM UTC

    We have identified the root cause of the issue and it has been resolved.

Read the full incident report →

Major May 15, 2026 Investigating - Degraded performance 42m Hive CPQ application

Started May 15, 2026, 12:19 PM UTC· resolved May 15, 2026, 01:01 PM UTC

  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 1h 19m Hive CPQ application

Started Apr 12, 2026, 09:21 AM UTC· resolved Apr 12, 2026, 10:41 AM UTC

  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 37m Hive CPQ application

Started Feb 10, 2026, 10:00 AM UTC· resolved Feb 10, 2026, 10:37 AM UTC

  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 20m Hive CPQ application, HiveConnect, Hive CPQ API, Hive CPQ Support

Started Jan 20, 2026, 02:18 PM UTC· resolved Jan 20, 2026, 02:38 PM UTC

  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 20h 36m Hive CPQ application, HiveConnect, Hive CPQ API

Started Jan 15, 2026, 04:23 PM UTC· resolved Jan 16, 2026, 01:00 PM UTC

  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 →