Resolved after 10 days 11 hours, affecting Hub, on November 21, 2025.
Meta acknowledged the issue and pushed a fix this morning. The team is currently monitoring.
Affected components
Update timeline
- identified Nov 22, 2025, 08:58 AM UTC
Meta, our Facebook mention provider in Respond is currently experiencing issues with their APIs which means that we are unable to match facebook mentions to dives. We have contacted Meta and are currently working on a solution to restore service for all Respond clients that currently have an integrated facebook account.
- identified Nov 22, 2025, 11:21 PM UTC
The team has updated Respond clients saved dives to be able to more precisely target facebook mentions. We are still working with Meta for a resolution on this issue.
- identified Nov 22, 2025, 11:22 PM UTC
The team has updated Respond clients saved dives to be able to more precisely target facebook mentions. We are still working with Meta for a resolution on this issue.
- identified Nov 24, 2025, 02:19 AM UTC
We are still working with Meta for a resolution on this issue. We will update this thread once we receive an update.
- identified Nov 25, 2025, 02:35 AM UTC
We are continuing to work with Meta for a fix on this issue.
- monitoring Dec 01, 2025, 01:11 AM UTC
Meta acknowledged the issue and pushed a fix this morning. The team is currently monitoring.
- resolved Dec 02, 2025, 12:03 AM UTC
This incident has been resolved.
Your product runs on more than Lexer
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services