KORE Outage History

Started Jul 24, 2026, 06:20 PM UTC· resolved Jul 26, 2026, 06:46 PM UTC

1. investigating Jul 24, 2026, 06:20 PM UTC

   There is an outage affecting multiple clients using Salesforce integrated Kore pages. We are actively investigating the root cause and the quickest path to resolution. We will provide updates as soon as more information becomes available.

2. identified Jul 24, 2026, 07:18 PM UTC

   We have identified that the issue is affecting a subset of our Saleforce integrated clients that have "Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows" active. We are currently determining next steps to resolve the resulting connectivity issue.

3. identified Jul 25, 2026, 01:16 AM UTC

   We have identified the issue is isolated to certain organizations that use the standard KORE Connected App to authenticate between Salesforce and the KORE platform (Standalone and Dynamics 365 clients are not impacted). A recent change to Salesforce's security requirements has introduced an authentication method (PKCE) that is not yet supported by the current KORE platform integration. As a result, users may be unable to authenticate or access KORE functionality through Salesforce. We recognize the impact this has on your team and are treating the issue as a top priority. We are pursuing three resolution paths in parallel: 1. Salesforce configuration update We are working directly with Salesforce to determine whether the newly enforced setting can be adjusted on the existing KORE Connected App. 2. Emergency KORE platform patch Our engineering team is preparing a compatibility update so that the KORE platform can support the updated authentication requirements. 3. Client-specific Connected App workaround For clients who need functionality restored immediately, we can support the creation of a dedicated Connected App within your Salesforce environment. This requires coordination with your Salesforce administrator, with Two Circles supporting the configuration and transition. We will provide further updates as soon as we have confirmed progress. If your team requires access before Monday, please let us know and we will coordinate directly with your Salesforce administrator to implement the client-specific Connected App workaround. We apologize for the disruption and appreciate your patience while we work to restore full functionality.

4. identified Jul 25, 2026, 09:01 PM UTC

   Our engineering team has made progress on the emergency platform patch. A fix has now been deployed that restores functionality for a subset of affected Salesforce users. Users with an existing, valid authentication session should begin to regain access to KORE functionality through Salesforce. During validation, we identified an additional scenario that may continue to affect some users. Users who need to reauthorize the KORE platform, or whose Salesforce authentication token needs to be renewed through the platform’s automated background process, may still be unable to authenticate. Our engineering team is actively working on a further patch to address this remaining scenario and restore full functionality for all affected users. We continue to treat this as a top-priority incident and will provide another update as soon as the additional fix has been deployed and validated. We apologize for the continued disruption and appreciate your patience.

5. monitoring Jul 26, 2026, 05:46 AM UTC

   The additional platform patch was deployed this evening, and the remaining authentication issues should now be resolved. Our team is continuing to monitor the environment closely. Should your organization or any of your users experience further issues, please notify your Client Lead and open a support ticket with our team so we can investigate promptly. We apologize for the inconvenience and disruption this incident has caused, and we appreciate your patience while our team worked to restore full functionality.

6. resolved Jul 26, 2026, 06:46 PM UTC

   Our testing, including validation with an affected user, has confirmed that the issue appears to be resolved. We are now closing this incident. As always, please keep us apprised if your organization or users experience any further issues. Our team is also reviewing the circumstances around this incident and our internal processes to identify improvements that will help us respond more effectively and reduce the risk of similar disruptions in the future. We apologize again for the inconvenience and appreciate your patience throughout the resolution.

Read the full incident report →

Started Apr 24, 2026, 02:54 PM UTC· resolved Apr 24, 2026, 04:33 PM UTC

1. investigating Apr 24, 2026, 02:54 PM UTC

   We are currently investigating an issue preventing from accessing KORE pages, including deal sheets and the ticket transaction tool. Our development team is actively investigating the issue. We will provide further updates as more information becomes available.

