Khoros incident

YouTube Automatically De-authenticating & Scheduled Posts Not Published

Major Resolved View vendor source →

Khoros experienced a major incident on November 3, 2025 affecting User Login and Organic Publishing, lasting 1d 12h. The incident has been resolved; the full update timeline is below.

Started
Nov 03, 2025, 10:18 PM UTC
Resolved
Nov 05, 2025, 11:01 AM UTC
Duration
1d 12h
Detected by Pingoru
Nov 03, 2025, 10:18 PM UTC

Affected components

User LoginOrganic Publishing

Update timeline

  1. investigating Nov 03, 2025, 10:18 PM UTC

    We are currently investigating an issue causing all connected YouTube accounts to become automatically deauthenticated across multiple markets. As a result, scheduled posts to YouTube and other integrated platforms may not be published as expected. Some users have successfully reauthenticated their accounts but continue to receive deauthentication notifications. Others are unable to reauthenticate due to error messages. Impact Scope: YouTube integrations Scheduled post publishing Comment monitoring and moderation workflows Our engineering team is actively working with YouTube’s API team to identify the root cause and restore stable authentication. We will provide updates as soon as more information is available.

  2. investigating Nov 04, 2025, 04:30 AM UTC

    We’re continuing to investigate reports of YouTube accounts automatically disconnecting, which is impacting integrations, scheduled publishing, and comment workflows. We’ll continue to share updates as soon as new information is available.

  3. monitoring Nov 04, 2025, 05:50 AM UTC

    A fix has been implemented and customers can now connect/authenticate their YouTube accounts again. We are monitoring this.

  4. monitoring Nov 05, 2025, 04:48 AM UTC

    We are receiving confirmations that the issue has been resolved and no new issues have been reported related to this. We will continue to monitor.

  5. resolved Nov 05, 2025, 11:01 AM UTC

    This issue is now resolved, as confirmed by our users. Please reach out to Customer Support for any other queries.