Inriver incident

Degraded Performance in Prod US

Minor Resolved View vendor source →

Inriver experienced a minor incident on June 16, 2026, lasting 21h 15m. The incident has been resolved; the full update timeline is below.

Started
Jun 16, 2026, 06:43 PM UTC
Resolved
Jun 17, 2026, 03:59 PM UTC
Duration
21h 15m
Detected by Pingoru
Jun 16, 2026, 06:43 PM UTC

Update timeline

  1. investigating Jun 16, 2026, 06:43 PM UTC

    An isssue has been acknowledged and is being investigated.

  2. investigating Jun 16, 2026, 08:37 PM UTC

    Investigating We are actively investigating reports of degraded performance affecting the Web Portal, Rest API, and Connect services in the US Production environment. Customers may experience slower-than-normal response times and intermittent errors while using the platform. Our Engineering and SRE teams are actively engaged and working to identify the root cause. We will continue to provide updates as more information becomes available.

  3. investigating Jun 17, 2026, 08:03 AM UTC

    We are continuing to investigate degraded performance affecting the Web Portal, Rest API, and Connect services in the US Production environment. Customers may experience slower-than-normal response times and intermittent errors while using the platform. We have seen some improvements, but we will continue the investigation. Next update by 5:00 AM CDT

  4. monitoring Jun 17, 2026, 09:28 AM UTC

    We have mitigated the degraded performance affecting the Web Portal, Rest API, and Connect services in the US Production environment. We are monitoring the system to confirm recovery. Next update at ~7:00 CDT

  5. monitoring Jun 17, 2026, 12:01 PM UTC

    We are continuing to monitor to confirm system recovery. Next update at ~9:00 CDT

  6. monitoring Jun 17, 2026, 01:37 PM UTC

    We are continuing to monitor to confirm system recovery. Next update at ~11:00 CDT

  7. resolved Jun 17, 2026, 03:59 PM UTC

    System stability and performance have been maintained throughout our monitoring period, with no further issues identified. The issue has been successfully resolved.