2. monitoring Apr 24, 2026, 03:25 PM UTC

   A fix has been implemented for the issue impacting access to KORE pages. This issue was caused by a change deployed yesterday, which has now been rolled back. We are seeing recovery and continuing to monitor system performance.

3. resolved Apr 24, 2026, 04:33 PM UTC

   The issue impacting access to KORE pages has been resolved. All services are now operating normally.

Read the full incident report →

Started Apr 02, 2026, 03:26 PM UTC· resolved Apr 13, 2026, 02:08 PM UTC

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.

Read the full incident report →

Started Mar 13, 2026, 07:46 PM UTC· resolved Mar 17, 2026, 08:47 PM UTC

1. identified Mar 13, 2026, 07:46 PM UTC

   We have identified an issue affecting Premium Deals. When attempting to reset the workflow, users may encounter an error. Additionally, the hyperlink within the approval email that navigates to the associated account may be broken. Our development team is actively investigating and working on a fix. We will provide another update as soon as a release date for the resolution is confirmed. Please use the below temporary workarounds until a fix is deployed Workaround for Resetting the Approval Workflow: Open the Premium Deal flat form and manually update the "Premium Deal Status" to the desired state, then execute the workflow. Workaround for Approval Email Account Hyperlink: In the meantime, users can access the relevant account by logging directly into the CRM and navigating to the account associated with the deal sheet referenced in the approval email. We appreciate your patience and will share further updates as they become available.

2. monitoring Mar 17, 2026, 01:58 PM UTC

   A fix has now been successfully released to production for the previously identified issue affecting Premium Deals. Our team is actively monitoring performance to ensure stability. We appreciate your patience and will continue to provide updates if any further action is required.

3. resolved Mar 17, 2026, 08:47 PM UTC

   This issue affecting Premium Deals has now been fully resolved. Our team has confirmed that systems are operating as expected following the fix implemented in production. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Started Feb 24, 2026, 03:49 PM UTC· resolved Feb 24, 2026, 06:40 PM UTC

1. identified Feb 24, 2026, 03:49 PM UTC

   We have identified an issue on the deal sheet rollover tool that prevents organizations that use rounds with round order specified from rolling over assets to the next season of a deal. Our development team is working on a fix for this issue, are working to patch a fix soon, with a hopeful ETA of later today. We will return once there is an update.

2. resolved Feb 24, 2026, 06:40 PM UTC

   Our Partnerships Intelligence team has patched a fix for this issue into production and we have validated the issue has since been resolved. We thank you for your patience and continued partnership.

Read the full incident report →

Started Feb 19, 2026, 07:26 PM UTC· resolved Mar 06, 2026, 04:09 PM UTC

1. identified Feb 19, 2026, 07:26 PM UTC

   We have identified an issue with the supporting infrastructure behind our Data Warehouse and Analytics platform. As a result, data from KORE integrations may be slow to load in client warehouses and/or appear in a failed state. We are working with our Engineering teams to mitigate this issue and restore the platform to normal operation. We will update this page with additional information as we progress.

2. monitoring Feb 19, 2026, 09:23 PM UTC

   We have put a fix in place to address backend infrastructure performance issues and are monitoring affected integrations.

3. resolved Mar 06, 2026, 04:09 PM UTC

   We experienced a temporary service disruption that was fully resolved the same day. Since resolution, we have closely monitored the platform for two weeks with no further occurrences. In addition, we have strengthened our daily monitoring processes to help detect potential issues earlier and minimize any future impact to our clients.

Read the full incident report →

Started Feb 13, 2026, 10:39 PM UTC· resolved Feb 24, 2026, 04:51 PM UTC

1. identified Feb 13, 2026, 10:39 PM UTC

   We have identified an issue with a backend process whereby not all changes to Shopify source records are being ingested. This impacts a small subset of clients using the Integration Framework for Shopify. The legacy Shopify integration continues to function as expected. We are currently implementing an automated backfill to ensure the data is fully reconciled and to resolve the issue. We are working on implementing an automated backfill to ensure the data is fully reconciled and the issue is resolved.

