Oracle Aconex incident

Multiple Instances - Service issue impacting Cross Project Search

Major Resolved View vendor source →

Oracle Aconex experienced a major incident on June 4, 2026 affecting Search and Search and 1 more component, lasting 4d 12h. The incident has been resolved; the full update timeline is below.

Started
Jun 04, 2026, 01:38 AM UTC
Resolved
Jun 08, 2026, 02:09 PM UTC
Duration
4d 12h
Detected by Pingoru
Jun 04, 2026, 01:38 AM UTC

Affected components

SearchSearchSearchSearch

Update timeline

  1. investigating Jun 04, 2026, 01:38 AM UTC

    We have identified an issue that may result in intermittent service interruption. We are actively engaged and focused on resolving the issue as quickly as possible. We will provide regular updates and remain committed to your success. The next update will be in 60 minutes.

  2. investigating Jun 04, 2026, 01:57 AM UTC

    Our engineers are continuing to work toward resolving the issue that may be impacting your user experience. We are committed to resolving this issue as quickly as possible. The next update will be in 60 minutes.

  3. investigating Jun 04, 2026, 03:09 AM UTC

    Our engineers are continuing to work towards resolving the unplanned service outage. Thank you for your continued patience. The next update will be in 60 minutes.

  4. investigating Jun 04, 2026, 04:20 AM UTC

    We are actively working to resolve the unplanned service outage. We understand that it's impacting your experience and are committed to resolving the issue as quickly as possible. The next update will be in 60 minutes.

  5. investigating Jun 04, 2026, 05:20 AM UTC

    We are continuing to investigate this issue. We apologize for any inconvenience caused and thank you for your continued patience. The next update will be in 60 minutes.

  6. investigating Jun 04, 2026, 06:55 AM UTC

    Our engineers are actively working on resolving the current issue. While we are making progress, our recovery time has been extended as we continue to work toward mitigation. We are committed to resolving this issue as quickly as possible. The next update will be in 60 minutes.

  7. investigating Jun 04, 2026, 08:43 AM UTC

    Our engineers are actively working on resolving the current issue. While we are making progress, our recovery time has been extended as we continue to work toward mitigation. We are committed to resolving this issue as quickly as possible. The next update will be in 60 minutes.

  8. investigating Jun 04, 2026, 11:25 AM UTC

    Our engineers are actively working on resolving the current issue. While we are making progress, our recovery time has been extended as we continue to work toward mitigation. We are committed to resolving this issue as quickly as possible. The next update will be in 60 minutes.

  9. resolved Jun 08, 2026, 02:09 PM UTC

    The root cause of the issue has been identified, and our engineering teams are actively working on a permanent fix. We appreciate your patience and understanding as we complete the necessary remediation activities. A fix is targeted tentatively for inclusion in the June 20, 2026, release.