ESET incident

ESET PROTECT's Integration with Microsoft services is not possible.

Minor Resolved View vendor source →

ESET experienced a minor incident on September 24, 2026 affecting Europe, Africa, Asia Pacific and Americas, Oceania and 1 more component, lasting 6d 8h. The incident has been resolved; the full update timeline is below.

Started
Sep 24, 2026, 11:08 PM UTC
Resolved
Oct 01, 2026, 08:06 AM UTC
Duration
6d 8h
Detected by Pingoru
Sep 24, 2026, 11:08 PM UTC

Affected components

Europe, Africa, Asia PacificAmericas, OceaniaJapanCanadaGermany

Update timeline

  1. investigating Sep 24, 2026, 11:08 PM UTC

    Redirection to Microsoft for providing consent returns error: "Failed to create connector" We are investigating the issue.

  2. identified Sep 28, 2026, 08:22 AM UTC

    Based on the information currently available, the issue appears to be isolated to a single customer, with no indications of a broader impact.

  3. identified Sep 28, 2026, 08:26 AM UTC

    At this time, we have received only one report regarding this issue. While we initially considered the possibility of a broader impact, we have not received any additional reports suggesting a global issue. As there are currently no further reports, we are setting the status to Monitoring and will continue to monitor the situation.

  4. identified Sep 28, 2026, 08:26 AM UTC

    At this time, we have received only one report regarding this issue. While we initially considered the possibility of a broader impact, we have not received any additional reports suggesting a global issue. As there are currently no further reports, we are setting the status to Monitoring and will continue to monitor the situation.

  5. monitoring Sep 28, 2026, 08:27 AM UTC

    At this time, we have received only one report regarding this issue. While we initially considered the possibility of a broader impact, we have not received any additional reports suggesting a global issue. As there are currently no further reports, we are setting the status to Monitoring and will continue to monitor the situation.

  6. resolved Oct 01, 2026, 08:06 AM UTC

    The issue has been resolved.