Gtmhub incident

Increased error rate in Quantive REST API

Major Resolved View vendor source →

Gtmhub experienced a major incident on October 9, 2025 affecting Web Application and OKRs API and 1 more component, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Oct 09, 2025, 09:07 AM UTC
Resolved
Oct 10, 2025, 10:00 AM UTC
Duration
1d
Detected by Pingoru
Oct 09, 2025, 09:07 AM UTC

Affected components

Web ApplicationOKRs APIComments APIFilter Definitions APIInsights APITeams APITimeline APISearch APIExtensibility APICognitive Service API

Update timeline

  1. investigating Oct 09, 2025, 09:07 AM UTC

    We are currently investigating an issue with the Quantive REST API not loading. This might result in inability to load your account data or load it only partially.

  2. identified Oct 09, 2025, 10:50 AM UTC

    Since 09:07 UTC on 09 October 2025, the Quantive has experienced intermittent loading issues, which may result in an inability to load account data or only partial data loading. This incident is related to a third-party vendor issue. Azure Front Door (AFD) has reported a significant capacity loss starting at 07:40 UTC, impacting services that rely on AFD, including Quantive. Azure is actively investigating the root cause. We are closely monitoring Azure’s updates and will provide further information as it becomes available.

  3. identified Oct 09, 2025, 01:20 PM UTC

    We identified the root cause of the issue to be related to an ongoing incident with our CDN provider. For more information, see: https://azure.status.microsoft/en-us/status. We will continue to update this incident accordingly.

  4. identified Oct 09, 2025, 02:38 PM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Oct 09, 2025, 03:40 PM UTC

    Microsoft has provided a fix for the underlying Azure Front Door incident. All Quantive accounts should now work as expected. We'll continue monitoring the application health and updating this incident accordingly until its final resolution.

  6. resolved Oct 10, 2025, 10:00 AM UTC

    This incident has been resolved.