Some Boleto payments not applied to customer accounts

At a glance · Microsoft's status

ResolvedLasted 28 days

Microsoft says it started
· on Microsoft Advertising platform health
First posted
on Microsoft Advertising platform health
Ended
· marked resolved
Affects
Microsoft Advertising
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, starting 09:18 UTC on 16 Sep. Microsoft marked it resolved at 23:25 UTC on 14 Oct after 28 days.

Microsoft says

Microsoft's latest update, , in short excerpts.

Starting Sep 16, 2026, at 9:18 AM UTC, some customers using Prepay Boleto payment method are not seeing their payments applied to their accounts even…

Microsoft,

Read the full update on Microsoft's status page

Timeline

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

  1. 16 Sep

    MicrosoftMicrosoft says it startedon Microsoft Advertising platform health

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

  3. 30 Sep+14 days

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

  4. 14 Oct+28 days 14 h

    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 Advertising
    Start time
    2026-09-16 09:18 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.

  2. Active ·

    Our Engineering teams remain actively engaged and are treating this issue with high priority.

  3. Active ·

    Our Engineering teams remain actively engaged and are treating this issue with high priority.

  4. Active ·

    Our Engineering teams remain actively engaged and are treating this issue with high priority.

  5. Active ·

    Our Engineering teams remain actively engaged and are treating this issue with high priority.

  6. Active ·

    Our Engineering teams remain actively engaged and are treating this issue with high priority.

  7. Active ·

    Our Engineering teams remain actively engaged and are treating this issue with high priority.

  8. Active ·

    Our Engineering teams remain actively engaged and are treating this issue with high priority.

  9. Active ·

    Our Engineering teams remain actively engaged and are treating this issue with high priority.

Show 2 earlier updates
  1. Active ·

  2. Active ·

Read the full update on Microsoft's status page

Last updated