Thryv incident

Marketing Center & Business Center: Social Platform Outage - Command Center: Website Builder Outage

Major Resolved View vendor source →

Thryv experienced a major incident on February 25, 2025 affecting Leads Inbox, lasting 3h 7m. The incident has been resolved; the full update timeline is below.

Started
Feb 25, 2025, 07:47 PM UTC
Resolved
Feb 25, 2025, 10:55 PM UTC
Duration
3h 7m
Detected by Pingoru
Feb 25, 2025, 07:47 PM UTC

Affected components

Leads Inbox

Update timeline

  1. investigating Feb 25, 2025, 07:47 PM UTC

    Current Status: Partial Outage Discovered: 2/25/25 1PM CST Resolved: Impacted Product: Marketing Center, Business Center, and Command Center Affected Feature: Marketing Center & Business Center: Social Platform Command Center: Website Builder What does this mean for you? At this time when accessing the Social platform via Marketing Center or Business Center users will see an error stating "We were unable to locate your subscription" and cannot access the Social Platform features. Similarly, if users attempt to access their website builder via Command Center, users will see the same error stating "We were unable to locate your subscription" and cannot access the Website Builder features. We have a high priority ticket opened with our development team to determine the root cause and have this resolved. No current ETA Current Workaround: N/A We are working diligently to resolve this issue; we will provide ongoing status updates.

  2. investigating Feb 25, 2025, 08:36 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 25, 2025, 08:52 PM UTC

    Our development team has identified the issue and is working to implement a fix to resolve.

  4. monitoring Feb 25, 2025, 09:50 PM UTC

    A fix has been implemented and we are monitoring the results. We are not seeing any further reports of the error displaying when users access the Web Builder in Command Center, or the Social platform in Marketing Center or Business Center.

  5. resolved Feb 25, 2025, 10:55 PM UTC

    This incident has been fully resolved.