2. monitoring Feb 24, 2026, 01:06 AM UTC

   Automated backfill has been implemented for all affected clients. We will continue to monitor and verify that the issue has been fully resolved.

3. resolved Feb 24, 2026, 04:51 PM UTC

   The automated backfill of any delayed or missing data resulting from this incident for the Shopify Integration has been successfully completed. We appreciate your continued patience and understanding while we worked to resolve this issue.

Read the full incident report →

Started Jan 29, 2026, 04:36 PM UTC· resolved Jan 30, 2026, 09:53 PM UTC

1. investigating Jan 29, 2026, 04:36 PM UTC

   We have identified an issue regarding the filter on multiple Sponsorship and Suites and Premium Pages (i.e. deal sheets, inventory, premium deals, etc.). Currently, the filter button is not operational and is not applying any new filters added. Our Partnerships Intelligence team is aware and are investigating the issue. We will update you once we have more information. Thank you for your patience!

2. identified Jan 29, 2026, 05:45 PM UTC

   We have identified the root cause of the filters not functioning and our Partnerships Intelligence team will be patching a fix to production this evening to resolve this bug. We apologize for any inconvenience this may have caused, and we appreciate your partnership.

3. resolved Jan 30, 2026, 09:53 PM UTC

   We have implemented a fix for the issue that was causing the filter button to be inoperable. The Filter button should now show a page's current filters and allow users to adjust and save the filters, as well. We apologize for any inconvenience this may have caused, and we appreciate your patience and partnership.

Read the full incident report →

Started Jan 22, 2026, 10:12 PM UTC· resolved Feb 05, 2026, 05:00 PM UTC

1. identified Jan 22, 2026, 10:12 PM UTC

   Over the past ~48 hours, we have observed failures in the Facebook Marketing ETL affecting multiple clients. The issue is caused by throttling from the Meta (Facebook). Specifically, Meta is returning rate-limit errors indicating that affected ad accounts have exceeded allowed API request volumes (“Ad Account Has Too Many API Calls”). As a result, some data ingestion jobs are failing after multiple retry attempts. Our team is actively monitoring the situation and evaluating mitigation options while we continue to work within Meta’s API limits. We will provide further updates as more information becomes available.

2. resolved Feb 05, 2026, 05:00 PM UTC

   This has been resolved. We thank you for your patience while we worked through this issue.

Read the full incident report →

Started Sep 08, 2025, 09:11 PM UTC· resolved Feb 23, 2026, 05:28 PM UTC

1. identified Sep 08, 2025, 09:11 PM UTC

   Salesforce recently made a change that blocks users from performing the “Authorize KORE” step. As a result, Sponsorship to Salesforce customers using SSO (KOREAuth) will be unable to add new users to access Sponsorship. What changed: Salesforce now prevents end users from approving uninstalled Connected Apps. During “Authorize KORE,” non-admins are blocked. Who is affected: Sponsorship customers with Salesforce + KOREAuth SSO — including existing customers when adding new users. What users see: “We can’t authorize you because of an OAuth error.” (OAUTH_APPROVAL_ERROR_GENERIC) Interim workaround: Clients can enable Approve Uninstalled Connected Apps on all Profiles used by Sponsorship users. Path: Setup → Users→ Profiles, Edit the profile and enable the permission "Approve Uninstalled Connected Apps" A permanent solution is under validation now. We will update this page with additional details soon. Additional information can be found here: Salesforce KB: https://help.salesforce.com/s/articleView?id=005132365&type=1

2. resolved Feb 23, 2026, 05:28 PM UTC

   Our partner vendors at Salesforce have implemented a change in their authentication process that no longer blocks the "Authorize KORE" step and allows for new users to be added as expected. We thank you for your patience while we worked through this issue.

Read the full incident report →