Epicor incident

Kinetic - Americas Service Outage

Major Resolved View vendor source →

Epicor experienced a major incident on September 20, 2026 affecting Kinetic - Americas and Kinetic and 1 more component, lasting 5h 59m. The incident has been resolved; the full update timeline is below.

Started
Sep 20, 2026, 01:51 PM UTC
Resolved
Sep 20, 2026, 07:50 PM UTC
Duration
5h 59m
Detected by Pingoru
Sep 20, 2026, 01:51 PM UTC

Affected components

Kinetic - AmericasKineticKineticKineticKineticKineticKineticKineticKineticKinetic

Update timeline

  1. identified Sep 20, 2026, 01:51 PM UTC

    We are currently investigating an incident affecting availability of Kinetic for the customers with the following account numbers: 10138, 157104, 166610, 62041, 68751, 168474, 66064, 19637, 69185, 69197, 163621, 63092, 165261, 157194, 166646, 64053, 78789, 69783, 11092, 168217, 90743, 97271, 69100, 165614, 165276, 69367, 166435, 29149, 99609, 165594, 162339, 19330, 167821, 97162, 106166, 166917, 69721, 160525, 67405, 14113, 27739, 158059, 156530, 29290, 79252, 168111, 14807, 78746, 29552, 69860, 27415, 69398, 165371, 27600, 00000, 167243, 167679, 93802, 169168, 168854, 166611, 93723, 94926, 162164, 14577, 167555, 27862, 168125, 165083, 64464, 93420, 92985, 27638, 161980, 95779, 169323, 160998, 93333, 68969, 14556, 68123, 68935, 97040, 28207, 167393, 93064, 158203. Our technical teams are fully engaged and working to restore service as quickly as possible. We apologize for the impact to your operations and will provide the next update within 60 minutes, or sooner if there is a significant change.

  2. identified Sep 20, 2026, 02:56 PM UTC

    We are continuing to investigate the incident affecting availability of Kinetic for some customers in Americas Live. The root cause has not yet been confirmed. Our teams are continuing to review service health, system activity, and related components to determine the cause and restore service. We apologize for the ongoing disruption and will provide the next update within 30 minutes, or sooner if there is a significant change.

  3. identified Sep 20, 2026, 03:50 PM UTC

    We are continuing to investigate the incident affecting availability of Kinetic Public Cloud for some customers in the US region. Our technical teams are actively working to restore service, and recovery actions are currently in progress. The root cause has not yet been confirmed. We apologize for the ongoing disruption and will provide another update as recovery progresses, or sooner if there is a significant change.

  4. identified Sep 20, 2026, 04:44 PM UTC

    We are continuing to investigate the incident affecting printing functionality for Kinetic Public Cloud for some customers in US region . The root cause has not yet been confirmed. Affected customers may continue to experience failures, delays, or pending print jobs while our teams work to identify the cause and restore printing functionality. We apologize for the continued disruption and will provide the next update within 30 minutes, or sooner if there is a significant change.

  5. identified Sep 20, 2026, 05:30 PM UTC

    We are continuing to investigate the incident affecting printing functionality for Kinetic Public Cloud for some customers in US region . The root cause has not yet been confirmed. Affected customers may continue to experience failures, delays, or pending print jobs while our teams work to identify the cause and restore printing functionality. We apologize for the continued disruption and will provide the next update within 30 minutes, or sooner if there is a significant change.

  6. identified Sep 20, 2026, 05:55 PM UTC

    A mitigation has been applied for the incident affecting printing functionality in Kinetic Public Cloud for some customers in US region. Printing services are showing signs of recovery, and our teams are monitoring closely to confirm that print jobs are completing successfully. The incident is not yet considered resolved. We will provide another update within 30 minutes, or a resolution notice once sustained stability has been confirmed.

  7. identified Sep 20, 2026, 06:26 PM UTC

    A mitigation has been applied for the incident affecting printing functionality in Kinetic Public Cloud for some customers in US region. Printing services are showing signs of recovery, and our teams are monitoring closely to confirm that print jobs are completing successfully. The incident is not yet considered resolved. We will provide another update within 30 minutes, or a resolution notice once sustained stability has been confirmed.

  8. identified Sep 20, 2026, 06:56 PM UTC

    A mitigation has been applied for the incident affecting printing functionality in Kinetic Public Cloud for some customers in US region. Printing services are showing signs of recovery, and our teams are monitoring closely to confirm that print jobs are completing successfully. The incident is not yet considered resolved. We will provide another update within 30 minutes, or a resolution notice once sustained stability has been confirmed.

  9. identified Sep 20, 2026, 07:32 PM UTC

    A mitigation has been applied for the incident affecting printing functionality in Kinetic Public Cloud for some customers in US region. Printing services are showing signs of recovery, and our teams are monitoring closely to confirm that print jobs are completing successfully. The incident is not yet considered resolved. We will provide another update within 30 minutes, or a resolution notice once sustained stability has been confirmed.

  10. resolved Sep 20, 2026, 07:50 PM UTC

    The incident affecting printing functionality in Kinetic Public Cloud for some customers in US region. has been resolved. Printing services have been restored, and our teams have confirmed that print jobs are processing successfully. We apologize for the disruption and appreciate your patience while we worked to restore this functionality. If you continue to experience any printing issues, please raise a ticket through the EpicCare Service Portal.