Epicor experienced a major incident on October 15, 2026 affecting Kinetic - Singapore and Kinetic - Singapore and 1 more component, lasting 9h 7m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 15, 2026, 06:00 AM UTC
We are currently investigating an incident that is impacting a subset of customers in your region. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible. We will provide updates as we have them, and appreciate your patience while we work to resolve the issue.
- identified Oct 15, 2026, 07:35 AM UTC
We are continuing to investigate the incident affecting availability of Kinetic for some customers in Singapore. 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.
- identified Oct 15, 2026, 08:00 AM UTC
We are continuing to investigate an issue affecting Kinetic availability for some customers in Singapore. The underlying cause has not yet been identified. Our teams remain actively engaged in analyzing system behavior, service health, and supporting components to determine the source of the disruption. We appreciate your patience and will provide another update within 30 minutes, or sooner if there is a significant development.
- identified Oct 15, 2026, 08:30 AM UTC
We are actively investigating an issue affecting Kinetic availability for some customers in Singapore. The cause remains under review, and our teams are examining system activity and service dependencies to better understand the scope and source of the disruption. We recognize the impact this is having and will provide another update within 30 minutes, or sooner if new information becomes available.
- identified Oct 15, 2026, 09:00 AM UTC
We are continuing to investigate degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Customers may continue to experience slow response times, delays, or intermittent timeouts. Our technical teams are validating recovery actions and continuing to review the affected service components. The root cause has not yet been confirmed, and the incident remains ongoing. We apologize for the continued impact and will provide another update within 30 minutes, or sooner if there is a significant change.
- identified Oct 15, 2026, 09:31 AM UTC
We are continuing to investigate degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Our technical teams are reviewing database workload behavior and comparing it with normal operating patterns while recovery validation continues. The root cause has not yet been confirmed, and customers may continue to experience slow response times, delays, or intermittent timeouts. We apologize for the continued impact and will provide another update within 30 minutes, or sooner if there is a significant change.
- identified Oct 15, 2026, 10:00 AM UTC
We are continuing to investigate degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Our technical teams are reviewing service and application workload behavior, validating recovery actions, and engaging additional product specialists. The root cause has not yet been confirmed, and customers may continue to experience slow response times, delays, or intermittent timeouts. We apologize for the continued impact and will provide the next update in 30 minutes, or sooner if there is a significant change.
- identified Oct 15, 2026, 10:30 AM UTC
We are continuing to investigate degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Additional product engineering specialists are now engaged and are working with our database teams to analyze application and database workload behavior and evaluate recovery options. The root cause has not yet been confirmed, and customers may continue to experience slow response times, delays, or intermittent timeouts. We apologize for the continued impact and will provide the next update in 30 minutes, or sooner if there is a significant change.
- identified Oct 15, 2026, 11:00 AM UTC
We are continuing to investigate degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Our product engineering and database teams are jointly analyzing application and database workload behavior and evaluating potential recovery options. The root cause has not yet been confirmed, and customers may continue to experience slow response times, delays, or intermittent timeouts. We apologize for the continued impact and will provide the next update in 30 minutes or sooner if there is a significant change.
- identified Oct 15, 2026, 11:32 AM UTC
We are continuing to investigate degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Our product engineering team is conducting a detailed review of the application behavior identified during the investigation, with database specialists supporting analysis and service-health validation. The root cause has not yet been confirmed, and customers may continue to experience slow response times, delays, or intermittent timeouts. We apologize for the continued impact and will provide the next update in 30 minutes or sooner if there is a significant change.
- identified Oct 15, 2026, 12:00 PM UTC
We are continuing to investigate degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Our product engineering team is conducting a detailed review of the application behavior identified during the investigation, with database specialists supporting analysis and service-health validation. The root cause has not yet been confirmed, and customers may continue to experience slow response times, delays, or intermittent timeouts. We apologize for the continued impact and will provide the next update in 30 minutes or sooner if there is a significant change.
- identified Oct 15, 2026, 12:32 PM UTC
We have applied a corrective action for the degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Our teams are validating the change and closely monitoring application and database performance to confirm sustained recovery. The incident is not yet considered resolved, and some customers may continue to experience slow response times, delays, or intermittent timeouts during validation. We will provide another update within 30 minutes, or sooner if service stability is confirmed.
- identified Oct 15, 2026, 01:04 PM UTC
We have applied a mitigation for the degraded performance affecting Kinetic Public Cloud for some customers in the Singapore region. Service performance has returned to expected levels in the affected environments validated so far, and our teams are continuing to monitor application and database health to confirm sustained stability across the region. The incident is not yet considered resolved. We will provide the next update in 30 minutes or sooner if service stability is fully confirmed.
- identified Oct 15, 2026, 01:30 PM UTC
Service performance remains at expected levels in the affected environments validated so far. Our product engineering, database, and support specialists are continuing to monitor the environment and review additional safeguards intended to prevent a recurrence. The incident is not yet considered resolved. We will provide the next update in 30 minutes or sooner if sustained stability is fully confirmed.
- identified Oct 15, 2026, 02:00 PM UTC
Service performance remains at expected levels in the affected Kinetic Public Cloud environments validated so far. Our product engineering, database, and support teams are applying targeted safeguards to reduce the abnormal activity identified during the incident and are closely monitoring customer-facing performance and service health. The incident is not yet considered resolved. We will provide the next update 30 minutes or sooner if sustained stability is fully confirmed.
- identified Oct 15, 2026, 02:30 PM UTC
Service performance remains improved for Kinetic Public Cloud customers in the Singapore region. Our product engineering, database, and support teams are applying targeted safeguards and continuing recovery validation across the affected environments. The incident is not yet considered resolved, and our teams are closely monitoring service performance and system health to confirm sustained stability. We will provide the next update in 30 minutes or sooner if recovery is fully confirmed.
- identified Oct 15, 2026, 03:00 PM UTC
Service performance remains at expected levels in the affected Kinetic Public Cloud environments validated so far. We have expanded monitoring and are implementing additional safeguards while our product engineering, database, and support teams continue to confirm sustained stability across the Singapore region. The incident is not yet considered resolved. We will provide the next update in 30 minutes or sooner if service stability is fully confirmed.
- resolved Oct 15, 2026, 03:07 PM UTC
The degraded performance affecting Kinetic for some customers in Singapore 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.