KORE incident

KORE - Update Season Records

Resolved after 10 days 22 hours, affecting Audience Intelligence: Ticketing & Engagement and Audience Intelligence: Ticketing & Engagement (Audience Intelligence: Ticketing & Engagement — North America) and 1 more, on April 2, 2026.

resolved Apr 13, 2026, 02:08 PM UTC

A fix has been deployed, and the issue preventing clients using the Classic UI from updating season records within Configuration Records has been resolved. Thank you for your patience.

Started
Apr 02, 2026, 03:26 PM UTC
Resolved
Apr 13, 2026, 02:08 PM UTC
Duration
10d 22h
Detected by Pingoru
Apr 02, 2026, 03:26 PM UTC

Affected components

Audience Intelligence: Ticketing & EngagementAudience Intelligence: Ticketing & Engagement (Audience Intelligence: Ticketing & Engagement — North America)Audience Intelligence: Ticketing & Engagement (Audience Intelligence: Ticketing & Engagement — Europe)Audience Intelligence: Ticketing & Engagement (Audience Intelligence: Ticketing & Engagement — Asia Pacific)Partnership Intelligence: SponsorshipPartnership Intelligence: Sponsorship (Partnership Intelligence: Sponsorship — North America)Partnership Intelligence: Sponsorship (Partnership Intelligence: Sponsorship — Europe)Partnership Intelligence: Sponsorship (Partnership Intelligence: Sponsorship — Asia Pacific)Partnership Intelligence: Suites & PremiumPartnership Intelligence: Suites & Premium (Partnership Intelligence: Suites & Premium — North America)

Update timeline

  1. investigating Apr 02, 2026, 03:26 PM UTC

    We are investigating an issue preventing clients using the Classic UI from updating season records within the Configuration Records. Our development team is actively investigating the issue. We’ll provide an update as soon as more information becomes available.

  2. identified Apr 02, 2026, 06:11 PM UTC

    We’ve identified the root cause of the issue preventing clients using the Classic UI from updating season records within Configuration Records. Our development team is actively working on a fix. We’ll share another update as soon as more information becomes available.

  3. identified Apr 03, 2026, 03:09 PM UTC

    Thank you for your patience. Our team is making progress on a fix and is continuing to work toward deployment. We’ll provide another update once we have a confirmed deployment timeline.

  4. identified Apr 07, 2026, 11:09 PM UTC

    Thank you for your patience. Our team has made progress on a fix and is targeting a release to production on the evening of Thursday, April 9. We’ll provide another update once deployment is complete.

  5. resolved Apr 13, 2026, 02:08 PM UTC

    A fix has been deployed, and the issue preventing clients using the Classic UI from updating season records within Configuration Records has been resolved. Thank you for your patience.

Your product runs on more than KORE

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →