Temporary Microsoft Monetize and Curate Platform Disruption

At a glance · Microsoft's status

ResolvedLasted 8 h 32 min

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

In short

Microsoft reported a major outage affecting Microsoft Monetize and Curate, starting 18:25 UTC on 21 Oct. Microsoft marked it resolved at 02:57 UTC on 22 Oct after 8 h 32 min.

Microsoft says

Microsoft's latest update, , in short excerpts.

Microsoft Advertising is aware of the recently disclosed security vulnerabilities affecting PHP, a third-party open-source software used broadly across the industry.

Microsoft,

Read the full update on Microsoft's status page

Timeline

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

  1. 21 Oct

    MicrosoftMicrosoft says it startedon Microsoft Advertising platform health

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

  3. 22 Oct+8 h 32 min

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

  4. +8 h 32 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 · 1 service
    Status
    Fixed
    Services
    Microsoft Monetize and Curate
    Start time
    2026-10-21 18:25 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.

Read the full update on Microsoft's status page

Last updated