ESET incident

ESET Inspect instances may experience degraded performance

Major Resolved View vendor source →

ESET experienced a major incident on November 13, 2025 affecting Japan, lasting 4d 22h. The incident has been resolved; the full update timeline is below.

Started
Nov 13, 2025, 10:24 AM UTC
Resolved
Nov 18, 2025, 09:13 AM UTC
Duration
4d 22h
Detected by Pingoru
Nov 13, 2025, 10:24 AM UTC

Affected components

Japan

Update timeline

  1. investigating Nov 13, 2025, 10:24 AM UTC

    Some instances in various regions are experiencing heavily degraded performance. The issue is under investigation, so far no ETA available.

  2. identified Nov 13, 2025, 05:52 PM UTC

    • Japan region is fully restored and stable. • Other regions are undergoing restoration efforts, but stability is not yet achieved. We cannot provide a firm ETA for full global stability yet. Restoration is ongoing, and updates will follow as soon as progress is confirmed.

  3. identified Nov 13, 2025, 06:13 PM UTC

    • JPN and EU regions are fully restored and stable. • US, CA & DE data centers are undergoing restoration efforts, but stability is not yet achieved. Next update in 2 hours.

  4. monitoring Nov 13, 2025, 07:43 PM UTC

    Currently, all 5 regions, including the latest Noram and Canada since 90min, US 45min, are stable. We will monitor it for next 2h.

  5. investigating Nov 14, 2025, 08:07 AM UTC

    The performance is again degraded for some instances in various regions. We are consulting the issue with Microsoft.

  6. monitoring Nov 14, 2025, 01:00 PM UTC

    We're identified the issue and monitoring the situation now.

  7. investigating Nov 17, 2025, 09:37 AM UTC

    We are currently investigating this issue.

  8. investigating Nov 17, 2025, 10:22 AM UTC

    JPN region is experiencing the slowness. We are currently investigating this issue.

  9. identified Nov 17, 2025, 12:05 PM UTC

    The issue has been identified and a fix is being implemented.

  10. monitoring Nov 17, 2025, 12:06 PM UTC

    We've identified and mitigated the performance issues, all instances should be operating as expected

  11. monitoring Nov 17, 2025, 01:55 PM UTC

    We are continuing to monitor for any further issues.

  12. resolved Nov 18, 2025, 09:13 AM UTC

    This incident has been resolved.