Thryv incident
Nextdoor Listings Creation and Listing Updates are currently unavailable.
Thryv experienced a minor incident on August 14, 2025 affecting Marketing Center Listings Management, lasting 68d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 14, 2025, 02:49 PM UTC
Impact: Nextdoor Listings Creation and Listing Updates are currently unavailable. Cause: We've identified the root cause to be related to a dependency on a third-party vendor who is making a required infrastructure change. This is not a software bug, but rather a platform-level upgrade requiring significant changes. Timeline: Due to the complexity of the fix, we estimate that resolution may take up to 6 weeks. We understand the disruption this may cause and are actively working toward a long-term fix. We will provide biweekly updates on progress, or sooner if timelines change. Thank you for your continued patience
- identified Aug 28, 2025, 03:19 PM UTC
We remain on track for the 6-week estimate regarding the vendor infrastructure change. No new action is required from users at this time.
- identified Sep 12, 2025, 05:18 PM UTC
Update: Work on the vendor infrastructure change continues as expected. The 6-week completion estimate is unchanged, and no action is required from users.
- identified Sep 25, 2025, 06:11 PM UTC
Update: We remain on track for the 6-week estimate regarding the Nextdoor infrastructure updates. No new action is required from users at this time. We will have another update next Wednesday.
- monitoring Oct 01, 2025, 06:33 PM UTC
Update: The code freeze by Nextdoor has been lifted. We are now beginning to send updates again to Nextdoor. We are currently monitoring the issue.
- monitoring Oct 08, 2025, 07:35 PM UTC
Update: We are currently monitoring the issue.
- monitoring Oct 16, 2025, 04:23 PM UTC
Update: We are continuing to monitor to ensure that updates are being received by Nextdoor after the code freeze was lifted
- resolved Oct 21, 2025, 03:11 PM UTC
This has been resolved.