Epicor incident

Kinetic - Performance Degraded

Major Resolved View vendor source →

Epicor experienced a major incident on July 31, 2026 affecting Kinetic and Kinetic and 1 more component, lasting 15h 30m. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2026, 03:30 PM UTC
Resolved
Aug 01, 2026, 07:00 AM UTC
Duration
15h 30m
Detected by Pingoru
Jul 31, 2026, 03:30 PM UTC

Affected components

KineticKineticKineticKineticKineticKineticKineticKineticKineticKinetic

Update timeline

  1. investigating Jul 31, 2026, 03:30 PM UTC

    We are currently investigating an incident that may be causing degraded performance in Production environment for some customers in US region. Customers may experience slow response times or intermittent delays while using the service. Our technical teams are actively investigating and working to restore normal performance. We apologize for any disruption and will provide the next update within 60 minutes, or sooner if there is a significant change.

  2. investigating Jul 31, 2026, 05:24 PM UTC

    We have identified the root cause of degraded performance affecting Production environment for some customers in US region . Our technical teams are implementing corrective actions to restore normal performance levels. Customers may continue to experience delays or slower-than-expected response times while remediation is in progress. We will provide the next update within 30 minutes, or sooner if normal performance is restored.

  3. investigating Jul 31, 2026, 07:00 PM UTC

    Corrective mitigation is currently being applied to address the degraded performance affecting some customers in the US Production environment. Our technical teams are monitoring service health closely as the remediation progresses. Customers may continue to experience delays or slower-than-expected response times during this work. The incident is not yet considered resolved. We will provide the next update within 30 minutes.

  4. investigating Jul 31, 2026, 10:00 PM UTC

    Corrective mitigation measures continues to be applied to address the degraded performance affecting some customers in the Americas Production environment. Our technical teams are monitoring service health closely as the remediation progresses. Customers may continue to experience delays or slower-than-expected response times during this work. The incident is not yet considered resolved. We will provide the next update within 60 minutes.

  5. investigating Jul 31, 2026, 11:00 PM UTC

    Corrective mitigation measures continues to be applied to address the degraded performance affecting some customers in the Americas Production environment. Our technical teams are monitoring service health closely as the remediation progresses. Customers may continue to experience delays or slower-than-expected response times during this work. The incident is not yet considered resolved. We will provide the next update within 60 minutes.

  6. investigating Aug 01, 2026, 12:27 AM UTC

    We identified a service issue that temporarily affected performance for certain customers in the Americas region. Service performance is improving, and our teams are monitoring closely to confirm that response times have returned to expected levels. Our teams are continuing their investigation into the root cause while closely monitoring the environment to ensure ongoing stability. We apologize for any inconvenience experienced and will provide further updates as they become available.

  7. investigating Aug 01, 2026, 01:20 AM UTC

    We identified a service issue that temporarily impacted performance for a subset of customers in the Americas region. Service responsiveness is improving, and we are observing positive recovery trends as response times continue to normalize. Our teams remain engaged in determining the root cause and are closely observing the environment to ensure sustained stability. We apologize for any inconvenience and will share further updates as new information becomes available.

  8. investigating Aug 01, 2026, 02:09 AM UTC

    We identified a service issue that temporarily impacted performance for a subset of customers in the Americas region. Conditions have improved, and key performance indicators continue to trend toward normal operating levels. Our teams are actively reviewing the incident to identify the underlying cause while maintaining enhanced monitoring across the environment. We apologize for any inconvenience and will provide additional updates as they become available.

  9. investigating Aug 01, 2026, 02:56 AM UTC

    We previously identified an issue that affected performance for a subset of customers in the Americas region. Service health continues to improve, and current metrics indicate that system performance is returning to expected levels. Our teams are continuing to monitor the environment to ensure continued stability. We appreciate your patience and will share further updates as they become available.

  10. investigating Aug 01, 2026, 03:14 AM UTC

    We previously identified a performance issue affecting a subset of customers in the Americas region. Service metrics continue to show improvement, with the environment operating within expected parameters. Our teams remain engaged and are closely monitoring the platform to ensure ongoing stability. We appreciate your patience and will provide further updates as warranted.

  11. investigating Aug 01, 2026, 04:11 AM UTC

    We previously identified a performance issue impacting a subset of customers in the Americas region. Current monitoring indicates that service levels remain stable, with performance operating within normal expectations. Our teams continue to closely observe the environment to ensure a consistent customer experience. We appreciate your patience and will provide additional updates if there are any significant developments.

  12. investigating Aug 01, 2026, 04:43 AM UTC

    We previously reported a performance degradation affecting a subset of customers in the Americas region. Current service indicators remain healthy, and system responsiveness continues to operate within expected thresholds. Our teams continue to closely observe the environment to ensure a consistent customer experience. We appreciate your patience and will provide additional updates if there are any significant developments.

  13. investigating Aug 01, 2026, 05:25 AM UTC

    We previously reported a service disruption affecting a subset of customers in the Americas region. Current observations show normal platform behavior, with application responsiveness remaining within expected ranges. Our teams continue to closely observe the environment to ensure a consistent customer experience. We appreciate your patience and will provide additional updates if there are any significant developments.

  14. investigating Aug 01, 2026, 06:11 AM UTC

    We previously communicated a service disruption affecting a subset of customers in the Americas region. Current performance metrics indicate that services are operating normally, and no further impact has been observed. Our teams remain engaged and continue to review the environment to confirm ongoing reliability. Thank you for your patience, and we will share any notable developments as they arise.

  15. resolved Aug 01, 2026, 07:00 AM UTC

    The degraded performance affecting Kinetic for some customers in America region has been resolved. Service performance has returned to expected levels, and our teams have confirmed stability through monitoring. We apologize for the disruption and appreciate your patience while we worked to restore normal performance. If you continue to experience any issues, please raise a ticket through the EpicCare Service Portal.