Trend Micro incident

XBC, XES functions unavailable

Major Resolved View vendor source →

Trend Micro experienced a major incident on March 1, 2026 affecting TrendAI Vision One™, lasting 6d 2h. The incident has been resolved; the full update timeline is below.

Started
Mar 01, 2026, 11:00 PM UTC
Resolved
Mar 08, 2026, 01:00 AM UTC
Duration
6d 2h
Detected by Pingoru
Mar 01, 2026, 11:00 PM UTC

Affected components

TrendAI Vision One™

Update timeline

  1. investigating Mar 01, 2026, 11:00 PM UTC

    TrendAI service engineers are actively investigating a potential issue that may be affecting our customers. Some services may experience temporary degradation or intermittent availability. We are working to identify the specific impact and resolve the issue as quickly as possible. We apologize for the inconvenience and greatly appreciate your patience as we work towards a prompt resolution.

  2. investigating Mar 02, 2026, 02:00 AM UTC

    Trend Micro service engineers have successfully identified the cause of the incident and are actively developing a solution to mitigate the impact. More information will be posted as available, and we greatly appreciate your patience as we work towards a resolution.

  3. investigating Mar 02, 2026, 06:00 PM UTC

    TrendAI service engineers are still addressing an ongoing issue; however, some services may currently be partially or intermittently available. We are continuing to work towards a resolution and restoring full services as soon as possible. More information will be posted as available, and we greatly appreciate your patience.

  4. investigating Mar 04, 2026, 07:30 AM UTC

    TrendAI service engineers are continuing to work towards a resolution and restoring full services as soon as possible; however, some services may currently be partially or intermittently available. More information will be posted as available, and we greatly appreciate your patience.

  5. investigating Mar 04, 2026, 04:39 PM UTC

    The root cause has been addressed and maintenance mode has been lifted. Service availability has been restored; however, a delay may be experienced in new policy/setting changes taking effect as changes will be processed when the backlog has cleared (estimated backlog processing time: up to 24 hours). We apologize for the inconvenience and greatly appreciate your patience as services are fully recovering.

  6. investigating Mar 05, 2026, 05:30 PM UTC

    The root cause has been addressed and maintenance mode has been lifted. Service availability has been restored. Backlog processing has completed for the AU, CA, JP, IN, and UK regions; however, backlog processing is still ongoing in the EU, SG, and US regions. As a result, there may be a delay in new policy or setting changes taking effect until the remaining backlog has cleared. We apologize for the inconvenience and greatly appreciate your patience as services are fully recovering.

  7. investigating Mar 06, 2026, 04:30 AM UTC

    The root cause has been addressed and maintenance mode has been lifted. Service availability has been restored. Backlog processing has completed for the AU, CA, JP, IN, SG, and UK regions; however, backlog processing is still ongoing in the EU and US regions. As a result, there may be a delay in new policy or setting changes taking effect until the remaining backlog has cleared. We apologize for the inconvenience and greatly appreciate your patience as services are fully recovering.

  8. investigating Mar 07, 2026, 02:00 AM UTC

    The root cause has been addressed and maintenance mode has been lifted. Service availability has been restored. Backlog processing has completed for the AU, CA, JP, IN, SG, UK and US regions; however, backlog processing is still ongoing in the EU region. As a result, there may be a delay in new policy or setting changes taking effect until the remaining backlog has cleared. We apologize for the inconvenience and greatly appreciate your patience as services are fully recovering.

  9. resolved Mar 08, 2026, 01:00 AM UTC

    TrendAI service engineers have confirmed that the implemented solution has resolved the issue. All affected services are considered back to normal and the issue has been resolved.