Microsoft Advertising Share of Voice (SOV) Data is delayed

At a glance · Microsoft's status

ResolvedLasted 26 h 23 min

Microsoft says it started
· on Microsoft Advertising platform health
First posted
on Microsoft Advertising platform health
Ended
· marked resolved
Affects
Microsoft Advertising, Microsoft Advertising API
Edited
Not since we first saw it
Source
Microsoft Advertising platform health · checked 1 min ago

In short

Microsoft reported degraded service affecting Microsoft Advertising and Microsoft Advertising API, starting 21:02 UTC on 22 Oct. Microsoft marked it resolved at 23:25 UTC on 23 Oct after 26 h 23 min.

Microsoft says

Microsoft's latest update, , in short excerpts.

Starting Oct 22, 2026, at 09:02 PM UTC, Microsoft Advertising Share of Voice (SOV) data may be delayed by up to 25 hours.

Microsoft,

Read the full update on Microsoft's status page

Timeline

Times in UTC, Microsoft's own where it gives them.

  1. 22 Oct

    MicrosoftMicrosoft says it startedon Microsoft Advertising platform health

  2. between Microsoft's stated start and its first public word

  3. 23 Oct+5 h 23 min

    MicrosoftFirst public postFrom Microsoft's own incident history, before our archive started.

  4. +26 h 23 min

    MicrosoftResolved

What Microsoft changed

Microsoft adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on Microsoft's page.

One version so far. If Microsoft edits it, each change shows here with what was removed and added.

  1. First version we captured ·

    As first seen: Fixed · 2 services
    Status
    Fixed
    Services
    Microsoft Advertising, Microsoft Advertising API
    Start time
    2026-10-22 21:02 UTC.

    Seen by us · Microsoft's timestamp · Microsoft's page

Affected services

Official updates

Posted by Microsoft Advertising platform health, newest first. The newest are quoted in their first sentence; the full text of each is on Microsoft's page.

  1. Resolved ·

    Our Engineering team has resolved the issue and data has now caught up.

  2. Active ·

    Engineering team has been engaged and is working on the issue with priority.

  3. Active ·

    Engineering team has been engaged and is working on the issue with priority.

Read the full update on Microsoft's status page

Last updated